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: [api-version] | --v1 | --v2 | --graphql-hybrid | --openapi
description: Design RESTful API architecture with comprehensive endpoints, authentication, and documentation
Design REST API
Design comprehensive RESTful API architecture: $ARGUMENTS
Current Application State
- Framework detection: @package.json or @requirements.txt (Express, FastAPI, Spring Boot, etc.)
- Existing API: !
grep -r "route\|endpoint\|@app\\.route" src/ 2>/dev/null | wc -lroutes found - Authentication: !
grep -r "auth\|jwt\|session" src/ 2>/dev/null | wc -lauth components - Documentation: @swagger.yaml or @openapi.json (if exists)
Task
Design complete RESTful API with industry best practices and comprehensive functionality:
API Version: Use $ARGUMENTS to specify API version, GraphQL hybrid approach, or OpenAPI specification
API Architecture:
- Resource Design - RESTful endpoints, HTTP methods, URL structure, resource relationships
- Request/Response Models - Data validation, serialization, error handling, status codes
- Authentication & Authorization - JWT, OAuth, RBAC, API keys, rate limiting
- API Documentation - OpenAPI/Swagger specs, interactive documentation, code examples
- Versioning Strategy - URL, header, or content-type based versioning
- Performance & Security - Caching, pagination, CORS, input validation, SQL injection prevention
Advanced Features: Real-time capabilities, file uploads, batch operations, webhooks, and monitoring integration.
Standards Compliance: Follow REST principles, HTTP specifications, and API design best practices.
Output: Complete API specification with endpoints, authentication, validation, documentation, and client SDKs.