From great-designers
Scaffold a design/ directory at the project root, sibling to manuscript/, film/, publishers/, marketing/, engineering/. Adds a Design section to CLAUDE.md (or creates one if absent) so design-stage commands know where to write. Use when starting the design work for a project — UI/UX, brand, design system, or cross-craft.
How this skill is triggered — by the user, by Claude, or both
Slash command
/great-designers:designers-project-initThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Scaffold the `design/` directory and register it in the project's `CLAUDE.md`.
Scaffold the design/ directory and register it in the project's CLAUDE.md.
Creates a design/ folder at the current working directory's project root with three subdirectories:
design/
├── specs/ # Design specs, IA docs, interaction specs, flow diagrams
├── audits/ # Design reviews, accessibility audits, heuristic evals
└── systems/ # Design system docs, component libraries, type scales, color tokens
Then adds (or creates) a ## Design section in CLAUDE.md:
## Design
**Path:** `design/` (at project root)
**Current spec:** `<user-chosen-slug>` (the spec or surface you're actively working on)
Commands that generate design artifacts (`/designers-channel` save behavior, `/designers-write-spec`, `/designers-design-review`) write to `design/<subdir>/<current-spec>.md` by default. Update `Current spec` when moving to a different surface or subsystem.
The designer personas read this file plus the project's `README.md`, brand brief at `design/systems/brand.md` (if present), existing component libraries, and any user research artifacts. For cross-craft projects (writing or film with a UI surface), they also read `.great-authors/project.md`.
For strategic visual taste at the executive register, cross-dispatch `great-minds:jony-ive-designer` — he stays in great-minds.
/designers-channel with save triggers (which need to know where to write).When this skill is invoked:
Resolve the project root. Use the current working directory unless the user specifies otherwise.
Check for existing design/ directory. If it exists, ask: "A design/ directory already exists. Overwrite the scaffold (destroys existing content) or skip (leaves it alone)? (overwrite/skip)" — default skip.
Read existing project context. Look for these files and read them if present:
README.mdCLAUDE.mddesign/systems/brand.md, BRAND.md, brand-guide.md)package.json, pyproject.toml, etc.) — informs which designers might be most relevant.great-authors/project.md (if cross-craft project)This context informs which design personas the user should know about (e.g., if there's a data-heavy dashboard, mention Tufte; if there's a brand identity question, mention Scher; if there's an icon system, mention Kare).
Ask the spec-slug question. One question:
onboarding-v3, dashboard-redesign, brand-identity-2026)."Create the directory tree. Three empty subdirectories under design/:
specs/audits/systems/Update CLAUDE.md. Read the existing file. If it doesn't exist, create one with a minimal header plus the ## Design section. If it exists and has a ## Design section, ask whether to overwrite. If it exists without one, append the ## Design block documented above.
Report:
Created design/ with subdirs:
specs/ audits/ systems/
Updated CLAUDE.md with ## Design section.
Current spec: <slug>
Detected project context:
- <Surface summary: dashboard / brand / app / book site / etc.>
- <Key files present: brand.md, research/, etc.>
Next:
- /designers-channel <persona> for direct collaboration. The personas best-fit to this surface are <list 2-3 based on project signals>.
- /designers-write-spec <feature> to draft a design spec.
- /designers-design-review <path> to audit existing UI or design system.
For strategic visual taste at the executive register, dispatch jony-ive-designer from great-minds:
Agent({subagent_type: "great-minds:jony-ive-designer", ...})
design/ directory is for ARTIFACTS at the design stage. The actual UI implementation lives in src/ (or wherever the project conventions place it). Design artifacts describe, audit, and decide; they don't replace the code..great-authors/ is needed. For cross-craft projects, .great-authors/ is the bible spine and designer personas read it alongside the design context.current-spec slug names "what we're working on right now." Update it when you move to a different surface within the same project.npx claudepluginhub sethshoultes/great-designers-plugin --plugin great-designersProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.