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.9 KiB

allowed-tools: Read, Write, Edit, Bash argument-hint: [monorepo-tool] | --nx | --lerna | --rush | --turborepo | --yarn-workspaces description: Configure monorepo project structure with comprehensive workspace management and build orchestration

Setup Monorepo

Configure comprehensive monorepo structure with advanced workspace management: $ARGUMENTS

Current Project State

  • Repository structure: !find . -maxdepth 2 -type d | head -10
  • Package manager: @package.json or existing workspace configuration
  • Existing monorepo: @nx.json or @lerna.json or @rush.json or @turbo.json
  • Project count: !find . -name "package.json" -not -path "./node_modules/*" | wc -l

Task

Implement production-ready monorepo with advanced workspace management and build orchestration:

Monorepo Tool: Use $ARGUMENTS to configure Nx, Lerna, Rush, Turborepo, or Yarn Workspaces

Monorepo Architecture:

  1. Workspace Structure - Directory organization, package architecture, shared libraries, application separation
  2. Dependency Management - Workspace dependencies, version management, package hoisting, conflict resolution
  3. Build Orchestration - Task dependencies, parallel builds, incremental compilation, affected package detection
  4. Development Workflow - Hot reloading, debugging, testing strategies, development server coordination
  5. CI/CD Integration - Build pipelines, affected project detection, deployment orchestration, artifact management
  6. Tooling Configuration - Shared configurations, code quality tools, testing frameworks, documentation

Advanced Features: Task caching, distributed execution, performance optimization, plugin ecosystem integration.

Team Productivity: Developer experience optimization, onboarding automation, maintenance procedures.

Output: Complete monorepo setup with optimized build system, comprehensive tooling, and team productivity enhancements.