// Analyze a project's codebase and documentation to generate coding standards, architecture docs, and development practices. Perfect for new project onboarding. Usage: 'analyze-project: /path/to/project' or 'analyze: /path/to/project'
Save and recall information across sessions. Use when you hear 'remember this', 'save to memory', 'add to your knowledge', or similar. Stores to Claude OS knowledge bases for persistent recall.
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
Analyze a project's codebase and documentation to generate coding standards, architecture docs, and development practices. Perfect for new project onboarding. Usage: 'analyze-project: /path/to/project' or 'analyze: /path/to/project'
| name | analyze-project |
| description | Analyze a project's codebase and documentation to generate coding standards, architecture docs, and development practices. Perfect for new project onboarding. Usage: 'analyze-project: /path/to/project' or 'analyze: /path/to/project' |
| allowed-tools | Read, Write, Bash, Glob, Grep |
Automatically analyze any project's codebase, specifications, and coding patterns to generate comprehensive documentation for the project_profile MCP. This enables AI assistants to understand:
Simply say one of:
How it works:
Example Workflow:
You: "analyze-project: 1"
→ Loads project from Claude OS (ID #1)
→ Registers 4 MCPs (myapp-project-profile, etc.)
→ Analyzes codebase
→ Generates 3 docs locally
→ Displays summary:
PROJECT: MyApp (ID: 1)
TYPE: Rails
... (save this to native memory)
→ MCPs ready to load on-demand when you need them
Then:
You (saving to memory): "Remember: [paste the summary above]"
When working on the project: "Load myapp-project-profile"
→ Loads that specific MCP into context only when needed
When you invoke this skill:
CODING_STANDARDS.md - Style, conventions, patternsARCHITECTURE.md - Design, structure, principlesDEVELOPMENT_PRACTICES.md - Workflows, testing, deployment.claude-os/project-profile/ for referenceYou: "analyze-project: /Users/me/Projects/my-rails-app"
→ I scan Rails structure (app/, config/, spec/, etc.)
→ Analyze Models, Controllers, Services, Views
→ Review gems and dependencies
→ Generate 3 docs with Rails-specific patterns
→ Save to mcp/kb/my-rails-app-project-profile/
→ Confirm: "✓ Project analysis complete. 3 docs saved to project_profile KB"
You: "analyze-project: /Users/me/Projects/api-service architecture"
→ Focus on architecture analysis
→ Generate ARCHITECTURE.md
→ Skip coding standards and practices (or generate minimal versions)
You: "analyze-project: /Users/me/Projects/my-project"
→ Existing docs are replaced with fresh analysis
→ Useful after major refactoring or architecture changes
✅ Consistency - Apply same analysis to any project ✅ Speed - Generate docs in seconds instead of hours ✅ Comprehensive - Captures coding style, architecture, and practices ✅ Automatic Integration - Syncs directly to project_profile MCP ✅ Reusable - Same skill works for Rails, Python, Node, Go, etc. ✅ AI-Friendly - Docs enable Claude to write better code for your project
Output Location: mcp/kb/{project-name}-project-profile/
Document Names:
CODING_STANDARDS.mdARCHITECTURE.mdDEVELOPMENT_PRACTICES.mdIntegration: Automatically available in Claude OS's project_profile MCP Storage: SQLite via project_profile knowledge base Sync: Uses Claude OS file watcher for auto-updates
Pro Tip: Run this skill immediately after creating a new project in Agent OS. The generated docs become the foundation for AI-assisted development, ensuring all code generation aligns with your project's patterns and practices.