skills.rest
MatheusFelipeCorrea
MatheusFelipeCorreaCOMMUNITY
Explore all skills by this author →
GitHub

architecture-blueprint-generator

Generates comprehensive architecture documentation by analyzing codebase structure, patterns, and integrations.

Updated Jun 19, 2026
Search Tags:#architecture#documentation#code generation#monorepo#codebase analysis#blueprint#diagrams
One-click install
npx skills add https://github.com/MatheusFelipeCorrea/Agrofarm --skill architecture-blueprint-generator-matheusfelipecorrea
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-blueprint-generator
Source: https://github.com/MatheusFelipeCorrea/Agrofarm/tree/main/.github/skills/architecture-blueprint-generator
Command: npx skills add https://github.com/MatheusFelipeCorrea/Agrofarm --skill architecture-blueprint-generator-matheusfelipecorrea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams struggle to keep architectural documentation accurate and current as codebases evolve, making onboarding slow and architectural decisions inconsistent. This Skill analyzes an actual codebase and produces a definitive Project_Architecture_Blueprint.md that reflects the real implementation rather than outdated assumptions. ## Core Features & Use Cases - Automatic Stack and Pattern Detection: Identifies technology stacks (.NET, Java, React, Angular, Vue, Next.js, Node.js, Python, Go, Rust, Rails, Flutter, and more) and architectural patterns (Clean Architecture, Microservices, MVC, CQRS, and others) directly from project files and dependencies. - Monorepo-Aware Analysis: Detects workspace configurations and sub-projects, analyzes each independently, then documents cross-project contracts, shared packages, authentication flows, and end-to-end data flows. - Deep Concern Coverage: Documents background jobs, external API integrations, infrastructure-as-code, data pipelines, state management strategies (Zustand, Redux, TanStack Query, SWR), and response formatting layers. - Use Case: A developer joining a React + Node.js monorepo runs the Skill to generate a blueprint covering the API layer structure, frontend state management, shared contracts, and deployment topology, giving them an accurate architectural reference in minutes. ## Quick Start Ask the AI to analyze this repository and generate a comprehensive Project_Architecture_Blueprint.md documenting its architecture, patterns, and integrations.

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 repository root. It auto-detects the technology stack and architectural pattern from project files and dependencies, then writes a Project_Architecture_Blueprint.md covering layers, components, data flow, and cross-cutting concerns.

What tools analyze monorepo architecture across multiple sub-projects?▼

This Skill detects workspace configurations like pnpm-workspace.yaml, turbo.json, and nx.json, analyzes each sub-project independently, then documents cross-project contracts, shared packages, authentication flows, and end-to-end data flows between services.

Does it support React state management analysis like Zustand or Redux?▼

Yes. It detects Zustand, Redux Toolkit, TanStack Query, and SWR from dependencies and folder conventions, then documents store organization, slice structure, cache strategies, mutation patterns, and how multiple state solutions interact.

Can it document background jobs and external API integrations?▼

Yes. It scans for cron configurations, worker queues, and scheduler libraries to document job schedules and error handling, and maps external integrations including authentication methods, resilience patterns, and coupling assessments.

What diagram types can the blueprint include?▼

The DIAGRAM_TYPE variable supports C4, UML, Flow, and Component diagrams at multiple abstraction levels, including high-level subsystem overviews, component interaction diagrams, and data flow diagrams reflecting the actual implementation.

When should I not use automated architecture documentation?▼

Avoid relying on it for greenfield design decisions before code exists, since it documents implemented patterns rather than proposing new ones. It also cannot capture business rationale behind decisions unless recorded in decision records or comments.

Related Skills

Explore More Software Engineering Skills→
EmeaAppGbbEmeaAppGbb

dependency-inventory

Identify and document project dependencies, versions, and purposes from manifests and lock files.

Official
Advanced
goodnight000goodnight000

code-review-excellence

Guide engineers through structured pull request reviews with actionable feedback.

Community
Basic
icartshicartsh
4

code-analyze

Analyze .NET solutions for code quality, security, and dependency issues.

Community
Advanced
Brave-LabsBrave-Labs

Dev10x-adr

Create Architecture Decision Records using project templates and PlantUML diagrams.

Official
Advanced