A masterpiece of CLAUDE.md, maximize Claude Code proficiency
SaferSkills independently audited golden-CLAUDE.md (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
English | 中文
A copy-paste-ready behavioral template for Claude Code. Research-backed. Operational. Under 100 lines.
Distilled from 30+ of the most successful CLAUDE.md files, blog posts, and Anthropic's own documentation into one firm, general-purpose set of behavioral rules.
Install (recommended) — apply globally as your default Claude Code behavior:
mkdir -p ~/.claude && curl -o ~/.claude/CLAUDE.md https://raw.githubusercontent.com/Z-M-Huang/golden-CLAUDE.md/main/CLAUDE.mdThis is the recommended approach. Behavioral rules are universal — they don't change per project, so user scope (~/.claude/CLAUDE.md) is the natural home. Your project-root CLAUDE.md stays free for project-specific context (tech stack, test commands, conventions).
Share with your team — commit to your repository as a rules file:
mkdir -p .claude/rules && curl -o .claude/rules/golden.md https://raw.githubusercontent.com/Z-M-Huang/golden-CLAUDE.md/main/CLAUDE.mdUsing .claude/rules/ instead of the project root keeps the behavioral rules separate from project context. Claude Code loads both automatically.Existing CLAUDE.md — paste the golden rules at the top of your file, above your project-specific rules. Behavioral rules go first for maximum attention budget.
If your combined CLAUDE.md exceeds ~120 lines, consider splitting: behavioral rules in~/.claude/CLAUDE.md, project-specific rules in./CLAUDE.md. See the wiki for details.
| Section | Purpose |
|---|---|
| Core Commitments | 6 core commitments — verification, honesty, tool-backed facts, diligence, code understanding, safety |
| Before Changing Code | Pre-edit checklist — read first, check existing patterns, never assume |
| Honesty & Communication | Anti-sycophancy, surface confusion, push back on bad ideas |
| Verification & Quality | Smallest effective change, reviewable steps, Chesterton's fence, prefer editing over creating |
| Critical Evaluation | Falsify before endorsing, visible Risk section, inverted non-trivial default, no generic warnings |
| Safety & Boundaries | Consolidated destructive-action guard, secrets protection, permission-scope clarification |
| Discipline | No shortcuts, no over-engineering, crashes are data, root-cause investigation |
| Response Style | Caveman Lite — drop filler/hedging, keep articles and full sentences, auto-expand for safety |
| Communication & Proposals | Show don't tell — code examples, before/after diffs, ASCII diagrams, comparison tables |
This template is behavioral only. It does not include:
eslint, prettier, ruff)CLAUDE.md rules are defense-in-depth, not a security guarantee. Be aware:
These rules measurably improve compliance. They do not eliminate risk.
Visit the wiki for deep dives:
Open an issue or PR. Every proposed rule change must justify its attention budget cost — one line added means one line of compliance pressure on every other rule.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.