open-design-guidelisted

# Open Design guide This skill does not contain the library. It knows how to find it and how to use it well. The library is a local, offline clone of the content half of [Open Design](https://github.com/nexu-io/open-design). Plain files. No `od` binary, no daemon on port 7456, no desktop app. ## Step 1: locate the library Read `~/.claude/open-design-guide.local.md`. Its `library:` field is the absolute path to the clone. If that file does not exist, the library is not installed. Stop and tell the user to run: ```bash "${CLAUDE_PLUGIN_ROOT}/scripts/install.sh" ``` Do not guess a path and do not fall back to the network. One clone, one recorded location. ## Step 2: find the right entry Read `CATALOGUE.md` at the library root. That is the index: every design system grouped by category with its real tagline, every skill, every template. Never guess a folder name. Names are not obvious (`linear-app`, not `linear`). ## Step 3: read the entry, then work **Design systems** live at `design-systems/<name>/`. Read `DESIGN.md` first. It is the brand contract and it governs every other file in the folder: the atmosphere, the typographic logic, the reason a color exists. Skipping it and grabbing `tokens.css` alone produces output that has the right hex codes and the wrong soul. Then take real values from `tokens.css` or `design-tokens.json`, and copy component markup from `components.html`. Once a system is in play, invent nothing: no new colors, no new spacing steps, no new