使唤它的窍门

先看下面这块原始片段，等会儿再回头看解释会顺得多。

read /src/auth and understand how we handle sessions and login.
also look at how we manage environment variables for secrets.

先看下面这块原始片段，等会儿再回头看解释会顺得多。

I want to add Google OAuth. What files need to change?
What's the session flow? Create a plan.

先看下面这块原始片段，等会儿再回头看解释会顺得多。

implement the OAuth flow from your plan. write tests for the
callback handler, run the test suite and fix any failures.

这一段要真抓重点，通常就抓下面这块原文。

# Code style
- Use ES modules (import/export) syntax, not CommonJS (require)
- Destructure imports when possible (eg. import { foo } from 'bar')

# Workflow
- Be sure to typecheck when you're done making a series of code changes
- Prefer running single tests, and not the whole test suite, for performance

这会儿轮到改配置了，字段名和关键字别自己乱换。

See @README.md for project overview and @package.json for available npm commands.

# Additional Instructions
- Git workflow: @docs/git-instructions.md
- Personal overrides: @~/.claude/my-project-instructions.md

光知道意思还不够，这里得把规矩落进配置里，下面这块照着填。

---
name: api-conventions
description: REST API design conventions for our services
---
# API Conventions
- Use kebab-case for URL paths
- Use camelCase for JSON properties
- Always include pagination for list endpoints
- Version APIs in the URL path (/v1/, /v2/)

光知道意思还不够，这里得把规矩落进配置里，下面这块照着填。

---
name: fix-issue
description: Fix a GitHub issue
disable-model-invocation: true
---
Analyze and fix the GitHub issue: $ARGUMENTS.

1. Use `gh issue view` to get the issue details
2. Understand the problem described in the issue
3. Search the codebase for relevant files
4. Implement the necessary changes to fix the issue
5. Write and run tests to verify the fix
6. Ensure code passes linting and type checking
7. Create a descriptive commit message
8. Push and create a PR

这一段说完，最后还得写到配置里才算真的生效。

---
name: security-reviewer
description: Reviews code for security vulnerabilities
tools: Read, Grep, Glob, Bash
model: opus
---
You are a senior security engineer. Review code for:
- Injection vulnerabilities (SQL, XSS, command injection)
- Authentication and authorization flaws
- Secrets or credentials in code
- Insecure data handling

Provide specific line references and suggested fixes.

"Let Claude interview you"这一段里最要紧的原始写法在下面，先看它怎么落地。

I want to build [brief description]. Interview me in detail using the AskUserQuestion tool.

Ask about technical implementation, UI/UX, edge cases, concerns, and tradeoffs. Don't ask obvious questions, dig into the hard parts I might not have considered.

Keep interviewing until we've covered everything, then write a complete spec to SPEC.md.

这一段要真抓重点，通常就抓下面这块原文。

Use subagents to investigate how our authentication system handles token
refresh, and whether we have any existing OAuth utilities I should reuse.

先别急着往下翻，下面这条命令跑完，心里才有底。

# One-off queries
claude -p "Explain what this project does"

# Structured output for scripts
claude -p "List all API endpoints" --output-format json

# Streaming for real-time processing
claude -p "Analyze this log file" --output-format stream-json

这一段不是只让你理解意思，下面这条命令就是现在要跑的。

for file in $(cat files.txt); do
  claude -p "Migrate $file from React to Vue. Return OK or FAIL." \
    --allowedTools "Edit,Bash(git commit *)"
done

这一段不是只让你理解意思，下面这条命令就是现在要跑的。

claude -p "<your prompt>" --output-format json | your_command

真到动手的时候了，下面这条直接敲一遍，看它回什么。

claude --permission-mode auto -p "fix all lint errors"

任务要具体，最好带上范围、限制、验收标准。

上下文别太杂。不同活别硬塞同一会话，不然它会把东家的锄头拿去修西家的墙。