Files
Dani 054c0e56e9 fix(commands): Remove deprecated 'model: sonnet' field from 142 command files
Removed the deprecated 'model: sonnet' field from command frontmatter to fix
compatibility issues with Claude Code. Commands will now inherit the model from
the active conversation instead of using a hardcoded deprecated model identifier.

Changes:
- Removed 'model: sonnet' from 142 command files across all categories
- Commands now use default model inheritance behavior
- Preserved 'model: claude-sonnet-4-5-20250929' in gemini-review.md (valid model)
- 67 commands without model field remain unchanged

This resolves the "model: sonnet not found" error reported in GitHub issues
and aligns with Claude Code's recommended practice of letting commands inherit
the conversation model.

Affected categories:
- Database/Supabase commands (8 files)
- Documentation commands (8 files)
- Deployment commands (11 files)
- Setup commands (14 files)
- Performance commands (8 files)
- Team commands (14 files)
- Security commands (6 files)
- NextJS/Vercel commands (10 files)
- Sync commands (14 files)
- And more across other categories

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-21 10:08:58 -04:00

1.6 KiB

allowed-tools: Read, Write, Edit, WebSearch, Grep, Glob argument-hint: [feature-description] | --research | --template | --validate description: Create comprehensive Product Requirement Prompt (PRP) with research and validation

Create Product Requirement Prompt

Create comprehensive Product Requirement Prompt (PRP) following structured research process: $ARGUMENTS

PRP Foundation

  • Base template: @concept_library/cc_PRP_flow/PRPs/base_template_v1
  • PRP concept: @concept_library/cc_PRP_flow/README.md
  • Existing PRPs: !find concept_library/cc_PRP_flow/PRPs/ -name "*.md" | head -5
  • Documentation: @ai_docs/ directory analysis

Task

Develop comprehensive PRP through systematic research and structured documentation:

Research Process:

  1. Documentation Review - Analyze existing ai_docs/ and project documentation
  2. Web Research - Gather implementation examples, library docs, and best practices
  3. Template Analysis - Study base_template_v1 structure and existing PRPs
  4. Codebase Exploration - Identify patterns, dependencies, and integration points
  5. Context Synthesis - Compile comprehensive implementation context

PRP Development:

  • Follow base_template_v1 structure exactly
  • Include specific file references and web resources
  • Provide curated codebase intelligence
  • Define clear validation criteria and success metrics
  • Create production-ready implementation guide

Remember: PRP = PRD + curated codebase intelligence + agent/runbook—the minimum viable packet an AI needs to ship production-ready code on the first pass.