soundome-change-routing

Estrelas11

Forks0

Atualizado3 de junho de 2026 às 08:39

Use when identifying the right Soundome crate, entry point, owning abstraction, or validation command before changing code. Useful for routing work across server, domain, database, fetcher, downloader, tagger, organizer, config, shared, and web.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

barthofu

barthofu/soundome

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	soundome-change-routing
description	Use when identifying the right Soundome crate, entry point, owning abstraction, or validation command before changing code. Useful for routing work across server, domain, database, fetcher, downloader, tagger, organizer, config, shared, and web.

Soundome Change Routing

Use this skill when you need to decide where a change belongs before editing code.

Routing guide

apps/server: HTTP handlers, route exposure, Swagger, static serving
apps/web: admin UI and frontend interactions
packages/domain: business workflow orchestration
packages/database: Diesel persistence and repository semantics
packages/fetcher: source URL parsing and source metadata
packages/downloader: provider resolution and audio downloads
packages/tagger: metadata enrichment and audio tagging
packages/organizer: filesystem placement
packages/config: typed configuration and overrides
packages/shared: models, errors, shared helpers, proxy-aware HTTP

Procedure

Start from the user-visible failing behavior or requested feature.
Decide whether the owning surface is UI, HTTP, orchestration, persistence, source integration, provider integration, tagging, organizing, or config.
Pick the nearest code path that directly computes or controls the behavior.
Identify the narrowest validation command for that slice.
Only after that, branch into the targeted crate or module.

Useful references

docs/architecture/repository-map.md
docs/architecture/design.md
docs/workflows/download.md

Mais deste repositório

mesmo repositório

add-diesel-migration

barthofu/soundome

Use when adding or modifying SQLite schema, Diesel migrations, repository persistence, schema.rs, entities, mappers, or repository implementations. Safely update migrations and keep Soundome reference semantics intact.

2026-06-0311

debug-rocket-route

barthofu/soundome

Use when debugging a Rocket route, API endpoint, request/response mismatch, State injection issue, Db usage issue, OpenAPI registration problem, or route-level error mapping in apps/server.

2026-06-0311

extend-download-workflow

barthofu/soundome

Use when changing DownloadService, playlist sync, source-to-provider flow, staging logic, deduplication, tagging handoff, organize step, or track finalization without breaking Soundome workflow invariants.

2026-06-0311

manual-validation-flow

barthofu/soundome

Use when changing pending validation behavior, needs_validation flags, approval or rejection flow, validation routes, staged file finalization, or the web admin validation UI in Soundome.

2026-06-0311

proxy-aware-http

barthofu/soundome

Use when adding or fixing direct HTTP calls, reqwest clients, proxy support, no_proxy behavior, rotating proxy behavior, or network code that should respect Soundome proxy configuration.

2026-06-0311

reference-semantics

barthofu/soundome

Use when changing Track, Album, Artist, Playlist, Reference, ReferenceType, deduplication merge logic, transpose logic, or Diesel repository reference handling in Soundome.

2026-06-0311

name	soundome-change-routing
description	Use when identifying the right Soundome crate, entry point, owning abstraction, or validation command before changing code. Useful for routing work across server, domain, database, fetcher, downloader, tagger, organizer, config, shared, and web.

Soundome Change Routing

Use this skill when you need to decide where a change belongs before editing code.

Routing guide

apps/server: HTTP handlers, route exposure, Swagger, static serving
apps/web: admin UI and frontend interactions
packages/domain: business workflow orchestration
packages/database: Diesel persistence and repository semantics
packages/fetcher: source URL parsing and source metadata
packages/downloader: provider resolution and audio downloads
packages/tagger: metadata enrichment and audio tagging
packages/organizer: filesystem placement
packages/config: typed configuration and overrides
packages/shared: models, errors, shared helpers, proxy-aware HTTP

Procedure

Start from the user-visible failing behavior or requested feature.
Decide whether the owning surface is UI, HTTP, orchestration, persistence, source integration, provider integration, tagging, organizing, or config.
Pick the nearest code path that directly computes or controls the behavior.
Identify the narrowest validation command for that slice.
Only after that, branch into the targeted crate or module.

Useful references

docs/architecture/repository-map.md
docs/architecture/design.md
docs/workflows/download.md