doctor
Run Vite Doctor diagnostics for Vite, Vue, Nitro, and Nuxt projects and use stable diagnostic codes to guide fixes. Use before review on framework projects, when Doctor/Vite Doctor/Nuxt Doctor/diagnostics are requested, or when framework-specific runtime issues are suspected.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- doctor
- description
- Run Vite Doctor diagnostics for Vite, Vue, Nitro, and Nuxt projects and use stable diagnostic codes to guide fixes. Use before review on framework projects, when Doctor/Vite Doctor/Nuxt Doctor/diagnostics are requested, or when framework-specific runtime issues are suspected.
03 SKILL.md 正文
Doctor
Quick Start
Run Doctor from the target project root:
pnpm dlx vite-doctor . # or npx/bunx/yarn dlx
For Nuxt projects, the recommended workflow is:
pnpm add -D vite-doctor
export default defineNuxtConfig({
modules: ["vite-doctor/nuxt"],
});
pnpm nuxt doctor
The standalone CLI also works for Nuxt one-off runs, CI fallback, or monorepo scans.
Workflow
- Run Doctor against the target project or package; install dependencies first if needed.
- Read each Diagnostic Code,
why,fix, docs URL, severity, confidence, and source location. - Open
https://vite-doctor.onmax.me/diagnostics/CODEbefore recommending remediation. - Prefer the smallest fix that addresses the Diagnostic and preserves project conventions.
- Run the narrowest relevant verification after editing.
- Use
--format jsonor--format sarifonly when structured output is needed.
Rules
- Use
vite-doctorfor Vite, Vue, Nitro, and Nuxt projects; do not invent framework-specific packages or binaries. - Treat Rule IDs as execution/filtering selectors.
- Treat Diagnostic Codes as the stable remediation identity for docs, fixes, and user-facing explanations.
- Use Doctor terms consistently: Doctor, Rule, Rule Pack, Diagnostic Code, and Diagnostic.
- Keep code edits scoped to reported Diagnostics unless the user asks for broader cleanup.
04 同仓库更多 Skills
web-perf
Audit, diagnose, or optimize website loading and interaction performance, Core Web Vitals, and Lighthouse performance scores.
unlighthouse
Run Google Lighthouse on every page of a site with the unlighthouse CLI, and fail CI on low scores with unlighthouse-ci. Use when a task mentions unlighthouse, unlighthouse-ci, site-wide Lighthouse scans, performance budgets in CI, unlighthouse.config.ts, defineUnlighthouseConfig, scanner.exclude, dynamic sampling, the authenticate hook, or a scan that never exits, skips pages, or refuses to clear its output folder.
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
fixing-accessibility
Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors. Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance.
better-accessibility
Reviews and fixes keyboard and focus behavior, ARIA, accessible names, forms, screen-reader announcements, motion and zoom in your project against WCAG 2.2.
web-perf
Audit, diagnose, or optimize website loading and interaction performance, Core Web Vitals, and Lighthouse performance scores.