Claude Skills by Dankosik

Unit: Use when bound ACCEPTANCE_UNIT_LEAD for an implementation unit or final delivery validation. Own the assigned boundary; Skip sibling scheduling.

Task messages: Use when asked to turn rough input into a clear repository task or handoff. Write as to a capable colleague, preserving intent and leaving execution choices to them.

Use when a REST change can alter what a deployed client distinguishes across success, error, replay, async recovery, or compatibility.

Use when a Go change adds, mounts, moves, or reviews Chi routes, middleware, fallbacks, CORS, or bounded route identity.

Use to implement an authorized Go change with accepted behavior and source ownership, including focused tests and cleanup.

Use when correctness depends on overlapping goroutines, publication of shared state, bounded concurrent work, or stopping and joining goroutines.

Use when identity, durable schema, backfill, projection, derived surfaces, retention, or datastore fit changes where a datum is true over its lifecycle.

Use when SQL or transaction boundaries, query semantics, cache freshness or invalidation, or bounded fallback determine a request path.

Use when CI/CD, artifact provenance, drift, containers, migrations, rollout, or control-plane evidence determines whether a candidate may ship.

Use when cross-service consistency, replay, ordering, compensation, redrive, or reconciliation must survive process or owner boundaries.

Use when business acceptance, rejection, transitions, replay meaning, or effect order changes what states and moves are legal.

Use when grpc-go composition, interceptors, status mapping, streaming, credentials, Protobuf compatibility, limits, health, or shutdown changes an RPC.

Use when a Go change affects caller-visible error identity, context lifetime, nil or zero behavior, aliasing, method sets, or resource ownership.

Use when accepted Go behavior is closed but its package, file, canonical source, dependency direction, or proof location is not.

Use when simplifying Go control flow, predicates, names, or helpers while preserving observable behavior.

Use when the module's Go version can change a language or standard-library choice in the planned diff, or modernization is requested.

Use when an operational question needs a signal, SLI, SLO, or alert, or when an emitted field or label changes correlation, privacy, cardinality, or cost.

Use when a workload or budget can change the mechanism, or when an optimization claim needs a comparable baseline, attribution, and delta.

Use for any Go decision or review involving end-to-end deadlines, per-attempt timeouts, retry or backoff counts, overload, readiness, drain, shutdown, or rollout recovery.

Use when identity, authorization, tenancy, tokens, secrets, injection, SSRF, abuse, or another trust boundary changes what an attacker can reach.

Use when a Go diff adds layers, abstractions, compatibility shims, or parallel paths whose current necessity must be assessed.

Use when a change adds or changes a component crossing, protocol, source of truth, consistency expectation, failure model, or migration topology.

Use when a bug, flaky test, build failure, hang, deadlock, timeout, or regression has an unknown cause and needs diagnosis or authorized root-cause repair.

Use for test-only changes or non-routine fixtures and harnesses, selecting cases and assertions from accepted behavior during implementation.

Use while implementing Go tests when the observable failure, deterministic control, or smallest proving layer is non-obvious.

Use for Go verification-only work or when deciding whether existing evidence supports a requested claim at its stated scope.

Grill: Use only on an explicit ask to grill/stress-test a plan or decision. Own one question per turn with a recommendation; Skip ordinary answers.

Idea convergence: Use when a raw or solution-led idea lacks one buildable direction. Own problem/outcome/MVP/assumptions/decision; Skip engineering-ready work.

Use when an in-progress merge, rebase, cherry-pick, or revert has conflicted hunks that require intent reconstruction, resolution, proof, and continuation.

Ledger routing: Use only as LEDGER_ORCHESTRATOR for a ready persisted Implementation ledger. Own routing; Skip unit work.

Task ledger: Use when closed decisions need ordered tasks.md. Own boundaries, proof, and reopen conditions; Skip behavior and implementation.

Spec authoring: Use for delegated spec.md synthesis or repair from accepted inputs. Own falsifiable behavior; Skip phase and review ownership.

Problem frame: Use when a chosen change needs behavior delta, scope, constraints, or readiness. Own frame/next owner; Skip ideation, design, and tasks.

Thermo-nuclear review: Use only on an explicit ask for a thermo-nuclear, thermonuclear, harsh, or deep code-quality audit of one fixed candidate. Own read-only structural simplification and maintainability findings; Skip ordinary review and implementation.

Principal, credential, permission, tenant-isolation, and revocation depth reference reached from go-security.

Cache value, key, freshness, fill, invalidation, degradation, and value depth reference reached from go-db-cache.

Durable-state interleaving, arbitration, conflict, fencing, and singleton depth reference reached from go-concurrency.

Cross-component topology, state, coordination, resilience, capacity, and evolution depth reference.

Durable acceptance, identity, leases, effects, retries, schedules, and recovery depth reference.

External provider request identity, bounded attempts, ambiguity, callbacks, reconciliation, and migration depth reference.

PostgreSQL latency, load, locks, connections, WAL, vacuum, planner, and capacity depth reference.

Relational identity, cardinality, invariant, constraint, lifecycle, and migration depth reference.

Production symptom, timeline, localization, causal falsification, recovery, and prevention depth reference.

Broker publish, consume, identity, ordering, acknowledgement, redrive, replay, and business-effect depth reference.