- New commands: /define-design, /update-design, /generate-app (web | flutter | winui3) - New skills: ui-design, design-tokens, platform-ui-generation - /add-feature: check design spec before implementation (Step 3.5) and reconcile all six persistent docs after implementation (Step 8) - /setup-project: automatic document creation with self-check checkpoints - CLAUDE.md: document docs/design/, .claude/ configuration, and the design phase in the development process - Enrich subagent descriptions; allowlist new skills in settings.json - Add docs/design/README.md Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2.9 KiB
2.9 KiB
| description |
|---|
| Initial setup: automatically create the six persistent documents |
Initial Project Setup
This command automatically creates the project's six persistent documents without pausing for human feedback between steps.
How to Run
claude
> /setup-project
Pre-Run Check
Check the files in the docs/ideas/ directory.
# Check
ls docs/ideas/
# If files exist
✅ Found docs/ideas/initial-requirements.md
The PRD will be created based on its contents
# If no files exist
⚠️ No files found in docs/ideas/
The PRD will be created from the project context
Procedure
Step 0: Read the Inputs
- Read all markdown files in
docs/ideas/ - Understand their contents and use them as reference for creating the PRD
Step 1: Create the Product Requirements Document
- Load the prd-writing skill to guide PRD creation
- Create
docs/product-requirements.mdbased on the contents ofdocs/ideas/ - Flesh out the ideas raised during brainstorming:
- Detailed user stories
- Acceptance criteria
- Non-functional requirements
- Success metrics
- Run the skill's self-check checkpoints; if issues are found, fix them inline, then proceed immediately to the next step
All subsequent steps run automatically without waiting for human feedback.
Step 2: Create the Functional Design Document
- Load the functional-design skill
- Read
docs/product-requirements.md - Create
docs/functional-design.mdfollowing the skill's template and guide
Step 3: Create the Architecture Design Document
- Load the architecture-design skill
- Read the existing documents
- Create
docs/architecture.mdfollowing the skill's template and guide
Step 4: Create the Repository Structure Document
- Load the repository-structure skill
- Read the existing documents
- Create
docs/repository-structure.mdfollowing the skill's template
Step 5: Create the Development Guidelines
- Load the development-guidelines skill
- Read the existing documents
- Create
docs/development-guidelines.mdfollowing the skill's template
Step 6: Create the Glossary
- Load the glossary-creation skill
- Read the existing documents
- Create
docs/glossary.mdfollowing the skill's template
Completion Criteria
- All six persistent documents have been created
Completion message:
"Initial setup is complete!
Documents created:
✅ docs/product-requirements.md
✅ docs/functional-design.md
✅ docs/architecture.md
✅ docs/repository-structure.md
✅ docs/development-guidelines.md
✅ docs/glossary.md
You are now ready to start development.
How to use going forward:
- Editing documents: just ask in normal conversation
Examples: 'Add a new feature to the PRD', 'Review architecture.md'
- Adding features: run /add-feature [feature name]
Example: /add-feature User authentication
- Document review: run /review-docs [path]
Example: /review-docs docs/product-requirements.md
"