distributed-systems-basics
Distributed Systems Basics
Overview
Use this skill to reason about correctness and reliability in systems where network faults and partial failures are normal.
Scope Boundaries
- Multi-service workflows require explicit consistency and ordering guarantees.
- Retry/timeout/duplicate-message behavior can change business correctness.
- Teams need to define reliability primitives before implementation or rollout.
Shared References
- Failure mode and consistency rules:
references/failure-mode-consistency-rules.md
Templates And Assets
- Distributed flow risk template:
assets/distributed-flow-risk-template.md
Inputs To Gather
- Component boundaries and communication patterns.
- Consistency and ordering requirements per workflow.
- Failure scenarios (partition, timeout, duplicate, out-of-order, stale read).
- Recovery and observability capabilities.
Deliverables
- Failure-mode map and risk ranking.
- Consistency decision record per critical flow.
- Reliability mechanism selection (retry, idempotency, backoff, timeout).
- Validation plan (fault injection and invariant checks).
Workflow
- Capture critical flows with
assets/distributed-flow-risk-template.md. - Map failure assumptions and consistency requirements per flow.
- Select reliability primitives using
references/failure-mode-consistency-rules.md. - Define observability and recovery behavior.
- Validate assumptions with targeted failure tests and invariant checks.
Quality Standard
- Critical flows have explicit consistency and ordering rules.
- Retry/timeout semantics are bounded and intentional.
- Idempotency strategy exists where at-least-once delivery is possible.
- Failure handling is observable and testable.
Failure Conditions
- Stop when consistency assumptions are implicit or contradictory.
- Stop when retries/timeouts can amplify failure unboundedly.
- Escalate when critical failure modes have no mitigation path.
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