メニュー
Curate library gotchas and project patterns into .claude/rules/ entries for AI context. Use when documenting library knowledge for PRP reuse.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/laurigates/claude-plugins --skill blueprint-curate-docsコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Install, configure and troubleshoot MCP servers. Use when adding/enabling servers, editing .mcp.json, fixing OAuth, or when a server runs stale code after an upstream fix.
FinOps snapshot — org billing, workflow stats, cache usage. Use when you want a high-level view of CI spending or workflow health before diving deeper.
GitHub Actions billing, workflow efficiency, and waste analysis at org or repo level. Use when investigating CI/CD costs, wasted runs, or optimizing triggers.
SKILL.md を表示中
SOC 職業分類に基づく
| description | Curate library gotchas and project patterns into .claude/rules/ entries for AI context. Use when documenting library knowledge for PRP reuse. |
| args | [library-name|project:pattern-name] |
| argument-hint | Library name (e.g., redis, pydantic) or project:pattern-name |
| allowed-tools | Read, Write, Glob, Bash, WebFetch, WebSearch, AskUserQuestion |
| model | opus |
| created | "2025-12-16T00:00:00.000Z" |
| modified | "2026-07-03T00:00:00.000Z" |
| reviewed | "2026-02-14T00:00:00.000Z" |
| name | blueprint-curate-docs |
Curate library or project documentation into .claude/rules/ entries optimized for AI agents — concise, actionable, gotcha-aware context that is auto-loaded into sessions and referenceable from PRPs.
Note: earlier blueprint versions wrote these entries to
docs/blueprint/ai_docs/. That location is deprecated —.claude/rules/is the canonical home for curated AI context, since rules are loaded by Claude Code natively and shared with every contributor.
Usage: /blueprint:curate-docs [library-name] or /blueprint:curate-docs project:[pattern-name]
| Use this skill when... | Use alternative when... |
|---|---|
| Documenting library gotchas for PRP/context reuse | Reading raw documentation for ad-hoc tasks |
| Codifying project patterns as rules | One-time library usage |
Building a knowledge base under .claude/rules/ | General library research |
find . -maxdepth 2 -type d -name rules -path '*/.claude/*'find . -maxdepth 3 -path '*/.claude/rules/*' -name "*.md" -type ffind . -maxdepth 3 -path '*/docs/blueprint/manifest.json' -exec jq -r '.structure.generated_rules_path // ".claude/rules/"' {} +find . -maxdepth 1 \( -name package.json -o -name pyproject.toml -o -name requirements.txt \) -exec grep -m1 "^$1[\":@=]" {} +Parse $ARGUMENTS:
library-name: Name of library to document (e.g., redis, pydantic)
$RULES_DIR/lib-[library-name].mdproject:[pattern-name] for project patterns$RULES_DIR/[pattern-name].md$RULES_DIR is structure.generated_rules_path from docs/blueprint/manifest.json when set, otherwise .claude/rules/.
Execute complete documentation curation workflow:
$RULES_DIR (manifest structure.generated_rules_path, default .claude/rules/)$RULES_DIRFor libraries:
For project patterns:
grep -r "{pattern}" src/Sources for gotchas: GitHub issues, Stack Overflow, team experience, official docs warnings.
Generate the file at $RULES_DIR/lib-[library-name].md or $RULES_DIR/[pattern-name].md (see REFERENCE.md).
Never overwrite a hand-authored rule. If a file with the target name exists and was not produced by this skill, pick a distinct name (e.g. lib-[library-name]-gotchas.md) or ask.
Include all sections from template: Quick Reference, Patterns We Use, Configuration, Gotchas, Testing, Examples.
Keep under 200 lines total.
Include copy-paste-ready code snippets from:
Update the task registry entry in docs/blueprint/manifest.json:
jq --arg now "$(date -u +%Y-%m-%dT%H:%M:%SZ)" \
--argjson processed "${ITEMS_PROCESSED:-0}" \
--argjson created "${ITEMS_CREATED:-0}" \
'.task_registry["curate-docs"].last_completed_at = $now |
.task_registry["curate-docs"].last_result = "success" |
.task_registry["curate-docs"].stats.runs_total = ((.task_registry["curate-docs"].stats.runs_total // 0) + 1) |
.task_registry["curate-docs"].stats.items_processed = $processed |
.task_registry["curate-docs"].stats.items_created = $created' \
docs/blueprint/manifest.json > tmp.json && mv tmp.json docs/blueprint/manifest.json
| Context | Command |
|---|---|
| Resolve rules dir | jq -r '.structure.generated_rules_path // ".claude/rules/"' docs/blueprint/manifest.json |
| List existing rules | ls .claude/rules/ 2>/dev/null |
| Check library version | grep "{library}" package.json pyproject.toml 2>/dev/null | head -1 |
| Search for patterns | Use grep on src/ for project patterns |
| Fast research | Use WebSearch for common issues instead of fetching docs |
For the rule template, section guidelines, and example entries, see REFERENCE.md.