reference-semantics

스타11

포크0

업데이트2026년 6월 3일 08:39

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

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

barthofu

barthofu/soundome

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Reference Semantics

Use this skill when changes affect how Soundome stores, merges, replaces, or interprets references.

Core model

Source: user-requested origin
Provider: actual downloadable audio source
Metadata: durable identifiers and URLs that should survive source changes
Reference: supporting reference data

Rules to preserve

Replacing audio does not mean losing durable metadata identifiers.
Deduplication and quality replacement must preserve future matchability.
Repository code and model code must agree on reference semantics.
set_references and related persistence logic are architecture-sensitive.

Procedure

Identify whether the change lives in models, domain services, or Diesel repositories.
Check the current merge and replacement path before editing.
Decide explicitly whether each affected reference should be replaced or merged.
Update the model logic and repository logic together when required.
Validate the behavior with the narrowest affected flow, especially deduplication or finalization.

Useful files

packages/shared/src/models/
packages/domain/src/services/download_service.rs
packages/database/src/repositories/
docs/architecture/design.md

이 저장소의 다른 Skills

같은 저장소

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

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	reference-semantics
description	Use when changing Track, Album, Artist, Playlist, Reference, ReferenceType, deduplication merge logic, transpose logic, or Diesel repository reference handling in Soundome.

Reference Semantics

Use this skill when changes affect how Soundome stores, merges, replaces, or interprets references.

Core model

Source: user-requested origin
Provider: actual downloadable audio source
Metadata: durable identifiers and URLs that should survive source changes
Reference: supporting reference data

Rules to preserve

Replacing audio does not mean losing durable metadata identifiers.
Deduplication and quality replacement must preserve future matchability.
Repository code and model code must agree on reference semantics.
set_references and related persistence logic are architecture-sensitive.

Procedure

Identify whether the change lives in models, domain services, or Diesel repositories.
Check the current merge and replacement path before editing.
Decide explicitly whether each affected reference should be replaced or merged.
Update the model logic and repository logic together when required.
Validate the behavior with the narrowest affected flow, especially deduplication or finalization.

Useful files

packages/shared/src/models/
packages/domain/src/services/download_service.rs
packages/database/src/repositories/
docs/architecture/design.md