一键在 Manus 中运行任何 Skill

spotiarr-architecture

星标36

分支6

更新时间2026年6月10日 18:00

Trigger: architecture, layer, placement, where does X go, new feature, repo structure. spotiarr layer rules: backend DDD-lite, frontend hooks/store/views.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

mralexsaavedra

mralexsaavedra/spotiarr

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Activation Contract

Load when deciding where new code belongs across backend, frontend, or shared.

Hard Rules

Dependencies point inward: presentation → application → domain; infrastructure implements inner-layer contracts — never the reverse.
Prisma, Redis, yt-dlp, external HTTP → infrastructure/ only. Never in domain/ or presentation/.
All use-cases and services register at: apps/backend/src/container.ts (NOT in infrastructure/ — it's at src/ root).
Server state in frontend → TanStack Query (hooks/queries, hooks/mutations). Client state → Zustand slices under store/ (one file per domain).
Real-time SSE sync → useServerEvents hook. Do not add manual SSE subscriptions elsewhere.
Shared DTOs, enums, utilities → packages/shared/. Never duplicate in apps.
All Spotify HTTP calls must go through CircuitBreaker.execute() (infrastructure/external/circuit-breaker.ts). Never add a raw Spotify HTTP call without wrapping it. The circuit persists open state via onOpen callback → settings → restored on restart.

Decision Gates

Backend — where does it go?
  Business rule / invariant?         → domain/
  Use-case orchestration?            → application/
  DB, queues, APIs, filesystem?      → infrastructure/
  HTTP routes, controllers, SSE?     → presentation/
  Cross-cutting request guards?      → presentation/middleware/

Frontend — where does it go?
  UI rendering / composition?        → components/
  Page-level screens?                → views/
  View logic / orchestration?        → hooks/
  Remote fetch / mutate?             → services/ + hooks/queries|mutations
  App-wide client state?             → store/
  Ephemeral gate/overlay state?      → local useState in the controller hook (NOT a Zustand store; see useTokenGate)

Cross-cutting types / utils?         → packages/shared/

References

DI container: apps/backend/src/container.ts
Store pattern: apps/frontend/src/store/
Request guards: apps/backend/src/presentation/middleware/
Auth gate hook: apps/frontend/src/hooks/controllers/useTokenGate.ts

同仓库更多 Skills

同仓库

spotiarr-docker

mralexsaavedra/spotiarr

Trigger: Docker, docker-compose, deploy, container, volume, DOWNLOADS_DIR, PUID, PGID, update, self-hosted. spotiarr Docker setup: services, volumes, env vars, update flow.

2026-06-2436

spotiarr-zustand

mralexsaavedra/spotiarr

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.

2026-06-1836

spotiarr-workflow

mralexsaavedra/spotiarr

Trigger: command, validate, PR, branch, run lint, run build, secrets. Correct pnpm commands, branch naming, PR checklist, and secrets rules for spotiarr.

2026-06-1036

spotiarr-i18n

mralexsaavedra/spotiarr

Trigger: i18n, translation, i18next, language, locale, new language, translate. spotiarr frontend i18n: key conventions, useLanguageSync override, adding languages.

2026-06-1036

spotiarr-sse

mralexsaavedra/spotiarr

Trigger: SSE, server-sent events, real-time, useServerEvents, live updates, EventSource. spotiarr SSE pattern: frontend EventSource hook, backend AppEventBus, 4 event types.

2026-06-1036

oxlint

mralexsaavedra/spotiarr

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.

2026-06-0636

name	spotiarr-architecture
description	Trigger: architecture, layer, placement, where does X go, new feature, repo structure. spotiarr layer rules: backend DDD-lite, frontend hooks/store/views.
license	Apache-2.0
metadata	{"author":"gentleman-programming","version":"2.0"}

Activation Contract

Load when deciding where new code belongs across backend, frontend, or shared.

Hard Rules

Dependencies point inward: presentation → application → domain; infrastructure implements inner-layer contracts — never the reverse.
Prisma, Redis, yt-dlp, external HTTP → infrastructure/ only. Never in domain/ or presentation/.
All use-cases and services register at: apps/backend/src/container.ts (NOT in infrastructure/ — it's at src/ root).
Server state in frontend → TanStack Query (hooks/queries, hooks/mutations). Client state → Zustand slices under store/ (one file per domain).
Real-time SSE sync → useServerEvents hook. Do not add manual SSE subscriptions elsewhere.
Shared DTOs, enums, utilities → packages/shared/. Never duplicate in apps.
All Spotify HTTP calls must go through CircuitBreaker.execute() (infrastructure/external/circuit-breaker.ts). Never add a raw Spotify HTTP call without wrapping it. The circuit persists open state via onOpen callback → settings → restored on restart.

Decision Gates

Backend — where does it go?
  Business rule / invariant?         → domain/
  Use-case orchestration?            → application/
  DB, queues, APIs, filesystem?      → infrastructure/
  HTTP routes, controllers, SSE?     → presentation/
  Cross-cutting request guards?      → presentation/middleware/

Frontend — where does it go?
  UI rendering / composition?        → components/
  Page-level screens?                → views/
  View logic / orchestration?        → hooks/
  Remote fetch / mutate?             → services/ + hooks/queries|mutations
  App-wide client state?             → store/
  Ephemeral gate/overlay state?      → local useState in the controller hook (NOT a Zustand store; see useTokenGate)

Cross-cutting types / utils?         → packages/shared/

References

DI container: apps/backend/src/container.ts
Store pattern: apps/frontend/src/store/
Request guards: apps/backend/src/presentation/middleware/
Auth gate hook: apps/frontend/src/hooks/controllers/useTokenGate.ts