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
9.6 KiB
JSON
Raw Permalink Blame History

This file contains invisible Unicode characters
This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
{"content": "---\nallowed-tools: Bash(git:*), Read\ndescription: Display comprehensive Git Flow status including branch type, sync status, changes, and merge targets\n---\n\n# Git Flow Status\n\nDisplay comprehensive Git Flow repository status\n\n## Current Repository State\n\n- Current branch: !`git branch --show-current`\n- Git status: !`git status --porcelain`\n- Branch list: !`git branch -a | grep -E '(feature|release|hotfix|develop|main)' | head -20`\n- Latest tags: !`git tag --sort=-version:refname | head -5`\n- Recent commits: !`git log --oneline --graph --all -10`\n- Remote status: !`git remote -v`\n\n## Task\n\nProvide a comprehensive Git Flow status report:\n\n### 1. Branch Analysis\n\nDetermine current branch type and state:\n\n```bash\nCURRENT_BRANCH=$(git branch --show-current)\n\n# Detect branch type\nif [[ $CURRENT_BRANCH == \"main\" ]]; then\n BRANCH_TYPE=\"🏠 Production\"\n ICON=\"🏠\"\n STATUS_COLOR=\"red\"\nelif [[ $CURRENT_BRANCH == \"develop\" ]]; then\n BRANCH_TYPE=\"🔀 Integration\"\n ICON=\"🔀\"\n STATUS_COLOR=\"blue\"\nelif [[ $CURRENT_BRANCH == feature/* ]]; then\n BRANCH_TYPE=\"🌿 Feature\"\n ICON=\"🌿\"\n STATUS_COLOR=\"green\"\nelif [[ $CURRENT_BRANCH == release/* ]]; then\n BRANCH_TYPE=\"🚀 Release\"\n ICON=\"🚀\"\n STATUS_COLOR=\"yellow\"\nelif [[ $CURRENT_BRANCH == hotfix/* ]]; then\n BRANCH_TYPE=\"🔥 Hotfix\"\n ICON=\"🔥\"\n STATUS_COLOR=\"red\"\nelse\n BRANCH_TYPE=\"📁 Other\"\n ICON=\"📁\"\n STATUS_COLOR=\"gray\"\nfi\n```\n\n### 2. Comprehensive Status Display\n\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n🌿 GIT FLOW STATUS\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\n📍 CURRENT BRANCH\n $ICON $CURRENT_BRANCH\n Type: $BRANCH_TYPE\n Base: [origin branch]\n Target: [merge destination]\n\n📊 REPOSITORY INFO\n Remote: origin ($REMOTE_URL)\n Latest tag: v1.2.0\n Total branches: 12\n Active features: 3\n Active releases: 0\n Active hotfixes: 0\n\n🔄 SYNC STATUS\n Commits ahead: ↑ 2\n Commits behind: ↓ 1\n Status: ⚠️ Branch diverged from remote\n\n Recommendations:\n - Pull latest changes: git pull\n - Push your commits: git push\n\n📝 WORKING DIRECTORY\n Modified: ● 3 files\n Added: ✚ 5 files\n Deleted: ✖ 1 file\n Untracked: ? 2 files\n Total changes: 11 files\n\n Status: ⚠️ Uncommitted changes\n\n📈 COMMIT HISTORY\n Commits on branch: 5\n Commits since base: 7\n Last commit: 2 hours ago\n Author: John Doe <john@example.com>\n\n🎯 MERGE TARGET\n Will merge to: develop\n Merge status: ✓ Ready (no conflicts)\n\n Estimated files affected: 12\n Estimated lines changed: +245 -87\n\n🏷️ VERSION INFO\n Current production: v1.2.0 (on main)\n Last release: 3 days ago\n Next suggested: v1.3.0 (based on commits)\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n```\n\n### 3. Branch-Specific Information\n\n**For Feature Branches:**\n```\n🌿 FEATURE BRANCH: feature/user-authentication\n\nBranch info:\n Created: 2 days ago\n Base branch: develop\n Merge target: develop\n\nProgress:\n Commits: 5\n Files changed: 12\n Lines added: 245\n Lines removed: 87\n\nStatus:\n ✓ No merge conflicts with develop\n ✓ Branch is up to date with remote\n ⚠️ 3 uncommitted changes\n ⚠️ Tests not run recently\n\nNext steps:\n 1. Commit your changes\n 2. Run tests: npm test\n 3. Push to remote: git push\n 4. When ready: /finish\n```\n\n**For Release Branches:**\n```\n🚀 RELEASE BRANCH: release/v1.3.0\n\nRelease info:\n Version: v1.3.0\n Created: 1 day ago\n Base branch: develop\n Merge targets: main, develop\n\nRelease contents:\n Features: 5\n Bug fixes: 3\n Performance: 1\n Total commits: 15\n\nVersion analysis:\n Current: v1.2.0\n Proposed: v1.3.0\n Increment: MINOR (new features)\n\nChecklist:\n ✓ CHANGELOG.md updated\n ✓ Version in package.json\n ⚠️ Tests not run\n ✗ No tag created yet\n\nNext steps:\n 1. Run final tests: npm test\n 2. Review CHANGELOG.md\n 3. Create PR: gh pr create\n 4. Get approvals\n 5. Finish release: /finish\n```\n\n**For Hotfix Branches:**\n```\n🔥 HOTFIX BRANCH: hotfix/critical-security-patch\n\nHotfix info:\n Issue: critical-security-patch\n Created: 2 hours ago\n Base branch: main\n Merge targets: main, develop\n Severity: CRITICAL\n\nVersion info:\n Current production: v1.2.0\n Hotfix version: v1.2.1\n Increment: PATCH\n\nStatus:\n ✓ Fix implemented\n ✓ Tests passing\n ⚠️ Not yet deployed\n ⚠️ 2 uncommitted changes\n\n⚠️ URGENT: This is a critical production hotfix!\n\nNext steps:\n 1. Commit remaining changes\n 2. Final testing\n 3. Create emergency PR\n 4. Get fast-track approval\n 5. Finish and deploy: /finish\n 6. Monitor production\n```\n\n**For Main Branch:**\n```\n🏠 MAIN BRANCH (Production)\n\nProduction info:\n Latest tag: v1.2.0\n Released: 3 days ago\n Last commit: 3 days ago\n Status: ✓ Clean and stable\n\nActive work:\n Feature branches: 3\n Release branches: 0\n Hotfix branches: 0\n\nRecent releases:\n v1.2.0 - 3 days ago\n v1.1.5 - 1 week ago\n v1.1.4 - 2 weeks ago\n\n⚠️ WARNING: You are on the production branch!\n\nAvoid committing directly to main.\nUse feature/release/hotfix branches instead.\n\nTo start new work:\n /feature <name> - New feature\n /release <version> - New release\n /hotfix <name> - Emergency fix\n```\n\n**For Develop Branch:**\n```\n🔀 DEVELOP BRANCH (Integration)\n\nIntegration info:\n Ahead of main: 12 commits\n Last merge: 1 day ago\n Status: ✓ Stable\n\nMerged features:\n feature/user-authentication (2 days ago)\n feature/payment-gateway (1 week ago)\n feature/dashboard-redesign (2 weeks ago)\n\nActive features:\n feature/notifications (in progress)\n feature/api-v2 (in progress)\n feature/mobile-app (in progress)\n\nNext release:\n Suggested version: v1.3.0\n Estimated features: 5\n Estimated timeline: 1 week\n\nTo start new work:\n /feature <name> - Create new feature\n```\n\n### 4. All Git Flow Branches\n\nList all active Git Flow branches:\n\n```\n📋 ACTIVE BRANCHES\n\n🌿 Features (3):\n feature/notifications (2 commits, 1 day old)\n feature/api-v2 (8 commits, 1 week old)\n feature/mobile-app (15 commits, 2 weeks old)\n\n🚀 Releases (0):\n No active releases\n\n🔥 Hotfixes (0):\n No active hotfixes\n\n🏠 Main branches:\n main (production, v1.2.0)\n develop (integration, +12 commits ahead)\n\n📦 Stale branches (older than 30 days):\n feature/old-experiment (45 days old)\n feature/deprecated-feature (60 days old)\n\n Cleanup suggestion: /clean-branches\n```\n\n### 5. Recommendations\n\nProvide actionable recommendations based on status:\n\n```\n💡 RECOMMENDATIONS\n\nPriority Actions:\n 1. ⚠️ Commit your 3 uncommitted changes\n 2. ⚠️ Push 2 unpushed commits to remote\n 3. ⚠️ Pull 1 commit from remote (behind)\n 4. ℹ️ Run tests before finishing\n\nBranch Hygiene:\n - 2 stale branches can be deleted\n - feature/mobile-app is 2 weeks old (consider splitting)\n - No merge conflicts detected ✓\n\nNext Steps:\n 1. Commit changes: git add . && git commit\n 2. Pull updates: git pull\n 3. Push commits: git push\n 4. Run tests: npm test\n 5. Finish when ready: /finish\n```\n\n### 6. Error States\n\n**Not in Git Repository:**\n```\n❌ Not in a git repository\n\nInitialize git repository:\n git init\n git remote add origin <url>\n\nOr navigate to a git repository.\n```\n\n**No Git Flow Structure:**\n```\n⚠️ Git Flow structure not detected\n\nMissing branches:\n - develop (integration branch)\n - main (production branch)\n\nInitialize Git Flow:\n git flow init\n\nOr create branches manually:\n git checkout -b develop\n git checkout -b main\n```\n\n**Remote Not Configured:**\n```\n⚠️ No remote repository configured\n\nAdd remote:\n git remote add origin <repository-url>\n\nVerify remote:\n git remote -v\n```\n\n### 7. Quick Stats\n\n```\n📊 QUICK STATS\n\nCommits:\n Today: 3\n This week: 12\n This month: 45\n\nBranches:\n Features: 3 active\n Releases: 0 active\n Hotfixes: 0 active\n Other: 5\n\nContributors:\n Active this week: 4\n Total: 8\n\nRepository:\n Total commits: 1,234\n Total tags: 25\n Latest: v1.2.0\n Age: 6 months\n```\n\n### 8. Workflow Suggestions\n\nBased on current state, suggest next commands:\n\n```\n🎯 SUGGESTED NEXT COMMANDS\n\nFor current branch (feature/user-authentication):\n /finish - Complete and merge feature\n /flow-status - Refresh this status\n\nTo start new work:\n /feature <name> - New feature branch\n /release <version> - New release\n /hotfix <name> - Emergency fix\n\nRepository maintenance:\n /clean-branches - Clean up old branches\n git fetch --prune - Remove stale remote refs\n```\n\n## Related Commands\n\n- `/feature <name>` - Create feature branch\n- `/release <version>` - Create release branch\n- `/hotfix <name>` - Create hotfix branch\n- `/finish` - Complete current branch\n\n## Best Practices\n\n**Regular Status Checks:**\n- ✅ Run /flow-status daily\n- ✅ Check before starting new work\n- ✅ Verify before finishing branches\n- ✅ Monitor for stale branches\n\n**Status Indicators:**\n- ✓ Green: Good to proceed\n- ⚠️ Yellow: Attention needed\n- ✗ Red: Action required\n- ℹ️ Blue: Informational\n"}