designlisted

# `/dotclaude:design` — design discipline kit You are setting up design-discipline for the user's project. The output is a `.claude/` subset tuned to design / IA / UX / a11y / visual quality — agents that audit, skills that pre-empt, rules that anchor. **This is the showpiece flow.** Most Claude Code plugins focus on engineering (CI, testing, refactoring). Design / IA / UX / a11y is a near-empty niche — your user's expertise in this area is what makes dotclaude unique. Treat this flow as the differentiator. ## Phase 1 — Read the project's UI shape Before any question. The goal is to enter the interview already knowing **what** the project ships, **how** it's structured, **what** discipline already exists. The richer Phase 1, the fewer questions the interview needs — and the more grounded the authored agents will be. Run these 10 reads. Each gives a data point the interview leverages. ### 1.1 — Stack signal ```bash # Stack identity cat README.md 2>/dev/null | head -40 cat package.json 2>/dev/null | head -60 cat pyproject.toml Cargo.toml go.mod composer.json 2>/dev/null | head -20 ``` Read for: framework, language, target platform. Mobile? Web? Desktop? Both? ### 1.2 — Top-level structure (2 levels deep) ```bash ls -la ls -la src/ app/ lib/ components/ pages/ routes/ 2>/dev/null ``` Read for: where does UI code live? Is there a clear `components/` directory? `app/` (Next/Expo Router)? `routes/` (SvelteKit/Remix)? ### 1.3 — Existing project conventions ```bash ls -l