architect
Skill1 starsChanged 4 days agoMITView on GitHub
Decide repository-grounded architecture before blueprint planning; use for boundary, dependency-direction, state ownership, abstraction, consolidation, module or class structure, subsystems, or no-targets.
187 other projects use a version of this.
Adopted by
Most recently taken up by
- gfunc/skillstheir own version, first seen Nov 16, 2026
- RIJUDEVx/agent-skillstheir own version, first seen Nov 16, 2026
- fworks-tech/agenthoodtheir own version, first seen Nov 16, 2026
- shiwenbin1617/pstacktheir own version, first seen Nov 16, 2026
- jdonohoo/vern-bottheir own version, first seen Nov 15, 2026
- backnotprop/pstacktheir own version, first seen Nov 15, 2026
Used with
Projects with it also use ecosystem-reference, fractal-delegation 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.
naman10parikhSkillecosystem-reference
Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.
Also in 5 projects that use this
naman10parikhSkillfractal-delegation
Also in 5 projects that use this
tristanphvnSkillketchup-video
Catch the user up like /keel:ketchup, with a short silent video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.
Also in 14 projects that use this
jaydubya818Skillfigure-it-out
Use when novel or multi-phase work needs an auditable workflow and no narrower playbook fits.
Also in 55 projects that use this
ianclearySkillprinciple-explain-the-number
Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.
Also in 29 projects that use this
eryzerzSkillmake-bot-ui
Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.
Also in 20 projects that use this
- +6 more from naman10parikh
Other versions187 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 187
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- pascalorg/editor★ 26ksame name
- backnotprop/pstack★ 4.2ksame name
- agenticnotetaking/arscontexta★ 3.5ksame name
- jsmastery-pro/skills★ 1.4ksame name
- SethGammon/Citadel★ 927same name
- moeru-ai/xsai★ 667same name
- DanMcInerney/architect-loop★ 626same name
- Hainrixz/the-architect★ 562same name
177 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.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 175 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Stop at architecture. Never classify implementation tier, perform a full propagation sweep, prescribe file-level edits, write test or …
- Very specific: line 18
Follow Architecture Protocol.
- Distinctive: line 19
Use Bounded Delegation Protocol before any large sweep and for optional evidence workers or earned specialist review.
- Distinctive: line 21
Use Worked Example only for optional alternatives, user policy, or view calibration, and Calibration Examples before framing a target …
“Common” is measured: kept by at least 6 in 10 of the 175 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
Architect
Authority
Decide architecture. If no target is supplied, run Opportunity Discovery before selecting target, no-design-change, or blocker. Seal ignored .first-four-hours/architectures/<slug>/architecture.md for blueprint; do not edit implementation files.
Stop at architecture. Never classify implementation tier, perform a full propagation sweep, prescribe file-level edits, write test or execution blueprints, order migrations or rollout, or attack an implementation. Those responsibilities belong to blueprint. Paths and optional views are evidence bearings, not edit instructions.
Workflow
- Follow Architecture Protocol. Consult
reasonbefore committing to an approach, after a failure or direction change, and before sealing. Load Structural Techniques only where the protocol or discovery points to it. - Use Bounded Delegation Protocol before any large sweep and for optional evidence workers or earned specialist review.
- Draft from the Handoff Template.
- Use Worked Example only for optional alternatives, user policy, or view calibration, and Calibration Examples before framing a target inside one module or class or selecting any structure other than
no-design-change. - Seal once:
python /absolute/skill-root/scripts/cli.py --repo-root /absolute/repo \
--input draft=/absolute/architecture-draft.md \
--input slug=<architecture-slug> --format json runPersist settled structural truth: pressure or no-change outcome, owner/boundary, constraints, selected architecture, consequences, evidence, trust-relevant unknowns, and any user-owned policy.
Completion
Complete only when the command returns status: complete with result.path at .first-four-hours/architectures/<slug>/architecture.md; report result.git_ignored. If sealing fails, repair the named draft or workspace conflict and rerun. If evidence changed, refresh and seal against the new snapshot. Final and stop reports trace reason checkpoints per its Checkpoint trace. End with one optional next step fitting this outcome: a fenced, self-contained prompt naming any repository, issue, PR, or artifact it needs, or say none is needed. Only a "yes" starts it, via any skill it names, but the user runs a charter, diagnose, or ticket step as its /<skill> command.
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.

