debug-rocket-route

Stars11

Forks0

UpdatedJune 3, 2026 at 08:39

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

barthofu

barthofu/soundome

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Computer Systems AnalystsComputer and Mathematical Occupations·SOC 15-1211

SKILL.md

readonly

name	debug-rocket-route
description	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.

Debug Rocket Route

Use this skill to debug an API route in apps/server without drifting into unrelated parts of the repository.

When to use

an endpoint returns the wrong status or payload
a route is mounted but not reachable
State<Arc<ServiceLayer>> wiring is wrong
Db usage or blocking async boundaries fail
Swagger or OpenAPI registration is missing

Procedure

Locate the handler in apps/server/src/routes/.
Confirm it is exported in routes/mod.rs and mounted in apps/server/src/main.rs.
Verify request DTOs, response DTOs, and error mapping.
Check service injection through rocket::State<Arc<ServiceLayer>>.
Check database execution boundaries such as db.run, blocking behavior, and any async bridging.
Step one hop into the owning domain service if the route only forwards the work.
Apply the smallest patch that explains or fixes the failure.
Validate with the narrowest executable check available for that route or handler path.

Soundome-specific checks

Prefer thin handlers that defer to domain::services.
Avoid leaking Diesel types into the HTTP layer.
Keep HTTP error messages safe and free of secrets.
Update OpenAPI annotations when request or response shapes change.

Useful files

apps/server/src/main.rs
apps/server/src/routes/
apps/server/src/utils/database.rs
packages/domain/src/services/

More from this repository

same repository

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

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

soundome-change-routing

barthofu/soundome

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.

2026-06-0311

name	debug-rocket-route
description	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.

Debug Rocket Route

Use this skill to debug an API route in apps/server without drifting into unrelated parts of the repository.

When to use

an endpoint returns the wrong status or payload
a route is mounted but not reachable
State<Arc<ServiceLayer>> wiring is wrong
Db usage or blocking async boundaries fail
Swagger or OpenAPI registration is missing

Procedure

Locate the handler in apps/server/src/routes/.
Confirm it is exported in routes/mod.rs and mounted in apps/server/src/main.rs.
Verify request DTOs, response DTOs, and error mapping.
Check service injection through rocket::State<Arc<ServiceLayer>>.
Check database execution boundaries such as db.run, blocking behavior, and any async bridging.
Step one hop into the owning domain service if the route only forwards the work.
Apply the smallest patch that explains or fixes the failure.
Validate with the narrowest executable check available for that route or handler path.

Soundome-specific checks

Prefer thin handlers that defer to domain::services.
Avoid leaking Diesel types into the HTTP layer.
Keep HTTP error messages safe and free of secrets.
Update OpenAPI annotations when request or response shapes change.

Useful files

apps/server/src/main.rs
apps/server/src/routes/
apps/server/src/utils/database.rs
packages/domain/src/services/