odin-design

Use when starting UI work, defining palettes or design tokens, or fixing AI-generic, vibe-coded, or default-framework UI. Also handles TUI, CLI, and desktop surfaces when the runtime is named. Not for persisted design systems; use design-consultation. Not for live-URL audits; use web-design-review. No irreversible changes.

Use when /design-consultation proposes a design system with mockups or HTML and persists the approved system in DESIGN.md. Not for in-chat direction picking — use design. No remote, credential, publish, deploy, or irreversible changes.

Use when creative work is requested and no approved design exists, or when a raw idea or repository must be developed into an approved design document. Routes through idea, spike, bounded, or architectural design and fires before any implementation action. Not for work with an approved design already in context. No remote or irreversible changes.

Use when /design-variants generates distinct design directions and a gallery for selection. Not for one polished artifact — use polished-web-prototype; not for token-system direction picking — use design. No remote, credential, publish, deploy, or irreversible changes.

Use when a user builds or styles a web frontend or asks to make it not look AI-generated. Commits a token system and crafted interface passing a slop-audit and WCAG 2.2 AA gate. Not for component-level UI work without the token system; use frontend-ui-engineering. Local writes only.

Use when asked to build or modify user-facing interfaces and pages with production quality: components, layouts, state management, WCAG 2.1 AA accessibility, and real content, with output that looks hand-crafted rather than AI-generated. Not for token-system design with slop-audit gates; use frontend-design-deslop. Local writes only.

Use when the user invokes /ios-visual-review to audit an iOS app's visuals on a real device. Produces a per-screen visual-review report scoring ten dimensions 0-10 with a biggest-leverage fix for each. Don't use for remote, credential, publish, deploy, or irreversible changes.

Use when the user runs /polished-web-prototype or asks to turn an approved mockup, design plan, or freeform description into a polished responsive Pretext-native HTML artifact refined through a live preview loop. Writes the artifact and finalized.json under the project design directory. Not for variant galleries; use design-variants. Not for live-URL audits; use web-design-review.

Use when deciding what an interface should do before UI is built or audited: interaction consequences, action scope, reachable states, naming, and accessibility of the product decision. Read-only analysis; produces a chat report with findings and routed follow-on work. Not for visual implementation; use prototype.

Use when writing, editing, cleaning, or refactoring Tailwind classes, components, or configuration. Reorders and deduplicates classes, replaces arbitrary values with project tokens, and checks component extraction. Not for read-only audits of Tailwind code, or general CSS without Tailwind.

Use when asked to audit typography across a codebase. Produces a file:line report with concrete CSS and HTML fixes ordered by impact across 10 categories, and records rules that need rendered metrics as not-verifiable-from-source instead of fabricating violations. Not for building a type system or token scale.

Use when directing, building, or auditing React/Next.js UI in Tailwind: visual direction, responsive or dark-mode retrofits, and file:line UX findings with a ship verdict. Not for deep typography or motion passes; use typography-audit or ui-animation.

Use when the user runs /web-design-review with a URL to visually audit a live UI through the browser and fix findings in a screenshot-verified loop. Not for design direction picking; use design. Not for variant galleries; use design-variants.