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.8 KiB
1.8 KiB
allowed-tools: Read, Write, Edit, Bash
argument-hint: [schema-approach] | --schema-first | --code-first | --federation
description: Implement GraphQL API with comprehensive schema, resolvers, and real-time subscriptions
Implement GraphQL API
Implement comprehensive GraphQL API with modern best practices: $ARGUMENTS
Current Application Context
- Framework: @package.json or @requirements.txt (detect Apollo, GraphQL Yoga, etc.)
- Existing API: !
find . -name "*.graphql" -o -name "*schema*" -o -name "*resolver*" | wc -l - Database integration: @prisma/schema.prisma or database connection configs
- Authentication: !
grep -r "auth\|jwt\|context" src/ 2>/dev/null | wc -l
Task
Build production-ready GraphQL API with comprehensive functionality and performance optimization:
Schema Approach: Use $ARGUMENTS to specify schema-first, code-first, or federation architecture
GraphQL Implementation:
- Schema Design - Type definitions, queries, mutations, subscriptions, custom scalars
- Resolver Architecture - Data fetching, authentication, authorization, error handling
- DataLoader Integration - N+1 query prevention, batch loading, caching strategies
- Real-time Features - WebSocket subscriptions, live data updates, connection management
- Security & Performance - Query complexity analysis, depth limiting, rate limiting
- Development Tools - GraphQL Playground, introspection, schema stitching
Advanced Features: File uploads, federated schemas, Apollo Federation, schema directives, and monitoring.
Production Readiness: Implement comprehensive error handling, logging, metrics, and deployment strategies.
Output: Complete GraphQL API with optimized resolvers, real-time capabilities, security controls, and developer documentation.