architecture-guardian
Skill5 starsChanged 4 months agoMITView on GitHub
Use in Claude Code before non-trivial features, refactors, cross-module fixes, new capabilities, dependencies, schema changes, public API changes, or contract-governed edits. Requires discovery, reuse-first search, reviewed scope, baseline-aware classification, and a final architecture check.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- kbourzayq/arch-guardtheir own version, first seen Nov 8, 2026
- imMamdouhaboammar/riqortheir own version, first seen Aug 9, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- imMamdouhaboammar/riqor★ 4same name
- kbourzayq/arch-guard★ 2same 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- agent-kernelSkill
- architecture-guardianSkill
- agent-kernelSkill
- agent-kernelSkill
- agent-kernel-evolveSkill
- agent-kernel-opsSkill
- architecture-guardianSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 12 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
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
- Distinctive: line 15
Read CLAUDE.md, AGENTS.md, and the current architecture policy.
- Distinctive: line 18
Search reuse candidates before creating a parallel capability.
- Distinctive: line 19
Create or validate a change contract for non-trivial work.
- Distinctive: line 20
Keep Write, Edit, and MultiEdit operations inside the reviewed scope.
- Very specific: line 21
Run agent-kernel architecture check .
- Distinctive: line 23
Use only scoped, owned, expiring exceptions.
- Distinctive: line 47
Do not enable strict mode before policy, baseline, contract, and exception review.
- Distinctive: line 51
Do not create a second source of truth without evidence.
- Distinctive: line 52
Do not move business rules into UI, transport, persistence, provider, or framework layers.
- Distinctive: line 53
Do not bypass a public interface to reach infrastructure.
- Distinctive: line 54
Do not broaden a contract because implementation drifted.
- Distinctive: line 55
Do not let a hook mutate policy, approve exceptions, or publish memory.
- Distinctive: line 56
Do not treat baseline findings or expired exceptions as authorization for new violations.
- Very specific: line 58
Read docs/ARCHITECTURE_GUARDIAN.md,
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Architecture Guardian for Claude Code
The canonical workflow lives in skills/architecture-guardian/SKILL.md.
Required sequence
- Read
CLAUDE.md,AGENTS.md, and the current architecture policy. - Run
agent-kernel architecture doctor . --json. - Run
agent-kernel architecture discover . --json. - Search reuse candidates before creating a parallel capability.
- Create or validate a change contract for non-trivial work.
- Keep Write, Edit, and MultiEdit operations inside the reviewed scope.
- Run
agent-kernel architecture check . --jsonbefore commit. - Separate baseline debt from new regressions.
- Use only scoped, owned, expiring exceptions.
- Capture repeated architecture failures as Failure Lessons.
agent-kernel architecture reuse "<capability>" . --json
agent-kernel architecture contract init . \
--task "<task>" \
--owner "<owner>" \
--allow "src/area/**,test/area/**" \
--expect "src/area/file.ts,test/area/file.test.ts" \
--tests "<behavior>"
agent-kernel architecture check . --jsonClaude scope hook
Configure a narrow PreToolUse hook for Write|Edit|MultiEdit that calls agent-kernel-architecture-hook.
Review mode reports without denying. Strict mode is explicit:
AGENT_KERNEL_ARCHITECTURE_MODE=strict agent-kernel architecture check . --jsonDo not enable strict mode before policy, baseline, contract, and exception review.
Hard boundaries
- Do not create a second source of truth without evidence.
- Do not move business rules into UI, transport, persistence, provider, or framework layers.
- Do not bypass a public interface to reach infrastructure.
- Do not broaden a contract because implementation drifted.
- Do not let a hook mutate policy, approve exceptions, or publish memory.
- Do not treat baseline findings or expired exceptions as authorization for new violations.
Read docs/ARCHITECTURE_GUARDIAN.md, docs/architecture-guardian/COMMAND_REFERENCE.md, and docs/hooks/CLAUDE_HOOKS_BEST_PRACTICES.md.
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.

