design-managerlisted

# design-manager Ground UI work in ONE real, curated design system. Never load the corpus. ## Not for - Chart/graph/dashboard color and mark decisions — use a dedicated data-visualization skill. - Published Artifact/page-level design systems — use your platform's own design-guidance skill. - Sourcing a system that isn't already indexed here. Adding one is an authoring task (see "Adding a design system"), never something to do mid-task. ## Selection (deterministic — no model judgment, no extra call) 1. Read `manifest.json` in this skill's folder. If it has been sharded (see Scaling), read only the shard whose letter range covers your candidate names; if you have no candidate name yet, read every shard — they are jointly capped at the same budget. 2. Extract the request's **selection facts** from what the user actually wrote, in this priority order. Do not infer facts the user did not state. - `system` — a system named outright ("use Material 3"). An explicit name wins immediately; skip to step 4. - `framework` — react, vue, svelte, next, tailwind, plain-css, react-native. - `aesthetic` — the user's own adjective: minimal, brutalist, editorial, corporate, playful, dense, glassy, retro. - `project_type` — dashboard, marketing-site, docs, mobile-app, admin-panel, data-tool, landing-page. 3. Score every manifest entry: **+3** per matched `aesthetic` tag, **+2** per matched `project_type` tag, **+1** per matched `framework` tag. Case-in