architect-review
Skill1 starsChanged 2 months agoMITView on GitHub
Review a design, PR, or proposal as a Staff Solution Architect — simplicity, scalability, event-driven boundaries, security, cost, compliance, operability — ending in a prioritized must/should/nice list.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- aiqianqian521/architect-skillstheir own version, first seen Nov 1, 2026
- ya222/skillforgetheir own version, first seen Oct 20, 2026
- xfstudio/skillstheir own version, first seen Oct 13, 2026
- Tgoldi/claude-skillstheir own version, first seen Oct 13, 2026
- garthcodes/claude-skillstheir own version, first seen Oct 8, 2026
- LucaDominici/arbitertheir own version, first seen Sep 20, 2026
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- kumaran-is/claude-code-onboarding★ 35same name
- xfstudio/skills★ 9same name
- bis-code/claude-toolkit★ 8same name
- hlhr202/swe-skills★ 3same name
- ai4brands-design/claude-skills★ 2same name
- Aver005/agent-skills★ 2same name
- garthcodes/claude-skills★ 2same name
- aiqianqian521/architect-skills★ 1same name
- alex-macra/claude-codex-skills-assembly★ 1same name
- aptitude-stack/registery★ 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 repository28 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- article-writingSkill
- changelog-watchSkill
- coordinator-workersSkill
- cost-forecastSkill
- design-docSkill
- documentSkill
- ea-briefingSkill
- estimateSkill
- eval-toolSkill
- gh-ticketsSkill
- headless-loopSkill
- interview-guideSkill
- job-supervisorSkill
- market-researchSkill
- meeting-notesSkill
- migration-planSkill
- obsidian-noteSkill
- plan-to-issuesSkill
- postmortemSkill
- readSkill
- release-notesSkill
- skill-stocktakeSkill
- slide-deckSkill
- status-reportSkill
- threat-modelSkill
- tradeoff-tableSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
0
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 9
Read ./CONTEXT.md if present.
“Common” is measured: kept by at least 6 in 10 of the 14 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
Read ./CONTEXT.md if present. Adopt the persona of an experienced Staff Solution Architect;
take the stack, domain, constraints, and compliance requirements from ./CONTEXT.md rather than
assuming them.
Review $ARGUMENTS across: (1) simplicity / over-engineering — invoke the ponytail-review
skill; (2) scalability & failure modes; (3) event-driven boundaries (sync vs async, outbox/saga
where relevant); (4) security (delegate to the threat-model skill if deep); (5) cost &
operational burden; (6) compliance — data residency, regulated data, self-hosting, as
CONTEXT.md or the working agreement define them. End with a prioritized list
(must-fix / should-fix / nice-to-have) and, if a real decision was made, offer to capture it
via the domain-modeling skill.
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.

