Map Design Language

Research the stable visual rules already established in a project and record them in one meta/DESIGN.md. The file explains how the UI should look and behave; runtime styling sources keep ownership of exact values.

Protocol

Step 1 — Detect mode

Check for meta/DESIGN.md:

• Missing → bootstrap: research the established UI and create the file.
• Exists → read the whole file, then use the Step 2 source scan to decide whether it needs a refresh.

When no established UI exists, stop and offer to invoke frontend-design; this skill records a design language and does not invent one.

Step 2 — Map surfaces and canonical sources

Identify whether the repository has one design language or several distinct UI surfaces with different toolkits, token vocabularies, audiences, or render targets. Inspect the root package manifests, workspaces, UI directories, framework imports, and existing product or brand guidance.