T-DUEF-design-language-starlight-skin

Status: open/ready · Impact: medium · Complexity: medium

Goal

The doc sites should wear the family face. Express the Platinum seed tokens (light + dark) as a Starlight customCss file, shipped through the deterministic site-assembly seam so sites/df-docs and the library doc sites all pick it up. Phase 4 of D-DLNG-design-language.

Today

Location	Role today
sites/df-docs/	Starlight site on the stock theme.
solutions/ontological/site-template/	The D-0010 site-assembly seam; every doc site materializes from it.
packages/ts/ui/app/assets/css/tokens.css	The seed values to project (Platinum light/dark Tier-1 seeds).

Proposed

A customCss file in the site template mapping Platinum seeds onto Starlight’s CSS custom properties (both modes), so a regenerated site carries the skin with no per-site work.

Approach

1. Map Starlight’s theming properties to the closest --d-* seeds (static values — doc sites don’t load the layer).
2. Add the file + wiring to solutions/ontological/site-template/.
3. Regenerate sites/df-docs; before/after light+dark screenshots.
4. Note the projection (and its static nature) in design-system.md.

Files to touch

Location	Kind	Change
solutions/ontological/site-template/	modify	customCss + wiring
sites/df-docs/	modify	regenerated with the skin
packages/ts/ui/docs/design-system.md	modify	projection note

Acceptance criteria

• AC-1: df-docs renders the Platinum palette in light and dark.
• AC-2: The skin arrives via site-template (a fresh materialization carries it), not hand-edits to one site.
• AC-3: Before/after screenshot pairs in the PR.

Out of scope

• Non-Starlight static surfaces (augmented_dot_com), report templates (T-J8MT-design-language-report-palette).

Dependencies

• none

Discovery context

• docs/planning/design-language/PLAN.md Phase 4; D-0010 site assembly.

---

← Back to Tasks