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.md
source 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
  • architecture.architectureShardedLocation
    config (default:
    docs/architecture
    )
  • Write permissions to create files

Quick Start

  1. Run the skill
  2. Review existing documentation status
  3. Choose mode (create missing or recreate all)
  4. Wait for document generation
  5. Review generated documents and fill in project-specific details

Output Location:

docs/architecture/
(or as configured)

Workflow Steps

StepNamePurpose
1Load ConfigurationRead
core-config.yaml
settings
2Check ExistingShow status of existing docs
3Create DirectoryEnsure architecture folder exists
4Generate DocumentsCreate documents from templates
5Create Master IndexBuild README.md navigation
6Validate & CompleteVerify files and show next steps

Documents Generated

DocumentPurpose
coding-standards.md
Code quality and style guidelines
tech-stack.md
Technologies, frameworks, dependencies
source-tree.md
Code organization and structure
deployment.md
Infrastructure and deployment process
data-model.md
Database schemas and relationships
api-contracts.md
API endpoints and integrations
README.md
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 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

  1. 📝 Review each document and fill in project-specific details
  2. 🎨 Update status indicators as documents are completed
  3. 👥 Assign document owners
  4. 📅 Schedule quarterly reviews
  5. 🔄 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