History

DCCONSTRUCTIONS 69eb5260b0 Standardize NodeDC UI components		2026-05-02 10:56:43 +03:00
..
components	Standardize NodeDC UI components	2026-05-02 10:56:43 +03:00
recipes	docs: add nodedc ui guideline registry	2026-05-01 22:28:34 +03:00
rules	Standardize NodeDC UI components	2026-05-02 10:56:43 +03:00
sources	Standardize NodeDC UI components	2026-05-02 10:56:43 +03:00
tokens	docs: add nodedc ui guideline registry	2026-05-01 22:28:34 +03:00
README.md	docs: add nodedc ui guideline registry	2026-05-01 22:28:34 +03:00
mcp.manifest.json	docs: add nodedc ui guideline registry	2026-05-01 22:28:34 +03:00
registry.json	Standardize NodeDC UI components	2026-05-02 10:56:43 +03:00

README.md

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.