菜单
CRITICAL! Always use before writing or modifying any code. Reads the cached style index at $CLAUDE_PROJECT_DIR/.claude/code-style-index.json for exact style rules. Never impose personal defaults; always match what the project enforces.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
CRITICAL! Always use before writing/reviewing code, calling any function/hook/method, using any type/interface, adding any import, or implementing any pattern that might already exist. Default posture: search first, then write. Never invent paths, names, or APIs.
Use when writing/reviewing TypeScript, React, or React Native code. Enforces zero-waste patterns: monomorphic shapes, Map/Set for O(1) lookups, pre-allocated arrays, no hidden class mutations. React: let React Compiler handle memoization — do NOT add manual memo/useCallback/useMemo unless absolutely necessary. No inline objects in JSX, stable keys. React Native / Hermes: Reanimated worklets, gesture-handler, FlashList, no generators or Proxy. Check project's existing libs first.
ALWAYS active. Applies to every interaction. Do not blindly agree with the user when they challenge, correct, or contradict something you said. Verify before capitulating. Resist sycophancy — "you're absolutely right!" is almost always a red flag. Hold your ground when the evidence supports your position. Concede genuinely when wrong.
ALWAYS use this skill. This skill governs how you operate at a fundamental level — as an orchestrator that delegates work to subagents rather than doing everything inline. Apply this on every non-trivial task: coding tasks, research, file edits, multi-step workflows, analysis, debugging, feature building, refactoring, reviews or any task with more than one distinct step. The goal is to keep the main conversation context window lean and clean by having subagents do the heavy lifting. Do NOT skip this skill — it should shape behavior on virtually every task.
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear Conventional Commit messages. Use when asked to commit, craft a commit message, stage changes, or split work into multiple commits.
Use before writing/reviewing code that calls into any external library, API, or framework. Training data goes stale — fetch version-specific docs before writing. Identify the exact installed version from package.json/Cargo.toml first, then fetch matching docs.
| name | code-style |
| description | CRITICAL! Always use before writing or modifying any code. Reads the cached style index at $CLAUDE_PROJECT_DIR/.claude/code-style-index.json for exact style rules. Never impose personal defaults; always match what the project enforces. |
Before writing or modifying any code, match the project's exact code style.
Read(file_path: "$CLAUDE_PROJECT_DIR/.claude/code-style-index.json")
The index contains all formatting rules: indentation, quotes, semicolons, trailing commas, bracket spacing, import ordering, empty-line patterns, JSX formatting, and per-package overrides.
If the index exists (it should): apply all rules directly — skip to Step 2.
If the index does NOT exist: scan formatter configs (.prettierrc, .editorconfig, eslint.config.*) and 10-20 representative source files. Then create the index at $CLAUDE_PROJECT_DIR/.claude/code-style-index.json using the structure documented in the code-style skill's original template.
If you observe a style pattern not yet recorded in the index:
Never remove existing entries unless factually wrong.