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>
36 lines
1.8 KiB
Markdown
36 lines
1.8 KiB
Markdown
---
|
|
allowed-tools: Read, Write, Edit, WebSearch
|
|
argument-hint: [constraint-domain] | --business | --technical | --regulatory | --resource
|
|
description: Model system constraints with validation, dependency mapping, and optimization strategies
|
|
---
|
|
|
|
# Constraint Modeler
|
|
|
|
Model comprehensive system constraints with systematic validation and optimization: **$ARGUMENTS**
|
|
|
|
## Current System Context
|
|
|
|
- Domain scope: Based on $ARGUMENTS (business, technical, operational, financial)
|
|
- Existing constraints: @documentation or configuration files
|
|
- System boundaries: Current limitations and dependencies
|
|
- Change dynamics: Historical constraint evolution patterns
|
|
|
|
## Task
|
|
|
|
Create comprehensive constraint models for accurate simulation and decision-making:
|
|
|
|
**Constraint Domain**: Use $ARGUMENTS to focus on business, technical, regulatory, or resource constraints
|
|
|
|
**Constraint Framework**:
|
|
1. **Hard Constraints** - Absolute limits that cannot be violated (legal, physical, technical)
|
|
2. **Soft Constraints** - Preferences and trade-offs that can be managed (budget, quality, timing)
|
|
3. **Dynamic Constraints** - Limitations that evolve over time (market, technology, capacity)
|
|
4. **Constraint Dependencies** - Relationships and interactions between different limitations
|
|
5. **Validation Framework** - Methods to verify constraint accuracy and relevance
|
|
6. **Optimization Strategies** - Approaches to relax, substitute, or circumvent constraints
|
|
|
|
**Advanced Analysis**: Constraint sensitivity analysis, bottleneck identification, scenario boundary definition, and optimization algorithms.
|
|
|
|
**Strategic Application**: Link constraint models to decision scenarios, resource allocation, and strategic planning.
|
|
|
|
**Output**: Complete constraint model with interaction matrices, validation reports, optimization recommendations, and scenario boundary definitions. |