project-architecture
Skill1 starsChanged 3 months agoMITView on GitHub
<project> system architecture and boundary invariants. Use when designing or touching module boundaries, public contracts, tenancy, persistence, or anything that crosses service lines. Enforces the invariants listed in AGENTS.md.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- luigi-dv/react-ts-vitetheir own version, first seen Oct 20, 2026
- BidingCC/BuildingAItheir own version, first seen Oct 8, 2026
- marwan562/agents-skillstheir own version, first seen Sep 19, 2026
- Jithnkn/project-architecturetheir own version, first seen Aug 20, 2026
- extra-org/extratheir own version, first seen Jun 8, 2026
- fqmyysjjd/agent-feedtheir own version, first seen May 9, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- BidingCC/BuildingAI★ 1.9ksame name
- extra-org/extra★ 120same name
- Jithnkn/project-architecture★ 8same name
- marwan562/agents-skills★ 8same name
- fqmyysjjd/agent-feed★ 4same name
- luigi-dv/react-ts-vite★ 1same name
- thetruong1099/android-mvi-base-code★ 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 repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- code-commenterSkill
- project-code-standardsSkill
- subagent-driven-developmentSkill
The file
Files
<project> architecture
Stub — fill this in. This is the on-demand half of
AGENTS.md: the invariants live there in one line each, and the reasoning, the examples, and the checklists live here. Rename the skill to your project (<project>-architecture) and update.claude/skills/README.md.
The shape
flowchart LR
A["<module A>"] --> B["<module B>"]
B --> C["<store>"]<Two paragraphs: what each component owns, and the one boundary that defines the system.>
Invariants, with their reasoning
1. <Invariant, stated as an absolute>
Why. <The failure this prevents, concretely.>
What violating it looks like. <The tempting shortcut a reviewer must recognize.>
The right fix instead. <Where the change belongs when someone reaches for the shortcut.>
2. <…>
Where things go
| Concern | Lives in | Never in |
<…> | <…> | <…> |
Design checklist for a cross-boundary change
<Does it move identity or tenancy? Then where does it come from?><Does it add a public contract? What must be regenerated in the same PR?><Does it need an ADR? (multi-module, non-obvious trade-off, sensitive path)>
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.

