Map Design Language

Research what a project's UI is built from — toolkits, tokens, components, styling models — and record it as a lean meta/DESIGN.md of facts. Other skills (generate-mockups, product-interview) and humans read it to ground UI work.

When to use

YES: no meta/DESIGN.md exists and a skill or human needs grounding facts; the file exists but a surface's toolkit/tokens changed or it has gaps; the user asks to map/document/bootstrap/refresh the design language.

NOT this if:

• meta/DESIGN.md exists and is current → just read it.
• you're inventing a new aesthetic from a blank canvas → frontend-design.

Protocol

Step 1 — Detect state and mode

Check for meta/DESIGN.md:

• Missing → bootstrap mode: research everything, write the file.
• Exists → read it. A surface's toolkit/tokens changed, or blocks are missing/incomplete → refresh mode: update the affected blocks only. Current and complete → stop; tell the user it's already good.