Use this skill when the user explicitly requests optimize, asks for an optimization scan, or only wants to look at ux、perf、code a certain type of improvement.
Do not use for:
- Directly fixing a single bug
- A formal security review
- Large-scale refactoring without evidence
- Replacing requirements analysis or design documents
Core approach
- First define the scope: full, frontend, backend, or a specified directory.
- When the scope is very large, first provide a size estimate and hotspots, then decide whether to scan everything.
- Organize check items according to the mode:
full、ux、perf、code。 - All conclusions must be grounded in specific code evidence; do not make vague suggestions.
- By default, output a sorted optimization report; only enter implementation when the user explicitly names a specific item.
Output requirements
- First provide a project overview and scan scope
- Sort findings by impact priority
- Each suggestion should explain the benefits, costs, and prerequisites at the same time
- When there are no obvious issues, state that clearly and point out blind spots or unscanned areas
Expand as needed
- Scope selection:
references/scope-selection.md - Mode definition:
references/optimize-modes.md - Report format:
references/report-format.md - Output template:
templates/optimize-report.md