Claude-skill-registry initialize-architecture
Use to create complete architecture documentation structure. Creates all required architecture documents from templates.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/initialize-architecture" ~/.claude/skills/majiayu000-claude-skill-registry-initialize-architecture && rm -rf "$T"
manifest:
skills/data/initialize-architecture/SKILL.mdsource content
Initialize Architecture Documentation Task
When to Use
- New Projects: Initialize architecture documentation for greenfield projects
- Missing Documentation: Create missing architecture documents in existing projects
- Architecture Reset: Rebuild architecture documentation structure
- Onboarding: Ensure all architecture documents exist for new team members
What This Skill Does
Creates complete architecture documentation structure from templates:
- Configuration: Reads locations from
.prism/core-config.yaml - Status Check: Detects existing vs missing documents
- Generation: Creates documents from standardized templates
- Indexing: Builds master README with navigation
Prerequisites
- Project root must have
.prism/core-config.yaml
config (default:architecture.architectureShardedLocation
)docs/architecture- Write permissions to create files
Quick Start
- Run the skill
- Review existing documentation status
- Choose mode (create missing or recreate all)
- Wait for document generation
- Review generated documents and fill in project-specific details
Output Location:
docs/architecture/ (or as configured)
Workflow Steps
| Step | Name | Purpose |
|---|---|---|
| 1 | Load Configuration | Read settings |
| 2 | Check Existing | Show status of existing docs |
| 3 | Create Directory | Ensure architecture folder exists |
| 4 | Generate Documents | Create documents from templates |
| 5 | Create Master Index | Build README.md navigation |
| 6 | Validate & Complete | Verify files and show next steps |
Documents Generated
| Document | Purpose |
|---|---|
| Code quality and style guidelines |
| Technologies, frameworks, dependencies |
| Code organization and structure |
| Infrastructure and deployment process |
| Database schemas and relationships |
| API endpoints and integrations |
| Master index and navigation |
Modes
- Create Missing: Only generate documents that don't exist
- Recreate All: Regenerate all documents (overwrites existing)
- Cancel: Exit without changes
Reference Documentation
- Document Templates - Detailed templates for each document type
Document Status Indicators
All documents start as Draft and progress through:
- 🔴 Draft - Initial template, needs content
- 🟡 In Progress - Being actively updated
- 🟢 Complete - Reviewed and approved
Next Steps After Initialization
- 📝 Review each document and fill in project-specific details
- 🎨 Update status indicators as documents are completed
- 👥 Assign document owners
- 📅 Schedule quarterly reviews
- 🔄 Keep documentation current with architecture changes
Guardrails
- Always verify config is loaded before proceeding
- Check for existing documents to avoid accidental overwrites
- Write files immediately after generation
- Inform user of all files created
- Provide clear next steps for document completion