diff --git a/.claude/skills/vue-optimizer/SKILL.md b/.claude/skills/vue-optimizer/SKILL.md new file mode 100644 index 00000000..d9015e40 --- /dev/null +++ b/.claude/skills/vue-optimizer/SKILL.md @@ -0,0 +1,130 @@ +--- +name: vue-optimizer +description: Analyzes Vue 3 component structure and produces a prioritized, report-only set of performance and code-reuse optimization suggestions. Use this skill when asked to review, audit, profile, or optimize Vue components (.vue files) for performance, re-renders, reactivity efficiency, or duplicated UI/logic. Does NOT modify files. +--- + +# Vue Component Optimizer (Analyze & Report) + +This skill inspects the Vue 3 Composition API frontend and reports **prioritized +optimization opportunities**. It is **report-only**: it never edits `.vue` files. +Surface findings; let the user decide what to apply. If they ask you to apply a +finding afterward, delegate the `.vue` edit to the **vue-expert** subagent per +the project's mandatory rule. + +## When to use + +- "Analyze / audit / review / optimize the Vue components" +- "Why is this page slow / re-rendering too much?" +- "Find duplicated components or logic we can share" +- Before a refactor, to scope where the wins are + +## Scope & priorities + +Primary focus: **performance**. Secondary: **code reuse**. Stay conservative — +report opportunities with evidence (`file:line`), never guess. Do not invent +problems; if a component is already clean, say so. + +## Analysis workflow + +1. **Inventory the components.** List `client/src/views/*.vue` and + `client/src/components/*.vue`. Note each component's template size and + `setup()` logic size. +2. **Read each component** (template, `