Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action> sub-command pattern. Git-flow consolidated from 8→5 commands (commit variants absorbed into --push/--merge/--sync flags). Dispatch files, name: frontmatter, and cross-reference updates for all plugins. Phase 2: Design documents for 8 new plugins in docs/designs/. Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate, saas-react-platform, saas-test-pilot, data-seed, ops-release-manager, ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents, skills, README, and claude-md-integration. Marketplace grows from 12→20. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
name, description
| name | description |
|---|---|
| claude-config init | Initialize a new CLAUDE.md file for a project |
/claude-config init
Create a new CLAUDE.md file tailored to your project.
Skills to Load
- skills/visual-header.md
- skills/claude-md-structure.md
- skills/pre-change-protocol.md
Visual Output
Display: CONFIG-MAINTAINER - CLAUDE.md Initialization
Usage
/claude-config init # Interactive
/claude-config init --minimal # Minimal version
/claude-config init --comprehensive # Detailed version
Workflow
- Analyze project structure, ask clarifying questions
- Detect technologies, frameworks, tools
- Generate tailored CLAUDE.md sections
- Allow review and customization
- Save file in project root
Templates
| Template | Sections |
|---|---|
| Minimal | Overview, Quick Start, Critical Rules, Pre-Change Protocol |
| Standard | + Architecture, Common Operations, File Structure |
| Comprehensive | + Troubleshooting, Integration Points, Workflow |
Note: Pre-Change Protocol is MANDATORY in all templates.
When to Use
- Starting a new project
- Project lacks CLAUDE.md
- Taking over unfamiliar project