claude-guardian
Skill9 starsChanged 7 months agoMITView on GitHub
Validate and place rules into the correct CLAUDE.md or config file. Two modes: enhance-and-place a rough rule idea, or audit all config files for misplaced rules. Use when adding conventions, after editing CLAUDE.md, or when unsure where a rule belongs.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- DUNHKpcc/Claude-Guardiantheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- DUNHKpcc/Claude-Guardian★ 2.1ksame 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 repository44 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- anthropic-multi-agent-research-system-skillSkill
- apply-selectionsSkill
- bootstrap-dogfood-projectSkill
- brainstormSkill
- branch-choiceSkill
- cc-adoption-scoutSkill
- continueSkill
- end-sessionSkill
- executing-plansSkill
- five-advisorsSkill
- get-work-doneSkill
- git-branch-lifecycleSkill
- githubSkill
- grill-meSkill
- hook-transcript-fixture-testSkill
- instagramSkill
- linkedinSkill
- modern-data-pipeline-diagramSkill
- pattern-qualitySkill
- platform-event-live-probeSkill
- plugin-lifecycleSkill
- promote-to-coreSkill
- prompt-auto-enhanceSkill
- provision-reportSkill
- redditSkill
- review-new-claude-featuresSkill
- save-sessionSkill
- scan-discovery-reportSkill
- scan-repoSkill
- scan-urlSkill
- self-improveSkill
- skill-evaluatorSkill
- skill-masterSkill
- ssot-workflow-auditSkill
- start-sessionSkill
- synthesize-hubSkill
- synthesize-projectSkill
- twitter-xSkill
- verify-effect-at-destinationSkill
- workflow-doc-reviewerSkill
- writing-plansSkill
- writing-skillsSkill
- youtube-transcriptSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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
- Distinctive: line 55
Read the target file
- Distinctive: line 57
Add the rule without disrupting existing content
- Very specific: line 65
Read all CLAUDE.md, CLAUDE.local.md, and .claude/rules/*.md files.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Claude Guardian — Config Rule Placement & Audit
Enhance rough rule ideas into well-structured rules and place them in the correct config file. Audit all config files to catch accidental deletions, misplacements, and protected section violations.
Arguments: $ARGUMENTS
MODE SELECTION
$ARGUMENTScontainsaudit→ Mode 2: Audit & Guard- Otherwise → Mode 1: Enhance & Place (treat
$ARGUMENTSas the rough rule text)
CONFIG FILE LOCATIONS
| File | Scope | Content Type | Examples |
~/.claude/CLAUDE.md | ALL projects globally | Generic cross-project rules | "Always use forward slashes in bash" |
~/.claude/CLAUDE.local.md | All projects globally (private) | Personal preferences | "I prefer verbose test output" |
CLAUDE.md (project root) | This project only | Project-specific rules, architecture | Build commands, file structure |
CLAUDE.local.md (project root) | This project only (gitignored) | Local project preferences | Local env paths, personal shortcuts |
.claude/rules/*.md | This project, path-scoped | Detailed technical rules | Framework patterns, testing rules |
STEP 1: Enhance & Place
Step 1: Analyze the Rule
- Parse the rough rule text
- Determine scope: global, project, or path-specific
- Identify the correct target file
Step 2: Enhance the Rule
Transform rough text into structured format:
- Clear, actionable statement
- Example (if applicable)
- Rationale (brief)
Step 3: Place the Rule
- Read the target file
- Find the appropriate section
- Add the rule without disrupting existing content
- Report what was added and where
STEP 2: Audit
Step 1: Read All Config Files
Read all CLAUDE.md, CLAUDE.local.md, and .claude/rules/*.md files.
Step 2: Check for Issues
- Deletions: Compare against git history for accidentally removed rules
- Misplacements: Rules in wrong scope (global rule in project file, etc.)
- Duplicates: Same rule in multiple files
- Conflicts: Contradictory rules
Step 3: Report
Audit Results:
Files checked: N
Issues found: M
- [issue type]: [description] in [file]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.

