Claude代码蓝图

Installs globally for every project

mkdir -p ~/.claude && curl -o ~/.claude/CLAUDE.md https://raw.githubusercontent.com/faizkhairi/claude-code-blueprint/main/CLAUDE.md

That gives Claude Code four behavioral rules that prevent the most common AI coding mistakes: **Verify-After-Complete** · **Diagnose-First** · **Plan-First** · **Verify-Before-Exit-Plan**, applied to every project on your machine. That's the whole first step; try it, then come back for more. See [where config belongs](GETTING-STARTED.md#where-config-belongs-project-vs-personal) if you also want project-specific conventions.

<details>
<summary><strong>Want more than CLAUDE.md?</strong> (hooks, agents, settings)</summary>

Once CLAUDE.md is working, add the rest. Easiest path: run the installer from a cloned/forked copy:

Or let Claude do it: paste into a Claude Code session: "Set up the Claude Code Blueprint. Install CLAUDE.md to ~/.claude/CLAUDE.md, set up hooks and settings in ~/.claude/. Show me each step."

For every install option (fork / clone / cherry-pick / presets) plus a verification checklist, see SETUP.md. </details>

New to Claude Code, or want the guided version? The beginner guide walks you through the same thing step by step. Curious who this is for? See Who Is This For below.

---

Getting Started

Quick Start above is the fast path: copy CLAUDE.md and you're going in 60 seconds. For the next step, pick the doc that fits you: new to Claude Code? Read GETTING-STARTED.md (concepts + a guided walkthrough). Just want the install commands and presets? Go straight to SETUP.md (every option + a verification checklist).

Then grow into the rest with this order:

Quick Start

Do this first. Install one file and you're done in 60 seconds:

```bash

Recommended adoption path

1. Start with CLAUDE.md: the behavioral rules template. Biggest impact with zero setup.
2. Add 2-3 hooks: protect-config.sh + notify-file-changed.sh + cost-tracker.sh. Copy to ~/.claude/hooks/ and wire into settings.json.
3. Read WHY.md to understand the reasoning; adapt, don't blindly copy.
4. Add agents as your workflow matures, starting with verify-plan and code-reviewer.
5. Set up the memory system when you need cross-session persistence, opt-in during ./setup.sh (answer Y).

---

Common Questions

Works with my framework? Yes. The blueprint is framework-agnostic: it configures Claude Code, not your stack. More...

Too advanced for me? No. Start with one file (CLAUDE.md). Add more only when you need it. More...

Which plan do I need? Works on Pro, Max, Team, Enterprise, and API. Hooks are free on all plans. More...

A colleague sent you this? Start here: quickstart for referrals.

---

<details> <summary><strong>Plugin Compatibility</strong></summary>

&nbsp;

This blueprint is designed as a standalone configuration; no plugins required. In fact, plugins can interfere with a custom setup:

Known issues: - Plugins that modify CLAUDE.md may overwrite your custom behavioral rules - Plugins that add hooks on the same events (e.g., Stop, PreToolUse) will stack with your hooks; this can cause slowdowns or conflicting instructions - Plugins that inject context consume tokens from your context window, leaving less room for your agents and memory system - MCP server plugins work well alongside this setup: they add tools, not rules, so there's no conflict

Recommendation: If you adopt this blueprint, audit your installed plugins and disable any that: 1. Override CLAUDE.md or settings.json hooks 2. Inject prompts on SessionStart (conflicts with your session-lifecycle rule) 3. Add broad permissions that bypass your permission restrictions

Custom setup > generic plugins, because your setup encodes YOUR project's domain knowledge. A plugin can't know your architecture, your team's conventions, or your production constraints.

</details>

---