architecture-review
Skill0 starsChanged 15 days agoMITView on GitHub
Review a design or a change for structural fit: tenancy, access, data flow, sync and coupling. Use before a large feature or for a structural change.
84 other projects use a version of this.
Adopted by
Most recently taken up by
- erikperttu/steering-coding-agentstheir own version, first seen Nov 16, 2026
- Sequela02/canastatheir own version, first seen Nov 15, 2026
- OmarAlex24/audit-skillstheir own version, first seen Nov 15, 2026
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- myshra777-ai/garudatheir own version, first seen Nov 15, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Nov 9, 2026
Used with
Projects 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
lilangMaxSkillstory-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
Other versions84 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 84
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- langwatch/langwatch★ 5ksame name
- ghuntley/loom★ 1.7ksame name
- microsoft/hve-core★ 1.6ksame name
- DataDog/dd-trace-js★ 840same name
- decebals/claude-code-java★ 763same name
- borgbase/vykar★ 722same name
- appdevforall/CodeOnTheGo★ 586same name
- owainlewis/blueprint★ 432same name
- getsentry/warden★ 424same name
74 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 repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- bootstrap-projectSkill
- capture-screenshotsSkill
- customizeSkill
- deliver-featureSkill
- design-reviewSkill
- docs-upkeepSkill
- fix-bugSkill
- handoffSkill
- implementSkill
- leadSkill
- log-decisionSkill
- refine-requirementsSkill
- release-readinessSkill
- reproduce-in-worktreeSkill
- security-auditSkill
- ship-prSkill
- start-taskSkill
- sync-branchSkill
- threat-modelSkill
- verify-featureSkill
- vet-dependencySkill
- write-adrSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 76 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Read first: the relevant ADRs, the Architecture & Data Model doc, AGENTS.md, and for a PR the diff plus the code it touches.
- Distinctive: line 18
Tenancy and access: every new row and object is scoped to the tenant.
- Distinctive: line 24
Performance shape: no always-on work, budgets known, heavy work off the UI thread.
“Common” is measured: kept by at least 6 in 10 of the 76 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 review
Playbook files named here: when the project has its own copy at
.playbook/local/<same path>, use that copy instead.
Scope: $ARGUMENTS
Read first: the relevant ADRs, the Architecture & Data Model doc, AGENTS.md, and for a PR the diff plus the code it touches. Principles: ${CLAUDE_PLUGIN_ROOT}/principles/02-architecture.md and 09-data-and-migrations.md.
Check
- Fit with decisions: does it follow the ADRs? If it departs from one, is that intended (and then a new ADR is needed)?
- Tenancy and access: every new row and object is scoped to the tenant; access is enforced at the data layer with tests; server-only values are fetched online.
- Boundaries: one client per service; layers depend one way; no reaching into another feature's internals; shared rules have one home.
- Data flow: query keys scoped by tenant and by user; writes are idempotent with client ids; offline writes go through the durable queue if the product needs it; there's a single retry layer; live updates invalidate; nothing shows "empty" before data arrives.
- Time: UTC instants plus zones, calendar dates as dates, the shared time module, and entry in the zone where the event happens.
- Lifecycle: soft delete and purge, files follow rows, server-stamped fields, idempotent and re-plannable jobs.
- Product hooks: entitlement checks on costly creates, configuration as data, privacy by construction.
- Performance shape: no always-on work, budgets known, heavy work off the UI thread.
- Evolution: old clients keep working through the migration; the change is reversible or forward-fixable.
Output
- Verdict: fits / fits with changes / needs an ADR first.
- Findings, ranked: each with the concrete risk (scenario → consequence), the principle it breaks, and the suggested change. No style preferences.
- Decisions needed: for the owner (product) or for an ADR (technical).
- Offer to file the findings as tickets.
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.

