DESIGN:OS CLI (design-os)
Install once to equip any AI coding agent with 12+ domain design skills, deterministic verification gates, 2:1 axonometric art direction, and live Figma / SVG / 3D / SwiftUI / packaging workflows.
When to Use
Activate this skill when the user asks to:
"Initialize DESIGN:OS in this repo and wire our design tokens and verification gates for Claude Code and Codex.""Audit our current frontend components against DESIGN:OS typography, spacing, and WCAG 2.2 AA contrast gates.""Scaffold a new product landing page with 2:1 axonometric B&W technical illustrations and SEO/AEO/GEO metadata."
Progressive Disclosure Routing (What loads when)
- Always Loaded:
skills/design-os/SKILL.md(this router — keeps context lean). - On Demand — Prompt Recipes: Load
docs/cookbook.mdwhen selecting multi-step workflows or copy-paste prompt templates. - On Demand — Diagnostics: Load
commands/doctor.mdor runpython3 scripts/self_check.pywhen verifying installation or troubleshooting. - On Demand — Ecosystem Discovery: Load
llms.txtwhen cross-referencing companionDESIGN:OSengines.
Core Execution Workflow
- Inspect Context: Read the target repository or workspace constraints before mutating files.
- Execute Deterministically: Run
npx @easestart/design-os initornpx @easestart/design-os doctorrather than guessing outputs freehand. - Verify Quality Gates: Run
python3 scripts/self_check.pyand confirm zero errors before reporting completion.
Quality Bar & Anti-Scope
It's working if...
python3 scripts/self_check.pyexits0.- Outputs match the
DESIGN:OS2:1 axonometric B&W art direction and deterministic verification gates. - Execution remains 100% local with zero external telemetry (
PRIVACY.md).
When NOT to use
- Throwaway backend scripts with zero user-facing UI, CLI, or documentation surface.
- Teams looking for a hosted cloud SaaS design tool rather than a local-first, git-tracked engineering toolchain.
- Replacing human brand strategy — DESIGN:OS enforces and scales design systems, not customer discovery.


