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.7 KiB
1.7 KiB
allowed-tools: Read, Write, Edit, Bash
argument-hint: [schema-type] | --relational | --nosql | --hybrid | --normalize
description: Design optimized database schemas with proper relationships, constraints, and performance considerations
Design Database Schema
Design optimized database schemas with comprehensive data modeling: $ARGUMENTS
Current Project Context
- Application type: Based on $ARGUMENTS or codebase analysis
- Data requirements: @requirements/ or project documentation
- Existing schema: @prisma/schema.prisma or @migrations/ or database dumps
- Performance needs: Expected scale, query patterns, and data volume
Task
Design comprehensive database schema with optimal structure and performance:
Schema Type: Use $ARGUMENTS to specify relational, NoSQL, hybrid approach, or normalization level
Design Framework:
- Requirements Analysis - Business entities, relationships, data flow, and access patterns
- Entity Modeling - Tables/collections, attributes, primary/foreign keys, constraints
- Relationship Design - One-to-one, one-to-many, many-to-many associations
- Normalization Strategy - Data consistency vs performance trade-offs
- Performance Optimization - Indexing strategy, query optimization, partitioning
- Security Design - Access control, data encryption, audit trails
Advanced Patterns: Implement temporal data, soft deletes, JSONB fields, full-text search, audit logging, and scalability patterns.
Validation: Ensure referential integrity, data consistency, query performance, and future extensibility.
Output: Complete schema design with DDL scripts, ER diagrams, performance analysis, and migration strategy.