blueprint-curate-docslisted

# /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]` ## When to Use This Skill | 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 | ## Context - Rules directory: !`find . -maxdepth 2 -type d -name rules -path '*/.claude/*'` - Existing rules: !`find . -maxdepth 3 -path '*/.claude/rules/*' -name "*.md" -type f` - Rules path override: !`find . -maxdepth 3 -path '*/docs/blueprint/manifest.json' -exec jq -r '.structure.generated_rules_path // ".claude/rules/"' {} +` - Library in dependencies: !`find . -maxdepth 1 \( -name package.json -o -name pyproject.toml -o -name requirements.txt \) -exec grep -m1 "^$1[\":@=]" {} +` ## Parameters Parse `$ARGUMENTS`