architecture-blueprint-generator
Skill0 starsChanged 5 months agoMITView on GitHub
Analyze a codebase and generate Project_Architecture_Blueprint.md — detected stacks and architecture patterns, diagrams, layers, cross-cutting concerns, extension guidance. Use to document, map, or blueprint a project's architecture or keep it consistent.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- AgnesAI-Labs/agnet-skills-cntheir own version, first seen Nov 1, 2026
- github/awesome-copilottheir own version, first seen Oct 25, 2026
- 302ai/302-AI-Studiotheir own version, first seen Oct 8, 2026
- Adhamxon/claude-code-skillstheir own version, first seen Jul 30, 2026
- ReaperOAK/ForgeOStheir own version, first seen Jun 8, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- github/awesome-copilot★ 41ksame name
- 302ai/302-AI-Studio★ 133same name
- Adhamxon/claude-code-skills★ 2same name
- AgnesAI-Labs/agnet-skills-cn★ 1same name
- ReaperOAK/ForgeOS★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository63 other files it gives its agents.
- .claude/skills/nestjs-best-practices/AGENTS.mdAGENTS.md
- accessibility-a11ySkill
- backend-delivery-loopSkill
- backend-designSkill
- backend-dev-guidelinesSkill
- backend-testingSkill
- backend-to-frontend-handoff-docsSkill
- building-componentsSkill
- bullmq-specialistSkill
- canvas-designSkill
- code-patternsSkill
- components-composition-patternsSkill
- conventional-commitSkill
- core-web-vitalsSkill
- create-svgSkill
- css-architectureSkill
- cypress-authorSkill
- cypress-docsSkill
- cypress-explainSkill
- delivery-loop-retroSkill
- diagnoseSkill
- fastify-best-practicesSkill
- figma-code-connectSkill
- frontend-delivery-loopSkill
- frontend-fundamentalsSkill
- fullstack-delivery-loopSkill
- grill-meSkill
- hunt-race-conditionSkill
- impeccableSkill
- mermaid-diagramsSkill
- nestjs-best-practicesSkill
- nextjs-best-practicesSkill
- nextjs-performanceSkill
- nodejs-backend-patternsSkill
- owasp-security-reviewSkill
- performance-hunterSkill
- playwright-best-practicesSkill
- postgresql-code-reviewSkill
- postgresql-optimizationSkill
- postmanSkill
- prisma-postgresSkill
- pro-state-machineSkill
- race-conditionSkill
- react-best-practicesSkill
- react-performanceSkill
- react-querySkill
- redis-coreSkill
- redis-query-engineSkill
- redis-securitySkill
- refactorSkill
- review-panelSkill
- run-delivery-chainSkill
- spec-drivenSkill
- sql-optimizationSkill
- system-designSkill
- testing-strategySkill
- tune-skills-and-agentsSkill
- ui-ux-pro-maxSkill
- vercel-react-view-transitionsSkill
- viteSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 45
Read a reference only when writing that part of the blueprint:
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Project Architecture Blueprint Generator
Analyze the architectural patterns actually implemented in the codebase and write a
comprehensive Project_Architecture_Blueprint.md that serves as the definitive reference for
maintaining architectural consistency and guiding new development. Document what the code
does, not theoretical patterns — every claim should trace to project structure, dependencies,
or configuration.
Options
Defaults below; adjust any of them when the user specifies:
| Option | Default | Alternatives |
| Technology stack | Auto-detect | .NET, Java, React, Angular, Python, Node.js, Flutter, … |
| Architecture pattern | Auto-detect | Clean, Microservices, Layered, MVVM, MVC, Hexagonal, Event-Driven, Serverless, Monolithic, … |
| Diagrams | C4 | UML, Flow, Component, none (textual description instead) |
| Detail level | Detailed | High-level, Comprehensive, Implementation-Ready |
| Optional sections | All included | Drop implementation patterns, extensibility, code examples, or ADRs on request |
Workflow
- Detect — identify the stack(s) and architectural pattern(s) from project/config files,
dependencies, folder organization, and dependency flow (detection signals in
references/blueprint-structure.md§1). - Write the core sections — overview, visualization, components, layers, data
architecture, cross-cutting concerns, service communication, testing, deployment,
governance, and the blueprint-for-new-development guide, following
references/blueprint-structure.mdsection by section. - Add the per-stack section for each detected technology, using the checklists in
references/technology-patterns.md. - Add the optional sections that apply — implementation patterns, extension/evolution
guidance, code examples, ADRs — per
references/optional-sections.md. - Close with the generation date and recommendations for keeping the blueprint updated as the architecture evolves.
References
Read a reference only when writing that part of the blueprint:
references/blueprint-structure.md— the 12 core sections in full: detection signals, per-section content checklists, the new-development guide · read in step 2.references/technology-patterns.md— stack-specific pattern checklists (.NET, Java, React, Angular, Python + how to derive others) · read in step 3.references/optional-sections.md— implementation patterns, extension/evolution patterns, code examples, ADRs · read in step 4.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

