architecture-review-techniques
Skill45 starsChanged 4 months agoApache-2.0View on GitHub
Deep investigation techniques for architecture reviews — import chain tracing, constructor audits, error propagation, cross-reference validation, test hygiene. Load during pipeline reviews or detailed architectural analysis.
In this repository2 other files it gives its agents.
- .cursor/rules/engineering-standards.mdCursor rule
- codebase-overviewSkill
The file
Files
Architecture Review Techniques
Universal engineering standards (SOLID, hexagonal architecture, Pydantic, enums,
types, imports, naming, error handling, Python safety) are always active via
.cursor/rules/engineering-standards.md — no manual loading needed.
For deep investigation techniques needed during reviews, load
references/investigation-techniques.md.
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.