T-CNW8-design-language-layer-styling-idiom
Status: open/ready · Impact: low · Complexity: small
Each layer styles differently — @determined/ui leans on Tailwind
arbitrary values, app-frame on scoped CSS — but nothing states the idiom,
so moves between layers are unpredictable (SURVEY drift 11). Write one
idiom per layer down.
| Location | Role today |
|---|---|
packages/ts/ui/ | Tailwind arbitrary-value idiom (text-(--d-text-muted)), by practice only. |
packages/ts/app-frame/ | Scoped-CSS idiom, by practice only. |
packages/ts/ui/docs/design-system.md | States neither. |
Proposed
Section titled “Proposed”A short spec section naming the idiom per layer (ui, app-frame, experiences/products) and when each applies, so code moved between layers gets restyled to the destination idiom deliberately.
Approach
Section titled “Approach”- Confirm the de-facto idiom per layer from current code.
- Write the section into
design-system.md; cross-link from S-0010.
Files to touch
Section titled “Files to touch”| Location | Kind | Change |
|---|---|---|
packages/ts/ui/docs/design-system.md | modify | per-layer idiom section |
docs/planning/standards/S-0010-design-language-consumption.md | modify | cross-link |
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: The spec names the idiom for ui, app-frame, and experiences/products.
- AC-2: S-0010 links the section.
Out of scope
Section titled “Out of scope”- Rewriting existing styles to match (only the rule is written).
Dependencies
Section titled “Dependencies”- none
Discovery context
Section titled “Discovery context”- SURVEY.md drift 11;
docs/planning/design-language/PLAN.mdPhase 2.