Vue Frontend Review
Overview
Use this single skill to run two review tracks together for Vue projects:
- Vue compatibility track (Vue 2/3 API, migration safety, browser/runtime compatibility)
- UI guidelines track (Web Interface Guidelines compliance for UI/UX/accessibility quality)
Load both references before producing findings:
When to Use
Trigger this skill when the user asks for:
- Vue2/Vue3 compatibility review
- Vue migration risk checks
- Browser support / polyfill / transpilation compatibility checks
- UI review, accessibility audit, design/UX best-practice checks
- One-pass front-end规范审查 for Vue repos
Inputs to Collect
Identify or infer:
- Vue major version:
2.x,3.x, or mixed - Build toolchain:
Vite,Webpack,Vue CLI,Nuxt - Target browser baseline (if missing, assume modern evergreen + iOS Safari last 2 major versions)
- Review scope:
src/**/*.vue,src/**/*.ts|js, styles, plus build/config files
If key info is missing, proceed with explicit assumptions.
Workflow
- Run Vue compatibility track using compat-checklist.
- Run UI guidelines track using ui-guidelines.
- Merge findings and de-duplicate overlapping items.
- Prioritize by severity:
P0release blocker or runtime breakP1high risk regression/compatibility issueP2standards drift or preventive fix
Output Format
For each finding:
[Severity] path:line - Issue
Track: Vue-Compat | UI-Guidelines
Impact: ...
Recommendation: ...
Then provide:
Compatibility baseline usedUI guidelines source usedOpen assumptionsQuick fix plan(3-6 steps)
Practical Rules
- Prefer explicit, testable rules over style opinions.
- Do not claim browser compatibility without checking build targets and polyfills.
- For mixed Vue 2/3 migration, prefer migration-safe patterns.
- Always fetch latest Web Interface Guidelines before UI findings.
- If no issues are found, state that explicitly and include residual risks.
Source: miya511250/vue-frontend-review — distributed by TomeVault.