Files
daniel 41cbbea00c perf(dashboard): reducir payload del home 87% y restaurar caching en Cloudflare
- 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>
2026-06-13 16:58:13 -04:00

1 line
2.5 KiB
JSON

{"content": "---\nallowed-tools: Read, Write, Edit, Bash\nargument-hint: [testing-type] | --capacity | --stress | --spike | --endurance | --volume\ndescription: Configure comprehensive load testing with performance metrics and bottleneck identification\n---\n\n# Setup Load Testing\n\nConfigure comprehensive load testing with performance analysis and bottleneck identification: **$ARGUMENTS**\n\n## Current Performance Context\n\n- Application type: !`find . -name \"server.js\" -o -name \"app.py\" -o -name \"main.go\" | head -1 && echo \"Server application\" || echo \"Detect app type\"`\n- API endpoints: !`grep -r \"app\\\\.get\\\\|app\\\\.post\\\\|@RequestMapping\" . 2>/dev/null | wc -l` detected endpoints\n- Database: !`find . -name \"*.sql\" -o -name \"database.js\" | head -1 && echo \"Database detected\" || echo \"No database files\"`\n- Current monitoring: !`find . -name \"prometheus.yml\" -o -name \"newrelic.js\" | head -1 || echo \"No monitoring detected\"`\n\n## Task\n\nImplement comprehensive load testing with performance optimization and bottleneck analysis:\n\n**Testing Type**: Use $ARGUMENTS to focus on capacity planning, stress testing, spike testing, endurance testing, or volume testing\n\n**Load Testing Framework**:\n\n1. **Strategy & Requirements** - Analyze application architecture, define testing objectives, determine scenarios, identify performance metrics\n2. **Tool Selection & Setup** - Choose appropriate tools (k6, Artillery, JMeter, Gatling), install dependencies, configure environments\n3. **Test Scenario Design** - Create realistic user scenarios, implement API test scripts, configure data generation, design load patterns\n4. **Performance Metrics** - Configure response time monitoring, throughput measurement, error rate tracking, resource utilization monitoring\n5. **Infrastructure Setup** - Configure test environments, setup monitoring dashboards, implement result collection, optimize test execution\n6. **Analysis & Optimization** - Identify performance bottlenecks, analyze resource constraints, recommend optimizations, track improvements\n\n**Advanced Features**: Distributed load generation, real-time monitoring, automated performance regression detection, CI/CD integration, chaos engineering.\n\n**Quality Assurance**: Test reliability, result accuracy, environment consistency, monitoring completeness.\n\n**Output**: Complete load testing setup with configured scenarios, performance monitoring, bottleneck analysis, and optimization recommendations.\n"}