跳至主要内容
小龙虾小龙虾AI
🤖

OpenClaw Optimised

Guide for writing and optimizing CLAUDE.md files for maximum Claude Code performance. Use when creating new CLAUDE.md, reviewing existing ones, or when user asks about CLAUDE.md best practices. Covers structure, content, pruning, and common mistakes.

下载5.4k
星标9
版本1.0.1
写作创作
安全通过

技能说明


name: claude-optimised description: Guide for writing and optimizing CLAUDE.md files for maximum Claude Code performance. Use when creating new CLAUDE.md, reviewing existing ones, or when user asks about CLAUDE.md best practices. Covers structure, content, pruning, and common mistakes.

CLAUDE.md Optimization Guide

Write CLAUDE.md files that maximize Claude's adherence and performance.

Core Principle: Less Is More

Long CLAUDE.md = Claude ignores half of it. Critical rules get lost in noise.

For each line ask: "Would removing this cause Claude to make mistakes?"

  • If no → delete it
  • If Claude already does it correctly → delete it or convert to hook

What to Include

Essential (High Value)

SectionExample
Project context"Next.js e-commerce app with Stripe" (1 line)
Build/test commandsnpm run test, pnpm build
Critical gotchas"Never modify auth.ts directly"
Non-obvious conventions"Use vi for state, not useState"
Domain terminology"PO = Purchase Order, not Product Owner"

Include Only If Non-Standard

  • Branch naming (if not feature/, fix/)
  • Commit format (if not conventional commits)
  • File boundaries (sensitive files to avoid)

Do NOT Include

  • Things Claude already knows (general coding practices)
  • Obvious patterns (detectable from existing code)
  • Lengthy explanations (be terse)
  • Aspirational rules (only real problems you've hit)

Structure

# Project Name

One-line description.

## Commands
- Test: `npm test`
- Build: `npm run build`
- Lint: `npm run lint`

## Code Style
- [Only non-obvious conventions]

## Architecture
- [Brief, only if complex]

## IMPORTANT
- [Critical warnings - use sparingly]

Formatting Rules

  • Bullet points over paragraphs
  • Markdown headings to separate modules (prevents instruction bleed)
  • Specific over vague: "2-space indent" not "format properly"
  • IMPORTANT/YOU MUST for critical rules (use sparingly or loses effect)

File Placement

LocationScope
~/.claude/CLAUDE.mdAll sessions (user prefs)
./CLAUDE.mdProject root (share via git)
./subdir/CLAUDE.mdLoaded when working in subdir
.claude/rules/*.mdAuto-loaded as project memory

Optimization Checklist

Before finalizing:

  • Under 50 lines? (ideal target)
  • Every line solves a real problem you've encountered?
  • No redundancy with other CLAUDE.md locations?
  • No instructions Claude follows by default?
  • Tested by observing if Claude's behavior changes?

Maintenance

  • Run /init as starting point, then prune aggressively
  • Every few weeks: "Review this CLAUDE.md and suggest removals"
  • When Claude misbehaves: add specific rule
  • When Claude ignores rules: file too long, prune other content

Anti-Patterns

Don'tWhy
200+ line CLAUDE.mdGets ignored
"Write clean code"Claude knows this
Duplicate rules across filesWastes tokens, conflicts
Theoretical concernsOnly add for real problems
Long prose explanationsUse bullet points

Example: Minimal Effective CLAUDE.md

# MyApp

React Native app with Expo. Backend is Supabase.

## Commands
- `pnpm test` - run tests
- `pnpm ios` - run iOS simulator

## Style
- Prefer Zustand over Context
- Use `clsx` for conditional classes

## IMPORTANT
- NEVER commit .env files
- Auth logic lives in src/lib/auth.ts only

~15 lines. Covers what Claude can't infer. Nothing more.

如何使用「OpenClaw Optimised」?

  1. 打开小龙虾AI(Web 或 iOS App)
  2. 点击上方「立即使用」按钮,或在对话框中输入任务描述
  3. 小龙虾AI 会自动匹配并调用「OpenClaw Optimised技能完成任务
  4. 结果即时呈现,支持继续对话优化

相关技能