mirror of
https://github.com/davila7/claude-code-templates.git
synced 2026-09-19 01:30:23 +08:00
Dani
054c0e56e9
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>
1.4 KiB
1.4 KiB
allowed-tools: Read, Write, Edit, Bash
argument-hint: [project-name] | --minimal | --epic-name | --owner
description: Initialize Product as Code (PAC) project structure with templates and configuration
Configure PAC Project
Initialize Product as Code (PAC) project structure: $ARGUMENTS
Current Project State
- Git status: !
git status --porcelain | wc -luncommitted changes - PAC structure: !
ls -la .pac/ 2>/dev/null | head -5 || echo "No PAC directory" - Existing epics: !
find .pac/epics/ -name "*.yaml" 2>/dev/null | wc -l
Task
Configure and initialize PAC project structure for version-controlled product management:
Setup Process:
- Project Analysis - Validate git repository and analyze existing PAC structure
- Directory Creation - Create
.pac/structure with epics, tickets, and templates - Configuration Files - Generate
pac.config.yamlwith project metadata and defaults - Template Creation - Create epic and ticket templates following PAC v0.1.0 specification
- Initial Content - Create first epic and ticket based on user input
- Integration Setup - Configure git hooks and validation scripts
Arguments: Use --minimal for basic structure, --epic-name for initial epic, --owner for product owner.
Next Steps: Use /project:pac-create-epic and /project:pac-create-ticket to manage product development.