Vue
Use this skill to keep Vue work grounded in maintainable architecture, predictable delivery, and framework-appropriate conventions.
Intent Router
| Need |
Load |
| core conventions, structure, review priorities, and common red flags for Vue |
references/best-practices.md |
| setup, migration, testing, build, delivery, and day-two workflow guidance for Vue |
references/workflows.md |
Quick Start
- Confirm Vue version and host environment, Composition API, Options API, or mixed posture, router and store strategy, and app, library, or admin-surface scope.
- Identify whether the task is greenfield scaffolding, incremental refactoring, troubleshooting, migration planning, or code review.
- Apply the defaults in
references/best-practices.md before proposing custom architecture.
- Prefer the smallest change set that improves clarity, safety, operability, and long-term maintainability.
Workflow
- start from the owning feature folder or route
- keep composables honest about the state they own
- protect route and event semantics during refactors
- verify the Vite build and test path after changes
Typical Focus Areas
- Vue version and host environment
- Composition API, Options API, or mixed posture
- router and store strategy
- app, library, or admin-surface scope
Outputs to Prefer
- summarize API posture and host environment first
- group findings by components, composables, state, routing, and tests
- recommend feature-by-feature modernization instead of broad rewrites
First Response Pattern
- restate Vue version, API posture, and router or store strategy before suggesting changes
- anchor the plan at the owning feature, route, composable, or store boundary
- name the verification loop up front:
npm run test, npm run build, and a smoke test of the affected route or state flow
Common Requests
Review this Vue feature for component structure, Composition API or composable usage, Pinia state ownership, routing, and test gaps.
Refactor this Vue workflow to simplify composable or store ownership and preserve router and component behavior.
Safety Notes
- preserve externally visible behavior unless the user explicitly requests a redesign or a breaking change
- avoid style-only churn when the current repository already has working conventions and automation
Source: alisonaquinas/llm-web-design-skills — distributed by TomeVault.
1---2name: alisonaquinas-llm-web-design-skills-vue3description: Vue4---56# Vue78Use this skill to keep Vue work grounded in maintainable architecture, predictable delivery, and framework-appropriate conventions.910## Intent Router1112| Need | Load |13| --- | --- |14| core conventions, structure, review priorities, and common red flags for Vue | `references/best-practices.md` |15| setup, migration, testing, build, delivery, and day-two workflow guidance for Vue | `references/workflows.md` |1617## Quick Start18191. Confirm Vue version and host environment, Composition API, Options API, or mixed posture, router and store strategy, and app, library, or admin-surface scope.202. Identify whether the task is greenfield scaffolding, incremental refactoring, troubleshooting, migration planning, or code review.213. Apply the defaults in `references/best-practices.md` before proposing custom architecture.224. Prefer the smallest change set that improves clarity, safety, operability, and long-term maintainability.2324## Workflow2526- start from the owning feature folder or route27- keep composables honest about the state they own28- protect route and event semantics during refactors29- verify the Vite build and test path after changes3031## Typical Focus Areas3233- Vue version and host environment34- Composition API, Options API, or mixed posture35- router and store strategy36- app, library, or admin-surface scope3738## Outputs to Prefer3940- summarize API posture and host environment first41- group findings by components, composables, state, routing, and tests42- recommend feature-by-feature modernization instead of broad rewrites4344## First Response Pattern4546- restate Vue version, API posture, and router or store strategy before suggesting changes47- anchor the plan at the owning feature, route, composable, or store boundary48- name the verification loop up front: `npm run test`, `npm run build`, and a smoke test of the affected route or state flow4950## Common Requests5152```text53Review this Vue feature for component structure, Composition API or composable usage, Pinia state ownership, routing, and test gaps.54```5556```text57Refactor this Vue workflow to simplify composable or store ownership and preserve router and component behavior.58```5960## Safety Notes6162- preserve externally visible behavior unless the user explicitly requests a redesign or a breaking change63- avoid style-only churn when the current repository already has working conventions and automation6465---66> Source: [alisonaquinas/llm-web-design-skills](https://github.com/alisonaquinas/llm-web-design-skills) — distributed by [TomeVault](https://tomevault.io).67<!-- tomevault:4.0:skill_md:2026-04-19 -->