svelte-kit-vice

Commit Graph

Author	SHA1	Message	Date
dev	b504c1c4b7	feat(eidos foundation): vertebrate typography via named-style aliases + R-2.7 Single source of truth for typography values that the recipe layer consumes. The foundation aliases `--font-ui` and `--leading-ui` (read by ~30 recipe tokens in `lib/recipes/base.ts`) now derive from the canonical `label` named style instead of carrying duplicate literals: --style-label-font-family: var(--font-family-primary); --style-label-line-height: 1.25; --font-ui: var(--style-label-font-family, var(--font-family-primary)); --leading-ui: var(--style-label-line-height, 1.25); Chain: typography.ts styles → --style-{name}-* → --leading-ui / --font-ui → recipe tokens → component CSS. Editing `STATIC_TYPOGRAPHY.styles.label.lineHeight` now propagates to every recipe in one go. Why not push recipes to consume `--style-{name}-` directly: - t-shirt sizes (xs/sm/md/lg/xl) don't map to four semantic buckets - per-component matices (description/caption/hint) need their own color / weight / letter-spacing - ref libraries (Radix Themes, Mantine, MUI, Chakra) all keep numerical scale for component internals; semantic layer is only for user-facing typography primitives (`<Text variant="body2">`) Audit rule R-2.7 (warn): detects literal font-size / font-weight / line-height / letter-spacing in eidos component CSS. Escape valves: var(...), numeric identities (0/0px/1), keywords (inherit/initial/ unset), or trailing `/ literal: <reason> */` comment. Current run flags 6 components with letter-spacing/font-size literals (all intentional micro-tracking and em-relative; can be annotated case by case). Documentation: - src/uix/eidos/README.md § "Vertebración tipográfica" — two-layer architecture rationale, alias chain diagram, comparison vs Radix Themes / Chakra / Mantine / MUI, escape valves - web/routes/uix/lib/COMPONENT_AUDIT_GUIDE.md § 4.11 — pointer to R-2.7 + cross-link to the foundation doc Verified end-to-end in browser at /uix/components/field: --font-ui → 'Instrument Sans', system-ui, sans-serif --style-label-font-family → 'Instrument Sans', system-ui, sans-serif --leading-ui → 1.25 --style-label-line-height → 1.25 computed [data-field-label].line-height → 17.5px (= 14 × 1.25) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	60a50f1c27	docs: COMPONENT_AUDIT_GUIDE.md — inviolable pre-flight + audit script Creates the binding pre-flight checklist every agent / contributor must read before touching any UIX component. AGENTS.md gets a top-banner linking the three required reads (this guide, DEMO_AUTHORING_GUIDE, eidos components README). Sections: 0. Inviolable rule — always read this + the demo guide + components README before coding 1. Reference library matrix (radix-themes, radix-primitives, chakra, mantine, mui, react-aria, ark, bits, shadcn, WAI-ARIA APG) 2. 4-layer ownership recap + 2-of-3 rule for morfo extensions 3. Pre-flight audit template (feature parity matrix, architectural choices, reference comparison, decision log, user sign-off line) 4. Project-wide architectural rules — Radix item/container split, composition over visibility props, chip parity, size category cheatsheet, per-event intent, no re-export facades, persistent label registries, floating layer defaults, combobox keyboard, Chakra band-above-control chips 4.11 `npm run component:audit` is the canonical verification tool — walks every component, parses morfo, cross-checks eidos + demo, emits report. A component is "done" only when its scoreboard row reads PASS with 0 errors. 5. Demo template is locked — points at DEMO_AUTHORING_GUIDE 6. Anti-pattern catalogue — every failed approach from recent sessions with WHY it failed (shallow demos, matchAnchorWidth, visibility booleans, inline chips, onpointerdown picks, flex 100% wrap, unregistering labels on unmount, auto-rendering wrappers, refocus without guard, agent git reset, skipped audit) 7. Canonical canaries per domain 8. Audit log — running table with commit hashes + known gaps from Layout Batch 1 9. Pre-port checklist (now includes README writing + the audit script run + npm run check) 10. "When in doubt, ask the user" closer Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago
dev	4d45cfcc82	docs: COMPONENT_AUDIT_GUIDE.md — inviolable pre-flight for component work Creates the binding pre-flight checklist every agent / contributor must read before touching any UIX component (`src/uix/{morfo, soma, sema, eidos}/components/{name}` or `web/routes/uix/components/{name}/`). Sections: 0. Inviolable rule — always read this + DEMO_AUTHORING_GUIDE + components/README before coding 1. Reference library matrix (radix-themes, chakra, mantine, mui, react-aria, ark, bits, shadcn, WAI-ARIA APG) with what each is for 2. 4-layer ownership recap (morfo / soma / sema / eidos) + the 2-of-3 rule for morfo extensions 3. Pre-flight audit template — feature parity matrix, architectural choices, reference comparison, decision log, user sign-off line 4. Project-wide architectural rules (Radix item/container split, composition over visibility props, chip parity, size category cheatsheet, per-event intent, no re-export facades, persistent label registries, floating layer defaults, combobox keyboard, Chakra band-above-control chips) 5. Demo template lock — points at DEMO_AUTHORING_GUIDE 6. Anti-pattern catalogue — every failed approach from recent sessions with WHY it failed (shallow demos, matchAnchorWidth, visibility booleans, inline chips, onpointerdown picks, flex 100% wrap, unregistering labels on unmount, auto-rendering wrappers, refocus without guard, agent git reset, skipped audit) 7. Canonical canaries per domain (drawer, search-field, box, flex, date-picker, avatar) 8. Audit log — running table of completed audits with commit hashes + the known gaps from Layout Batch 1 to address before the next round (alignContent on Flex/Grid, columns/rows shorthand on Grid, grow boolean on Group, fluid on Container, HStack/VStack helpers) 9. Pre-port checklist consumers can copy into task plans 10. "When in doubt, ask the user" closer AGENTS.md updated with a top-banner ⚠ block linking the three required reads (this guide, the demo guide, the eidos components README) so any new agent picks them up before touching code. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago

Author

SHA1

Message

Date

dev

b504c1c4b7

feat(eidos foundation): vertebrate typography via named-style aliases + R-2.7

Single source of truth for typography values that the recipe layer
consumes. The foundation aliases `--font-ui` and `--leading-ui` (read
by ~30 recipe tokens in `lib/recipes/base.ts`) now derive from the
canonical `label` named style instead of carrying duplicate literals:

  --style-label-font-family: var(--font-family-primary);
  --style-label-line-height: 1.25;

  --font-ui:    var(--style-label-font-family, var(--font-family-primary));
  --leading-ui: var(--style-label-line-height, 1.25);

Chain: typography.ts styles → --style-{name}-* → --leading-ui / --font-ui
→ recipe tokens → component CSS. Editing
`STATIC_TYPOGRAPHY.styles.label.lineHeight` now propagates to every
recipe in one go.

Why not push recipes to consume `--style-{name}-*` directly:
- t-shirt sizes (xs/sm/md/lg/xl) don't map to four semantic buckets
- per-component matices (description/caption/hint) need their own
  color / weight / letter-spacing
- ref libraries (Radix Themes, Mantine, MUI, Chakra) all keep
  numerical scale for component internals; semantic layer is only for
  user-facing typography primitives (`<Text variant="body2">`)

Audit rule R-2.7 (warn): detects literal font-size / font-weight /
line-height / letter-spacing in eidos component CSS. Escape valves:
var(...), numeric identities (0/0px/1), keywords (inherit/initial/
unset), or trailing `/* literal: <reason> */` comment. Current run
flags 6 components with letter-spacing/font-size literals (all
intentional micro-tracking and em-relative; can be annotated case by
case).

Documentation:
- src/uix/eidos/README.md § "Vertebración tipográfica" — two-layer
  architecture rationale, alias chain diagram, comparison vs Radix
  Themes / Chakra / Mantine / MUI, escape valves
- web/routes/uix/lib/COMPONENT_AUDIT_GUIDE.md § 4.11 — pointer to
  R-2.7 + cross-link to the foundation doc

Verified end-to-end in browser at /uix/components/field:
  --font-ui          → 'Instrument Sans', system-ui, sans-serif
  --style-label-font-family → 'Instrument Sans', system-ui, sans-serif
  --leading-ui       → 1.25
  --style-label-line-height → 1.25
  computed [data-field-label].line-height → 17.5px (= 14 × 1.25)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

dev

60a50f1c27

docs: COMPONENT_AUDIT_GUIDE.md — inviolable pre-flight + audit script

Creates the binding pre-flight checklist every agent / contributor must
read before touching any UIX component. AGENTS.md gets a top-banner
linking the three required reads (this guide, DEMO_AUTHORING_GUIDE,
eidos components README).

Sections:
0. Inviolable rule — always read this + the demo guide + components
   README before coding
1. Reference library matrix (radix-themes, radix-primitives, chakra,
   mantine, mui, react-aria, ark, bits, shadcn, WAI-ARIA APG)
2. 4-layer ownership recap + 2-of-3 rule for morfo extensions
3. Pre-flight audit template (feature parity matrix, architectural
   choices, reference comparison, decision log, user sign-off line)
4. Project-wide architectural rules — Radix item/container split,
   composition over visibility props, chip parity, size category
   cheatsheet, per-event intent, no re-export facades, persistent
   label registries, floating layer defaults, combobox keyboard,
   Chakra band-above-control chips
4.11 `npm run component:audit` is the canonical verification tool —
   walks every component, parses morfo, cross-checks eidos + demo,
   emits report. A component is "done" only when its scoreboard row
   reads PASS with 0 errors.
5. Demo template is locked — points at DEMO_AUTHORING_GUIDE
6. Anti-pattern catalogue — every failed approach from recent
   sessions with WHY it failed (shallow demos, matchAnchorWidth,
   visibility booleans, inline chips, onpointerdown picks, flex
   100% wrap, unregistering labels on unmount, auto-rendering
   wrappers, refocus without guard, agent git reset, skipped audit)
7. Canonical canaries per domain
8. Audit log — running table with commit hashes + known gaps from
   Layout Batch 1
9. Pre-port checklist (now includes README writing + the audit
   script run + npm run check)
10. "When in doubt, ask the user" closer

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

dev

4d45cfcc82

docs: COMPONENT_AUDIT_GUIDE.md — inviolable pre-flight for component work

Creates the binding pre-flight checklist every agent / contributor
must read before touching any UIX component (`src/uix/{morfo, soma,
sema, eidos}/components/{name}` or `web/routes/uix/components/{name}/`).

Sections:
0. Inviolable rule — always read this + DEMO_AUTHORING_GUIDE +
   components/README before coding
1. Reference library matrix (radix-themes, chakra, mantine, mui,
   react-aria, ark, bits, shadcn, WAI-ARIA APG) with what each is for
2. 4-layer ownership recap (morfo / soma / sema / eidos) + the
   2-of-3 rule for morfo extensions
3. Pre-flight audit template — feature parity matrix, architectural
   choices, reference comparison, decision log, user sign-off line
4. Project-wide architectural rules (Radix item/container split,
   composition over visibility props, chip parity, size category
   cheatsheet, per-event intent, no re-export facades, persistent
   label registries, floating layer defaults, combobox keyboard,
   Chakra band-above-control chips)
5. Demo template lock — points at DEMO_AUTHORING_GUIDE
6. Anti-pattern catalogue — every failed approach from recent
   sessions with WHY it failed (shallow demos, matchAnchorWidth,
   visibility booleans, inline chips, onpointerdown picks, flex
   100% wrap, unregistering labels on unmount, auto-rendering
   wrappers, refocus without guard, agent git reset, skipped audit)
7. Canonical canaries per domain (drawer, search-field, box, flex,
   date-picker, avatar)
8. Audit log — running table of completed audits with commit hashes
   + the known gaps from Layout Batch 1 to address before the next
   round (alignContent on Flex/Grid, columns/rows shorthand on Grid,
   grow boolean on Group, fluid on Container, HStack/VStack helpers)
9. Pre-port checklist consumers can copy into task plans
10. "When in doubt, ask the user" closer

AGENTS.md updated with a top-banner ⚠ block linking the three
required reads (this guide, the demo guide, the eidos components
README) so any new agent picks them up before touching code.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

3 Commits (cd2c0326dc0a8be8ee08a4ca69f997dbe86f0b93)