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
2.1 KiB
Markdown
36 lines
2.1 KiB
Markdown
---
|
|
allowed-tools: Read, Write, Edit, WebSearch
|
|
argument-hint: [system-type] | --business-ecosystem | --organizational-dynamics | --market-evolution | --feedback-loops
|
|
description: Model complex system dynamics with feedback loops, delays, and emergent behavior analysis
|
|
---
|
|
|
|
# System Dynamics Modeler
|
|
|
|
Model complex system dynamics with comprehensive feedback analysis and emergent behavior prediction: **$ARGUMENTS**
|
|
|
|
## Current System Context
|
|
|
|
- System type: Based on $ARGUMENTS (business ecosystem, organizational dynamics, market evolution, feedback loops)
|
|
- System boundaries: Components, stakeholders, and environmental factors included in the model
|
|
- Key variables: Stock and flow variables, feedback mechanisms, and delay structures
|
|
- Behavior patterns: Current system performance and historical dynamics
|
|
|
|
## Task
|
|
|
|
Build comprehensive system dynamics model with feedback loops and emergent behavior analysis:
|
|
|
|
**System Type**: Use $ARGUMENTS to model business ecosystems, organizational dynamics, market evolution, or feedback loop systems
|
|
|
|
**System Dynamics Framework**:
|
|
1. **System Architecture** - Stock and flow identification, causal loop mapping, and boundary definition
|
|
2. **Feedback Structure** - Reinforcing loops, balancing loops, and delay modeling with policy resistance analysis
|
|
3. **Dynamic Simulation** - Time-based behavior analysis, scenario testing, and sensitivity analysis
|
|
4. **Emergent Behavior** - Non-linear effects, unintended consequences, and system archetypes identification
|
|
5. **Policy Testing** - Intervention analysis, leverage point identification, and strategy optimization
|
|
6. **Learning Laboratory** - What-if experimentation, mental model testing, and insight generation
|
|
|
|
**Advanced Features**: Nonlinear modeling, stochastic elements, multi-level hierarchy modeling, and behavioral dynamics integration.
|
|
|
|
**Strategic Applications**: Policy design, organizational change, strategic planning, and complex problem solving with systems thinking.
|
|
|
|
**Output**: Complete system dynamics model with causal structure, simulation results, policy recommendations, and strategic insights for complex system optimization and management. |