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.3 KiB
Markdown
36 lines
2.3 KiB
Markdown
---
|
|
allowed-tools: Read, Write, Edit, Bash
|
|
argument-hint: [optimization-type] | --queries | --indexes | --storage | --rls | --functions
|
|
description: Optimize Supabase database performance with intelligent analysis and recommendations
|
|
---
|
|
|
|
# Supabase Performance Optimizer
|
|
|
|
Optimize Supabase database performance with intelligent analysis and automated improvements: **$ARGUMENTS**
|
|
|
|
## Current Performance Context
|
|
|
|
- Supabase metrics: Database performance data via MCP integration
|
|
- Query patterns: !`find . -name "*.sql" -o -name "*.ts" -o -name "*.js" | xargs grep -l "from\|select\|insert\|update" 2>/dev/null | head -5` application queries
|
|
- Schema analysis: Current table structures and relationship complexity
|
|
- Performance logs: Recent query execution times and resource usage patterns
|
|
|
|
## Task
|
|
|
|
Execute comprehensive performance optimization with intelligent analysis and automated improvements:
|
|
|
|
**Optimization Focus**: Use $ARGUMENTS to focus on query optimization, index management, storage optimization, RLS policies, or database functions
|
|
|
|
**Performance Optimization Framework**:
|
|
1. **Performance Analysis** - Analyze query execution times, identify slow operations, assess resource utilization, evaluate bottlenecks
|
|
2. **Index Optimization** - Analyze index usage, recommend new indexes, identify redundant indexes, optimize index strategies
|
|
3. **Query Optimization** - Review application queries, suggest query improvements, implement query caching, optimize join operations
|
|
4. **Storage Optimization** - Analyze storage patterns, recommend archival strategies, optimize data types, implement compression
|
|
5. **RLS Policy Review** - Analyze Row Level Security policies, optimize policy performance, reduce policy complexity, improve security efficiency
|
|
6. **Function Optimization** - Review database functions, optimize function performance, implement caching strategies, improve execution plans
|
|
|
|
**Advanced Features**: Automated index recommendations, query plan analysis, performance trend monitoring, cost optimization, scaling recommendations.
|
|
|
|
**Monitoring Integration**: Real-time performance tracking, alert configuration, performance regression detection, optimization impact measurement.
|
|
|
|
**Output**: Comprehensive optimization plan with performance improvements, index recommendations, query optimizations, and monitoring setup. |