toolkit skill reference document.md
1.5 kB · 37 lines
Markdown
at main

tilde-style: document #

Write or update DESIGN.md from the current session's design state. Run at the end of every session.

Flow #

  1. Read the current DESIGN.md (if it exists).
  2. Read style.md for the active style tokens.
  3. Scan the project's CSS/HTML for:
    • Any new tokens defined this session
    • Any new component names used
    • Any new motion rules added
    • Any gaps noted but not resolved
  4. Update DESIGN.md:
    • Preserve the Design intention section verbatim — never overwrite it
    • Update the palette table if new tokens were added
    • Update the component vocabulary table
    • Update the motion section if new animations were added
    • Update Known gaps (remove resolved gaps; add new ones)
    • Add a ## Session [date] changelog entry at the bottom: one line per decision made

Changelog format #

## Session 2026-06-17

- Added Path navigation component (walk, not switch-tabs)
- Defined Teich-Abend evening mode via `data-mode="abend"`
- Added prefers-reduced-motion counterparts to welcome-fade and ripple
- Gap: prose/content surface not yet styled (field notes, specimen)

What document does NOT do #

  • It does not overwrite authorship. The design intention sentence is yours; document preserves it.
  • It does not generate new design decisions. It records what was decided.
  • It does not replace style.md. The manifest is the machine-readable source; DESIGN.md is the prose record. Both are needed.