# NODE.DC UI Guideline

This folder is the first local source of truth for reusable NODE.DC UI components.

It is intentionally MCP-friendly:
- `registry.json` lists every known component contract.
- `tokens/nodedc.tokens.json` contains machine-readable design tokens.
- `tokens/nodedc.tokens.css` mirrors runtime CSS variables.
- `components/*.json` describe component anatomy, states, rules, and source references.
- `recipes/*.json` describe larger UI compositions.
- `sources/source-map.json` links this launcher and NODEDC Task Manager implementation files.

The codebase remains the source of truth for implementation. This folder is the index and contract layer that an MCP server or coding agent can read before generating UI.

## Operating Rule

Before creating a new NODE.DC UI element, check `registry.json`.

If a matching component exists, use or extend it. Do not create a local one-off dropdown, modal, button, status pill, table, calendar, or navigation panel.