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
1.6 KiB
JSON

{"content": "---\nallowed-tools: Read, Write, Edit, Bash\nargument-hint: [auth-method] | --oauth | --jwt | --mfa | --passwordless\ndescription: Implement secure user authentication system with chosen method and security best practices\n---\n\n# Add Authentication System\n\nImplement secure user authentication system: **$ARGUMENTS**\n\n## Current Application State\n\n- Framework detection: @package.json or @requirements.txt or @Cargo.toml\n- Existing auth: !`grep -r \"auth\\|login\\|jwt\\|session\" src/ --include=\"*.js\" --include=\"*.py\" --include=\"*.rs\" | wc -l`\n- Security config: @.env* (check for auth-related variables)\n- Database setup: Check for user models or auth tables\n\n## Task\n\nImplement comprehensive authentication system with security best practices:\n\n**Authentication Methods**: Choose from username/password, OAuth 2.0, JWT, SAML, MFA, or passwordless based on $ARGUMENTS\n\n**Implementation Areas**:\n1. **User Management** - Registration, profiles, password policies, account verification\n2. **Authentication Flow** - Login/logout, session management, token handling, middleware\n3. **Authorization System** - RBAC, permissions, route protection, API security\n4. **Security Hardening** - Password hashing, rate limiting, CSRF protection, secure cookies\n5. **Integration** - Frontend components, API endpoints, database models, middleware\n\n**Security Standards**: Implement OWASP authentication guidelines, secure session management, and proper error handling.\n\n**Output**: Production-ready authentication system with comprehensive security controls and user-friendly interface.\n"}