db-transaction-design
DB Transaction Design
Overview
Use this skill to design transaction behavior that protects invariants while avoiding avoidable contention and deadlocks.
Scope Boundaries
- Concurrent workflows must preserve business invariants.
- Anomalies (lost update, write skew, phantom) are possible.
- Lock contention or deadlocks are degrading reliability.
Core Judgments
- Transaction boundary: what must be atomic versus eventually consistent.
- Isolation level per workflow and anomaly tolerance.
- Locking strategy: optimistic, pessimistic, or hybrid.
- Retry/idempotency behavior under deadlock/timeouts.
Practitioner Heuristics
- Keep transactions as short as possible while preserving invariants.
- Choose isolation by anomaly risk, not blanket highest level.
- Model retries as business behavior with idempotent operations.
- External network calls inside DB transactions are a major anti-pattern.
Workflow
- Identify critical invariants and concurrent access patterns.
- Define transaction boundaries per use case.
- Map anomaly risks and select isolation/locking strategy.
- Design timeout, retry, and deadlock-handling behavior.
- Evaluate contention hotspots and redesign access ordering if needed.
- Record assumptions and triggers for revisiting transaction policy.
Common Failure Modes
- Broad transaction scopes serialize unrelated work.
- Retry logic replays side effects without idempotency guard.
- Isolation is changed to fix symptoms without invariant analysis.
Failure Conditions
- Stop when invariants cannot be mapped to transaction boundaries.
- Stop when retry behavior can duplicate irreversible side effects.
- Escalate when contention cannot be controlled without workflow redesign.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9