architecture-blueprint-generator

Generates architecture blueprint documentation by analyzing codebase structure, patterns, and technology stacks.

25|4|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/thangchung/agent-engineering-experiment --skill architecture-blueprint-generator-thangchung
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-blueprint-generator
Source: https://github.com/thangchung/agent-engineering-experiment/tree/main/agentgateway-entraid-obo/.claude/skills/architecture-blueprint-generator
Command: npx skills add https://github.com/thangchung/agent-engineering-experiment --skill architecture-blueprint-generator-thangchung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often lack up-to-date architectural documentation, making it hard to onboard developers, maintain consistency, and guide new feature development. This Skill analyzes an existing codebase and produces a comprehensive Project_Architecture_Blueprint.md that captures the actual implemented architecture. ## Core Features & Use Cases - Automatic Detection: Identifies technology stacks (.NET, Java, React, Angular, Python, Node.js, Flutter) and architectural patterns (Clean Architecture, Microservices, MVC, Hexagonal, and more) directly from project files and dependencies. - Diagram Generation: Creates C4, UML, flow, or component diagrams at multiple abstraction levels reflecting the real implementation. - Deep Documentation: Covers layers, data architecture, cross-cutting concerns, service communication, testing, deployment, extension points, and architectural decision records. - Use Case: A lead engineer inheriting an undocumented microservices system runs this Skill to produce a definitive architecture reference, including extension guidelines and implementation templates for new developers. ## Quick Start Analyze this codebase and generate a comprehensive architecture blueprint document with C4 diagrams and architectural decision records.

Frequently Asked Questions about architecture-blueprint-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate architecture documentation from an existing codebase?▼

Run the architecture blueprint generator against your project root. It analyzes project files, dependencies, and folder organization to detect the technology stack and architectural pattern, then produces a Project_Architecture_Blueprint.md document covering components, layers, and data flow.

What architectural patterns can this generator detect?▼

It detects Clean Architecture, Microservices, Layered, MVVM, MVC, Hexagonal, Event-Driven, Serverless, and Monolithic patterns. Detection is based on folder organization, dependency flow, interface segregation, and communication mechanisms found in the actual code.

Which technology stacks are supported for architecture analysis?▼

Supported stacks include .NET, Java, React, Angular, Python, Node.js, and Flutter, with an auto-detect mode for mixed codebases. Each stack has dedicated sections covering framework-specific patterns like dependency injection, middleware pipelines, and state management.

Can I generate C4 or UML diagrams of my system architecture?▼

Yes, set the DIAGRAM_TYPE variable to C4, UML, Flow, or Component. The generator creates diagrams at multiple abstraction levels, including subsystem overviews, component interactions, and data flow, based on actual code dependencies rather than theoretical patterns.

Does the blueprint include guidance for adding new features?▼

Yes, the blueprint includes an extensibility section with feature addition patterns, implementation templates, and common pitfalls. It documents where to place new components, dependency introduction guidelines, and integration patterns for external systems.

What are the limitations of automated architecture detection?▼

Auto-detection relies on conventions visible in code structure and configuration files, so highly unconventional or hybrid architectures may need manual pattern specification. Diagrams reflect implemented dependencies and may not capture runtime-only or externally orchestrated interactions.