system-performance-improvement

name	system-performance-improvement
description	Use when Codex needs to audit or improve full-system performance across frontend, backend/API, database, deployment, scalability, bottlenecks, and risk-ranked optimization plans.

System Performance Improvement

Goal

Assess end-to-end system performance and identify bottlenecks across frontend, backend/API, database, and deployment/runtime assumptions. Recommend improvements grouped by implementation risk.

When to use

Use this skill when the user asks for overall performance audit, bottleneck analysis, scalability review, optimization roadmap, or P0/P1/P2/P3 performance priorities.

Use specialized skills for deeper lanes:

• frontend-performance-audit
• backend-api-performance-audit
• database-performance-audit
• refactor-optimization-plan

Required steps

1. Read docs/audits/project-intake-map.md if present; otherwise perform a quick project intake.
2. Identify critical user journeys:
   • first page load and navigation
   • login/bootstrap
   • library/content browse
   • quiz play/finalize/result
   • classroom dashboard/assignments/gradebook
   • leaderboard/gamification/notifications
   • admin list/detail/import flows
3. Gather evidence:
   • frontend bundle/build output and route/component structure
   • API routes, pagination, response shapes, sync heavy work
   • ORM query patterns, model indexes, migrations
   • caching/rate-limit/background-job patterns
   • deployment/static asset assumptions from README/settings
4. Find bottlenecks by layer:
   • frontend: bundle size, render churn, heavy lists, images, loading states
   • backend/API: slow endpoints, N+1, no pagination, heavy sync tasks, large responses
   • database: missing indexes, full-scan risk, transaction/lock risk, relation fan-out
   • deployment/runtime: static compression, cache headers, media/static serving, worker queues
5. Prioritize improvements by risk group:
   • A. Do now, low risk
   • B. Needs careful tests
   • C. Architectural change
6. Classify issues with P0/P1/P2/P3.
7. Write the report in Vietnamese to docs/audits/system-performance-improvement.md.

Output format

Write a Vietnamese Markdown report with:

1. Tom tat hieu nang he thong
2. Critical paths
3. Bottleneck theo layer
4. Phat hien P0/P1/P2/P3
5. Nhom cai tien A - lam ngay it rui ro
6. Nhom cai tien B - can test ky
7. Nhom cai tien C - can thay doi kien truc
8. Do luong va verification de xuat
9. Rui ro con lai

Each recommendation must name affected files/modules/routes/API/model and expected impact.

Quality checklist

• The audit covers frontend, backend/API, database, and runtime assumptions.
• Each bottleneck has evidence, not only intuition.
• Low-risk improvements are separated from architectural changes.
• Recommendations include measurable validation signals.
• The report avoids premature rewrites.

Safety rules

• Do not modify code unless the user explicitly asks.
• Do not run load tests against production.
• Do not mutate databases, run migrations, deploy, upload, delete, or reset data.
• Do not print secrets, tokens, cookies, or private rows.
• Prefer local static analysis and local dev measurements.