mirror of
https://github.com/davila7/claude-code-templates.git
synced 2026-09-19 01:30:23 +08:00
daniel
41cbbea00c
- Split components.json: índice sin content (1.9 MB / 249 KB br vs 15.6 MB / 4.15 MB br).
Generador produce component-content/{type}/{slug}.json por componente y auto-copia
a dashboard/public/. Página de detalle carga contenido on-demand via fetchComponentContent().
- Restaurar cabeceras de caché y seguridad perdidas en la migración Vercel→Cloudflare:
_headers con Cache-Control max-age=86400 para JSONs, immutable para _astro/*,
y HSTS, X-Frame-Options, Referrer-Policy, Permissions-Policy en todas las rutas.
- Eliminar dashboard/vercel.json (config muerta desde migración a Cloudflare Pages).
- Diferir hidratación: ClerkIsland y AuthButton client:load → client:idle;
SaveToCollectionButton → client:visible.
- Eliminar gpt-tokenizer del bundle del navegador: reemplazado por estimación chars/4.
- Actualizar .claude/rules/dashboard.md para reflejar hosting en Cloudflare Pages.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1 line
2.2 KiB
JSON
1 line
2.2 KiB
JSON
{"content": "---\nallowed-tools: Read, Write, Edit, Bash\nargument-hint: [migration-type] | --create | --alter | --seed | --rollback\ndescription: Generate and manage Supabase database migrations with automated testing and validation\n---\n\n# Supabase Migration Assistant\n\nGenerate and manage Supabase migrations with comprehensive testing and validation: **$ARGUMENTS**\n\n## Current Migration Context\n\n- Supabase project: MCP integration for migration management and validation\n- Migration files: !`find . -name \"*migrations*\" -type d -o -name \"*.sql\" | head -5` existing migration structure\n- Schema version: Current database schema state and migration history\n- Local changes: !`git diff --name-only | grep -E \"\\\\.sql$|\\\\.ts$\" | head -3` pending database modifications\n\n## Task\n\nExecute comprehensive migration management with automated validation and testing:\n\n**Migration Type**: Use $ARGUMENTS to specify table creation, schema alterations, data seeding, or migration rollback\n\n**Migration Management Framework**:\n1. **Migration Planning** - Analyze schema requirements, design migration strategy, identify dependencies, plan rollback procedures\n2. **Code Generation** - Generate migration SQL files, create TypeScript types, implement safety checks, optimize execution order\n3. **Validation Testing** - Test migration on development data, validate schema changes, verify data integrity, check constraint violations\n4. **Supabase Integration** - Apply migrations via MCP server, monitor execution status, handle error conditions, validate final state\n5. **Type Generation** - Generate TypeScript types, update application interfaces, sync with client-side schemas, maintain type safety\n6. **Rollback Strategy** - Create rollback migrations, test rollback procedures, implement data preservation, validate recovery process\n\n**Advanced Features**: Automated type generation, migration testing, performance impact analysis, team collaboration, CI/CD integration.\n\n**Safety Measures**: Pre-migration backups, dry-run validation, rollback testing, data integrity checks, performance monitoring.\n\n**Output**: Complete migration suite with SQL files, TypeScript types, test validation, rollback procedures, and deployment documentation."} |