architecture-audit
Skill1 starsChanged 3 months agoMITView on GitHub
Perform a read-only architecture inventory and dependency analysis for frontend, backend, security, RAG, repository, or deployment concerns. Use before cross-cutting implementation, migrations, or architecture decisions that need ownership, coupling, risk, and phased recommendations. Do not use to edit code, execute a refactor, review commits, or produce a task handoff.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- harshitsinghbhandari/domain-expansiontheir own version, first seen Nov 8, 2026
- MarieLynneBlock/arcanum-artifextheir own version, first seen Nov 1, 2026
- RBraga01/a-teamtheir own version, first seen Nov 1, 2026
- helderberto/agent-skillstheir own version, first seen Oct 11, 2026
- Suge8/friedbuntheir own version, first seen Oct 11, 2026
- Vincweb/caudron-plugintheir own version, first seen Oct 9, 2026
Used with
Projects with it also use prototype, review and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkillprototype
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 3 projects that use this
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- RBraga01/a-team★ 24same name
- helderberto/agent-skills★ 19same name
- Suge8/friedbun★ 13same name
- creativedeals/free-claude-skill-architecture-audit★ 4same name
- MarieLynneBlock/arcanum-artifex★ 4same name
- gootf/software-agent-sop★ 2same name
- harshitsinghbhandari/domain-expansion★ 2same name
- seikaikyo/dash-skills★ 2same name
- InsightStudio-2026/agent-assets★ 1same name
- MKAbuMattar/skills★ 1same name
5 more not listed
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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- commit-reviewSkill
- cxpSkill
- docs-updateSkill
- safe-refactorSkill
- session-handoffSkill
- task-briefSkill
- cxpSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
9
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 16
Use for a read-only architecture audit of one or more named surfaces: frontend, backend/domain logic, security, RAG, repository structure, …
- Distinctive: line 21
Do not use for ordinary file discovery, implementation, refactor execution, documentation synchronization, commit review, or handoff …
- Distinctive: line 55
Do not modify, stage, commit, run migrations, install dependencies, or call paid providers.
- Distinctive: line 57
Do not inspect or print credential values.
- Distinctive: line 58
Do not claim runtime behavior from static inspection alone.
- Distinctive: line 59
Do not present a proposed future architecture as current.
- Distinctive: line 60
Keep recommendations within the audited surface and explicit non-goals.
- Distinctive: line 65
Verify cited paths and separate code evidence, test evidence, documentation, runtime evidence, and inference.
- Distinctive: line 67
Check that every proposed phase protects named behavior and has validation and rollback criteria.
“Common” is measured: kept by at least 6 in 10 of the 10 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
Architecture Audit
Purpose
Map the current architecture from repository evidence before implementation. Explain ownership, dependencies, coupling, boundaries, and risks without editing the repository.
Trigger
Use for a read-only architecture audit of one or more named surfaces: frontend, backend/domain logic, security, RAG, repository structure, or deployment.
Do not trigger
Do not use for ordinary file discovery, implementation, refactor execution, documentation synchronization, commit review, or handoff generation.
Inputs
- Audit question, included surfaces, and explicit exclusions.
- Repository instructions, branch state, and relevant source and tests.
- Known runtime evidence, documentation, and prior audits.
- Constraints for compatibility, behavior, security, and deployment.
Workflow
- Establish the audit boundary and remain read-only.
- Inventory relevant entry points, modules, configuration, tests, assets, and operational files.
- Trace imports, calls, data flow, shared state, provider edges, persistence, and deployment dependencies relevant to the question.
- Assign each responsibility to its current owner and distinguish intended boundaries from observed coupling.
- Record behavior and architecture facts with file evidence; label inference and unknowns explicitly.
- Identify concentration points, cycles, hidden state, unsafe trust boundaries, test gaps, and migration constraints.
- Recommend ordered, behavior-preserving phases with prerequisites, validation, risks, and rollback points. Do not implement them.
Outputs
Return the inventory, dependency map, ownership map, coupling analysis, risks, and phased recommendations using the architecture audit format.
Safety
- Do not modify, stage, commit, run migrations, install dependencies, or call paid providers.
- Do not inspect or print credential values.
- Do not claim runtime behavior from static inspection alone.
- Do not present a proposed future architecture as current.
- Keep recommendations within the audited surface and explicit non-goals.
Validation
- Cross-check important dependencies in both directions where practical.
- Verify cited paths and separate code evidence, test evidence, documentation, runtime evidence, and inference.
- Check that every proposed phase protects named behavior and has validation and rollback criteria.
- Report excluded or inaccessible surfaces as unverified.
References
AGENTS.md— repository boundaries and safety rules.docs/agents/README.md— tooling ownership.- Architecture audit format — output structure and surface checklist.
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.

