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: [action] | --pull | --push | --diff | --validate\ndescription: Synchronize database schema with Supabase using MCP integration\n---\n\n# Supabase Schema Sync\n\nSynchronize database schema between local and Supabase with comprehensive validation: **$ARGUMENTS**\n\n## Current Supabase Context\n\n- MCP connection: Supabase MCP server with read-only access configured\n- Local schema: !`find . -name \"schema.sql\" -o -name \"migrations\" -type d | head -3` local database files\n- Project config: !`find . -name \"supabase\" -type d -o -name \".env*\" | grep -v node_modules | head -3` configuration files\n- Git status: !`git status --porcelain | grep -E \"\\\\.sql$|\\\\.ts$\" | head -5` database-related changes\n\n## Task\n\nExecute comprehensive schema synchronization with Supabase integration:\n\n**Sync Action**: Use $ARGUMENTS to specify pull from remote, push to remote, diff comparison, or schema validation\n\n**Schema Synchronization Framework**:\n1. **MCP Integration** - Connect to Supabase via MCP server, authenticate with project credentials, validate connection status\n2. **Schema Analysis** - Compare local vs remote schema, identify structural differences, analyze migration requirements, assess breaking changes\n3. **Sync Operations** - Execute pull/push operations, apply schema migrations, handle conflict resolution, validate data integrity\n4. **Validation Process** - Verify schema consistency, validate foreign key constraints, check index performance, test query compatibility\n5. **Migration Management** - Generate migration scripts, track version history, implement rollback procedures, optimize execution order\n6. **Safety Checks** - Backup critical data, validate permissions, check production impact, implement dry-run mode\n\n**Advanced Features**: Automated conflict resolution, schema version control, performance impact analysis, team collaboration workflows, CI/CD integration.\n\n**Quality Assurance**: Schema validation, data integrity checks, performance optimization, rollback readiness, team synchronization.\n\n**Output**: Complete schema sync with validation reports, migration scripts, conflict resolution, and team collaboration updates."} |