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] | --github-to-linear | --linear-to-github | --bidirectional | --validate\ndescription: Comprehensive migration assistant for large-scale GitHub-Linear data transitions with validation and rollback\n---\n\n# Sync Migration Assistant\n\nExecute comprehensive data migration between GitHub and Linear with enterprise-grade capabilities: **$ARGUMENTS**\n\n## Current Migration Environment\n\n- Source system: !`gh --version 2>/dev/null && echo \"GitHub CLI available\" || echo \"GitHub CLI needed\"`\n- Target system: Linear MCP server connectivity and authentication status\n- Migration scope: Analysis of data volume and complexity for planning\n- Infrastructure: Database, queue services, and processing capacity assessment\n\n## Task\n\nImplement large-scale data migration with comprehensive validation and enterprise features:\n\n**Migration Type**: Use $ARGUMENTS to specify GitHub-to-Linear, Linear-to-GitHub, bidirectional setup, or validation mode\n\n**Migration Framework**:\n1. **Pre-Migration Assessment** - Data volume analysis, dependency mapping, risk assessment, resource planning\n2. **Migration Planning** - Phased approach design, rollback strategy, validation checkpoints, timeline estimation\n3. **Data Extraction** - Comprehensive data harvesting, relationship preservation, metadata capture, error handling\n4. **Transformation Engine** - Field mapping, format conversion, validation rules, data enrichment\n5. **Migration Execution** - Batch processing, progress tracking, error recovery, quality assurance\n6. **Post-Migration Validation** - Data integrity verification, relationship validation, performance testing, rollback readiness\n\n**Enterprise Features**: Large-scale batch processing, comprehensive error recovery, detailed audit trails, rollback capabilities, performance optimization.\n\n**Quality Assurance**: Multi-stage validation, data integrity checks, relationship verification, comprehensive testing, enterprise monitoring.\n\n**Output**: Complete migration system with phased execution, comprehensive validation, detailed reporting, and enterprise-grade reliability for large-scale data transitions."} |