菜单
Claude Code documentation reference and discovery. Use when looking up Claude Code features, configuration, plugins, skills, hooks, or troubleshooting.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/simpleapps-com/augur-skills --skill claude-code-docs命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Basecamp 2 integration via MCP. Covers MCP tool reference, URL parsing, authentication, Chrome fallback, attachments, and site-info documents. Use when reading or writing Basecamp data.
Bash command conventions. One command per call, use dedicated tools over shell equivalents, check wiki for approved commands. Load this skill before running Bash commands.
When working in load-bearing code (the 5-10% where correctness matters most: money math, auth, concurrency, state machines, security boundaries), tighten the type system first, then add formal contracts (@requires/@ensures/@invariant/@trusted) in the host language's native comment syntax. Use Unicode glyphs (∀, ∈, ≥, ℕ) for AI priming, paired with ASCII gloss for human readers. The contracts pay off through three independent mechanisms: priming agent reasoning, surfacing tests, and adding context-window value that agents themselves report. Drift between contract and code is a defect.
正在显示 SKILL.md
| name | claude-code-docs |
| description | Claude Code documentation reference and discovery. Use when looking up Claude Code features, configuration, plugins, skills, hooks, or troubleshooting. |
| allowed-tools | ["Bash","Read","WebFetch"] |
IMPORTANT: YOU MUST start from llms.txt for current URLs. Doc pages are renamed and reorganized with each release. Never rely on memorized URLs.
Claude Code ships several releases a week. Settings keys, frontmatter fields, tool names, and default behaviours all move. Training data lags the product, so recalled detail is stale by default.
MUST fetch the relevant page before asserting that a feature, setting, or field exists. This applies even when the answer feels certain. A confidently wrong config key costs the user a debugging session.
Doc pages carry min-version markers ("Requires Claude Code v2.1.218 or later"), and behaviour frequently differs across releases. When a page gates something on a version, check what is actually installed:
claude --version
Report the gap rather than the feature when the installed build predates the requirement.
Large pages blow out context. Two habits keep the cost down:
rg the file for the keys you need instead of reading it whole.