architecture-review
Skill4 starsChanged 6 months agoApache-2.0View on GitHub
Review layer separation, design patterns, DI, and module boundaries
Files
Review code architecture and design patterns.
What it checks
- Layer separation (controller → service → repository)
- Dependency injection usage
- Module boundaries (no cross-boundary DB access)
- Single responsibility (line limits, god class detection)
- Composition over inheritance
For full instructions, read agents/architecture-review.md.
Other versions69 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 69
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- langwatch/langwatch★ 5ksame name
- microsoft/hve-core★ 1.6ksame name
- ghuntley/loom★ 1.4ksame name
- DataDog/dd-trace-js★ 839same name
- decebals/claude-code-java★ 763same name
- borgbase/vykar★ 713same name
- appdevforall/CodeOnTheGo★ 457same name
- getsentry/warden★ 421same name
- owainlewis/blueprint★ 413same name
59 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.
Used alongsideProjects with it also use create-stories, story-done and 10 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.
lilangMaxSkillcreate-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Also in 11 projects that use this
- lilangMaxSkill
story-done
End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.
Also in 11 projects that use this
- +10 more from lilangMax
In this repository54 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/code-review.mdcCursor rule
- .cursor/rules/db-design.mdcCursor rule
- .cursor/rules/debug.mdcCursor rule
- .cursor/rules/django-forge.mdcCursor rule
- .cursor/rules/dotnet-forge.mdcCursor rule
- .cursor/rules/flutter-forge.mdcCursor rule
- .cursor/rules/nestjs-forge.mdcCursor rule
- .cursor/rules/neuraforge.mdcCursor rule
- .cursor/rules/pr-review.mdcCursor rule
- .cursor/rules/react-forge.mdcCursor rule
- .cursor/rules/refactor.mdcCursor rule
- .cursor/rules/rn-forge.mdcCursor rule
- .cursor/rules/scaffold.mdcCursor rule
- .cursor/rules/spring-forge.mdcCursor rule
- .cursor/rules/test-forge.mdcCursor rule
- api-designSkill
- api-testingSkill
- changelogSkill
- codebase-graphSkill
- code-reviewSkill
- db-designSkill
- debugSkill
- deps-auditSkill
- design-syncSkill
- devils-advocateSkill
- devopsSkill
- django-forgeSkill
- doc-generatorSkill
- documentationSkill
- domain-setupSkill
- dotnet-forgeSkill
- explainSkill
- feature-pipelineSkill
- flutter-forgeSkill
- fullstack-orchestratorSkill
- git-worktreesSkill
- load-testingSkill
- migrateSkill
- nestjs-forgeSkill
- performance-reviewSkill
- presentation-builderSkill
- product-managerSkill
- pr-reviewSkill
- react-forgeSkill
- refactorSkill
- rn-forgeSkill
- scaffoldSkill
- security-reviewSkill
- spring-forgeSkill
- test-forgeSkill
- ui-validationSkill
- video-creatorSkill
- workspace-protocolSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.