菜单
Use when the task involves choosing how to validate a change in this repository, deciding whether to inspect a running dev server, run unit tests, run Playwright UI screenshot tests, or avoid unnecessary builds.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when adding or refactoring frontend features in this repository and you need to prevent large single-file changes, oversized entry files, mixed responsibilities, or giant App.tsx/Home.tsx style implementations. Apply it when a task risks stuffing UI, state, effects, data access, and helper logic into one file instead of splitting work into focused components, hooks, services, utils, and types.
Use when adding, refactoring, or reviewing frontend runtime behavior in this repository, especially visualizers, lyrics animation, Framer Motion usage, useMotionValueEvent, requestAnimationFrame, ResizeObserver, high CPU reports, jank, per-character or per-frame animation, React state update frequency, and performance-sensitive UI paths.
Use when the user refers to repository-specific terms such as home view, panel, local library, Navidrome view, visualizer mode, queue, current song, search state, or other spoken component/state names and you need to map them quickly to the concrete files, hooks, stores, and code ownership in this project.
Use when making code, workflow, testing, or documentation changes in this repository and you need targeted project-specific facts from README files before editing. Read only relevant snippets from root README.md or src/README.md; do not load whole README files unless the user explicitly asks for a full document review.
Use when implementing, refactoring, or reviewing code in this repository and the task may duplicate existing helpers, libraries, visualizer utilities, lyrics utilities, font/color helpers, list virtualization, icon usage, i18n, playback adapters, or service patterns. Trigger before writing new utility functions or installing/hand-rolling functionality already present in the project.
Use when adding, changing, refactoring, or reviewing user-facing settings in this repository, especially visual settings, appearance settings, visualizer tuning, background/theme/typography controls, playback/integration/storage/desktop/lab settings, or any setting that should be importable/exportable or invokable from the command palette.
| name | testing-strategy |
| description | Use when the task involves choosing how to validate a change in this repository, deciding whether to inspect a running dev server, run unit tests, run Playwright UI screenshot tests, or avoid unnecessary builds. |
这个 skill 用于判断当前任务应该采用哪一种验证方式。
如果当前用户终端已经在运行热加载开发服务器，例如 vercel dev、vite、npm run dev、npm run dev:electron，不要再额外运行构建来“测试”问题。
优先做这些事：
优先使用 Playwright UI 测试：
npm run test:uinpm run test:ui:update适用场景：
注意：
test/ui/*.spec.ts-snapshots/test-results/ 是临时产物，不应提交优先使用 Vitest 单元测试：
npm run test:unit适用场景：
src/utils/**src/stores/**src/hooks/** 中不依赖真实浏览器渲染的逻辑同步与本地存储也按纯逻辑路径处理：
src/services/sync/** 的 schema、fingerprint、Merkle bucket、主题注册表迁移和 coordinator 分支，优先看 test/unit/sync/**src/services/themeCache.ts、src/services/db.ts 的缓存边界，优先看 test/unit/cache/** 和相关 service 测试不要默认通过完整打包来验证。
优先顺序：
涉及文件通常包括：
.github/workflows/*.ymlelectron/main.cjspackage.json如果已有 dev server 在跑：
npm run build通常不需要运行测试。
只在以下情况补充验证：
如果文档只是补充当前模块边界、模式列表或设计说明，通常只需要静态核对路径和命令；只有当文档修正了同步 API、部署命令或测试入口时，才运行对应的最小单测或配置检查。
npm run test:unitnpm run test:uinpm run test:ui:update同步/主题文档涉及协议或持久化边界时，可优先选择：
npm run test:unit -- test/unit/sync/themeSyncRegistry.test.tsnpm run test:unit -- test/unit/cache/themeCache.test.tstest-results/ 之类的临时产物提交进仓库