blueprint-curate-docslisted

# /blueprint:curate-docs Curate library or project documentation into ai_docs entries optimized for AI agents - concise, actionable, gotcha-aware context that fits in PRPs. **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... | |------------------------|-------------------------| | Creating ai_docs for PRP context | Reading raw documentation for ad-hoc tasks | | Documenting library patterns for reuse | One-time library usage | | Building knowledge base for project | General library research | ## Context - ai_docs directory: !`find docs/blueprint -maxdepth 1 -name 'ai_docs' -type d` - Existing library docs: !`find docs/blueprint/ai_docs/libraries -name "*.md" -type f` - Existing project patterns: !`find docs/blueprint/ai_docs/project -name "*.md" -type f` - Library in dependencies: !`find . -maxdepth 1 \( -name package.json -o -name pyproject.toml -o -name requirements.txt \) -exec grep -m1 "^$1[\":@=]" {} +` ## Parameters Parse `$ARGUMENTS`: - `library-name`: Name of library to document (e.g., `redis`, `pydantic`) - Location: `docs/blueprint/ai_docs/libraries/[library-name].md` - OR `project:[pattern-name]` for project patterns - Location: `docs/blueprint/ai_docs/project/[pattern-name].md` ## Execution Execute complete documentation curation workflow: ### Step 1: Determine target and check existing docs 1. Parse argument to determine