All authors

Claude Skills by Dankosik
github.com/Dankosik44 skills0 installs3 views
- Acceptance Unit LeadUnit: Use when bound ACCEPTANCE_UNIT_LEAD for an implementation unit or final delivery validation. Own the assigned boundary; Skip sibling scheduling.Votes: 0GitHub stars: 7
- Agent Prompt ComposerTask 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.Votes: 0GitHub stars: 7
- Go Api ContractUse when a REST change can alter what a deployed client distinguishes across success, error, replay, async recovery, or compatibility.Votes: 0GitHub stars: 7
- Go ChiUse when a Go change adds, mounts, moves, or reviews Chi routes, middleware, fallbacks, CORS, or bounded route identity.Votes: 0GitHub stars: 7
- Go CoderUse to implement an authorized Go change with accepted behavior and source ownership, including focused tests and cleanup.Votes: 0GitHub stars: 7
- Go ConcurrencyUse when correctness depends on overlapping goroutines, publication of shared state, bounded concurrent work, or stopping and joining goroutines.Votes: 0GitHub stars: 7
- Go Data ArchitectureUse when identity, durable schema, backfill, projection, derived surfaces, retention, or datastore fit changes where a datum is true over its lifecycle.Votes: 0GitHub stars: 7
- Go Db CacheUse when SQL or transaction boundaries, query semantics, cache freshness or invalidation, or bounded fallback determine a request path.Votes: 0GitHub stars: 7
- Go Delivery PlatformUse when CI/CD, artifact provenance, drift, containers, migrations, rollout, or control-plane evidence determines whether a candidate may ship.Votes: 0GitHub stars: 7
- Go DistributedUse when cross-service consistency, replay, ordering, compensation, redrive, or reconciliation must survive process or owner boundaries.Votes: 0GitHub stars: 7
- Go Domain InvariantUse when business acceptance, rejection, transitions, replay meaning, or effect order changes what states and moves are legal.Votes: 0GitHub stars: 7
- Go GrpcUse when grpc-go composition, interceptors, status mapping, streaming, credentials, Protobuf compatibility, limits, health, or shutdown changes an RPC.Votes: 0GitHub stars: 7
- Go IdiomaticUse when a Go change affects caller-visible error identity, context lifetime, nil or zero behavior, aliasing, method sets, or resource ownership.Votes: 0GitHub stars: 7
- Go Implementation OwnershipUse when accepted Go behavior is closed but its package, file, canonical source, dependency direction, or proof location is not.Votes: 0GitHub stars: 7
- Go Language SimplifierUse when simplifying Go control flow, predicates, names, or helpers while preserving observable behavior.Votes: 0GitHub stars: 7
- Go Modern VersionUse when the module's Go version can change a language or standard-library choice in the planned diff, or modernization is requested.Votes: 0GitHub stars: 7
- Go ObservabilityUse when an operational question needs a signal, SLI, SLO, or alert, or when an emitted field or label changes correlation, privacy, cardinality, or cost.Votes: 0GitHub stars: 7
- Go PerformanceUse when a workload or budget can change the mechanism, or when an optimization claim needs a comparable baseline, attribution, and delta.Votes: 0GitHub stars: 7
- Go ReliabilityUse 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.Votes: 0GitHub stars: 7
- Go SecurityUse when identity, authorization, tenancy, tokens, secrets, injection, SSRF, abuse, or another trust boundary changes what an attacker can reach.Votes: 0GitHub stars: 7
- Go Structural QualityUse when a Go diff adds layers, abstractions, compatibility shims, or parallel paths whose current necessity must be assessed.Votes: 0GitHub stars: 7
- Go System ArchitectureUse when a change adds or changes a component crossing, protocol, source of truth, consistency expectation, failure model, or migration topology.Votes: 0GitHub stars: 7
- Go Systematic DebuggingUse when a bug, flaky test, build failure, hang, deadlock, timeout, or regression has an unknown cause and needs diagnosis or authorized root-cause repair.Votes: 0GitHub stars: 7
- Go Test ImplementationUse for test-only changes or non-routine fixtures and harnesses, selecting cases and assertions from accepted behavior during implementation.Votes: 0GitHub stars: 7
- Go Test StrategyUse while implementing Go tests when the observable failure, deterministic control, or smallest proving layer is non-obvious.Votes: 0GitHub stars: 7
- Go Verification Before CompletionUse for Go verification-only work or when deciding whether existing evidence supports a requested claim at its stated scope.Votes: 0GitHub stars: 7
- GrillingGrill: 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.Votes: 0GitHub stars: 7
- Idea RefineIdea convergence: Use when a raw or solution-led idea lacks one buildable direction. Own problem/outcome/MVP/assumptions/decision; Skip engineering-ready work.Votes: 0GitHub stars: 7
- Merge Conflict ResolutionUse when an in-progress merge, rebase, cherry-pick, or revert has conflicted hunks that require intent reconstruction, resolution, proof, and continuation.Votes: 0GitHub stars: 7
- OrchestratorLedger routing: Use only as LEDGER_ORCHESTRATOR for a ready persisted Implementation ledger. Own routing; Skip unit work.Votes: 0GitHub stars: 7
- Planning And Task BreakdownTask ledger: Use when closed decisions need ordered tasks.md. Own boundaries, proof, and reopen conditions; Skip behavior and implementation.Votes: 0GitHub stars: 7
- Spec Document DesignerSpec authoring: Use for delegated spec.md synthesis or repair from accepted inputs. Own falsifiable behavior; Skip phase and review ownership.Votes: 0GitHub stars: 7
- Spec First BrainstormingProblem frame: Use when a chosen change needs behavior delta, scope, constraints, or readiness. Own frame/next owner; Skip ideation, design, and tasks.Votes: 0GitHub stars: 7
- Thermo Nuclear Code Quality ReviewThermo-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.Votes: 0GitHub stars: 7
- Auth Access ControlPrincipal, credential, permission, tenant-isolation, and revocation depth reference reached from go-security.Votes: 0GitHub stars: 7
- Cache EngineeringCache value, key, freshness, fill, invalidation, degradation, and value depth reference reached from go-db-cache.Votes: 0GitHub stars: 7
- Concurrency ControlDurable-state interleaving, arbitration, conflict, fencing, and singleton depth reference reached from go-concurrency.Votes: 0GitHub stars: 7
- Distributed System DesignCross-component topology, state, coordination, resilience, capacity, and evolution depth reference.Votes: 0GitHub stars: 7
- Durable Background JobsDurable acceptance, identity, leases, effects, retries, schedules, and recovery depth reference.Votes: 0GitHub stars: 7
- External Api IntegrationExternal provider request identity, bounded attempts, ambiguity, callbacks, reconciliation, and migration depth reference.Votes: 0GitHub stars: 7
- Postgres PerformancePostgreSQL latency, load, locks, connections, WAL, vacuum, planner, and capacity depth reference.Votes: 0GitHub stars: 7
- Postgres Schema DesignRelational identity, cardinality, invariant, constraint, lifecycle, and migration depth reference.Votes: 0GitHub stars: 7
- Production DiagnosisProduction symptom, timeline, localization, causal falsification, recovery, and prevention depth reference.Votes: 0GitHub stars: 7
- Reliable MessagingBroker publish, consume, identity, ordering, acknowledgement, redrive, replay, and business-effect depth reference.Votes: 0GitHub stars: 7