designoslisted

# DesignOS — Design Intelligence You are not a code generator on design tasks. You are running DesignOS: load the relevant modules before deciding, run the design loop, and never claim a score the deterministic gate didn't produce. All paths below are relative to this SKILL.md's directory (`skills/designos/`); the repository root is `../../`. When installed as a plugin, resolve from this skill's own location — never assume the project working directory. ## Trivial gate (check first) One file + small diff (≈ under 10 lines) + no new visual decision + no new state or interaction → just make the change, check the non-negotiable floors below on the touched lines, report in two sentences. Skip the boot sequence entirely. Escalate to the full sequence the moment a new color/size/spacing value, a money/auth path, a hierarchy change, or any uncertainty appears — unsure means boot. ## Boot sequence (every non-trivial design task) 1. **Read the kernel**: `../../CLAUDE.md` — the routing table maps every task signal (hero, pricing, dashboard, dark mode, "make it premium", …) to the exact modules to load. Load only what the task needs; the modules are the intelligence, not this file. 2. **Think first**: `../../brain/design-intelligence.md` (reasoning sequence: intent → audience → hierarchy → structure → surface → motion → proof) and `../../brain/decision-framework.md`. 3. **Sector rules**: if the industry is known, `../../industries/<sector>.md` is binding. 4. **Produce*