メニュー
Trigger: command, validate, PR, branch, run lint, run build, secrets. Correct pnpm commands, branch naming, PR checklist, and secrets rules for spotiarr.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Trigger: Docker, docker-compose, deploy, container, volume, DOWNLOADS_DIR, PUID, PGID, update, self-hosted. spotiarr Docker setup: services, volumes, env vars, update flow.
Trigger: Zustand, store, client state, usePlayerStore, usePreferencesStore, playerUISlice, ephemeral state, persist middleware. spotiarr Zustand rules: 2 stores + player UI slice, server state stays in TanStack Query, patterns for selectors and bulk hooks.
Trigger: architecture, layer, placement, where does X go, new feature, repo structure. spotiarr layer rules: backend DDD-lite, frontend hooks/store/views.
Trigger: i18n, translation, i18next, language, locale, new language, translate. spotiarr frontend i18n: key conventions, useLanguageSync override, adding languages.
Trigger: SSE, server-sent events, real-time, useServerEvents, live updates, EventSource. spotiarr SSE pattern: frontend EventSource hook, backend AppEventBus, 4 event types.
Run and configure oxlint — the high-performance JavaScript/TypeScript linter built on the Oxc compiler stack. Use this skill whenever working in a project that has oxlint installed (check for `oxlint` in package.json devDependencies or an `.oxlintrc.json` / `oxlint.config.ts` config file). This includes when you need to lint code after making changes, fix linting errors, configure oxlint rules/plugins, set up or modify `.oxlintrc.json`, or migrate from ESLint.
| name | spotiarr-workflow |
| description | Trigger: command, validate, PR, branch, run lint, run build, secrets. Correct pnpm commands, branch naming, PR checklist, and secrets rules for spotiarr. |
| license | Apache-2.0 |
| metadata | {"author":"gentleman-programming","version":"2.1"} |
Load when running commands, validating changes, creating PRs, managing branches, or checking secrets.
.env, tokens, or credentials. Use .env.example as source of truth.SPOTIARR_TOKEN (instance auth token) is a secret — treat like a password, never hardcode or log it. Generate with openssl rand -base64 32.--no-verify is forbidden).| Scope | Validate with |
|---|---|
| Frontend only | pnpm --filter frontend run lint → pnpm --filter frontend run test:run → pnpm --filter frontend run build |
| Backend only | pnpm --filter backend run lint → pnpm --filter backend run test:run → pnpm --filter backend run build |
| Shared or cross-workspace | pnpm lint → pnpm test → pnpm build |
Branch naming:
| Type | Prefix | Example |
|---|---|---|
| Feature | feature/ | feature/add-playback-retry |
| Fix | fix/ | fix/sse-reconnect-loop |
| Refactor | refactor/ | refactor/backend-di-wiring |
| Docs | docs/ | docs/update-env-guide |
| Chore | chore/ | chore/bump-deps |
PR checklist: branch up to date with main · lint + build passing · PR body has what/why/verification · screenshots for UI changes.
PR sizing policy:
| Situation | Action |
|---|---|
| Slice over 400 LOC | Default: split into chained-to-main PRs (see chained-pr skill). |
ask-on-risk | Only when the requester explicitly asks to be consulted before splitting. |
size:exception | Reserved for irreducible atomic refactors that cannot be split without breaking review or correctness. Label the PR and justify in the body. |
The 400 LOC threshold protects review focus. Prefer many small, sequentially reviewable PRs over one oversized PR. size:exception is the rare escape hatch, not a routine option.
Key commands:
pnpm dev # full dev stack
pnpm lint && pnpm test && pnpm build # broad validation
pnpm test # all workspace tests
pnpm --filter frontend run test:run # frontend unit tests
pnpm --filter backend run test:run # backend unit tests
pnpm --filter backend run prisma:migrate:deploy
gh pr create # title must follow Conventional Commits