data-structures
Data Structures
Overview
Use this skill to choose data structures with explicit tradeoffs, then justify the choice with workload assumptions and failure modes.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Inputs To Gather
- Required operations (
lookup,insert,delete,scan,range,top-k). - Read/write ratio and mutation frequency.
- Data volume now and forecast at peak.
- Latency/memory constraints and concurrency model.
Deliverables
- Candidate structure comparison with tradeoffs.
- Selected structure and rationale tied to workload.
- Risk list (memory blowup, contention, degeneration cases).
- Verification plan (microbenchmarks and edge-case tests).
Quick Decision Examples
- Frequent key lookup + updates:
hash map(+ collision strategy). - Sorted range queries:
balanced treeor ordered index. - Top-N / priority scheduling:
heap. - FIFO work pipeline:
queue(bounded if backpressure is needed). - Membership checks with low memory:
bitset/Bloom filter (with false-positive caveat).
Quality Standard
- Choice is tied to actual operation mix, not preference.
- Complexity claims include worst/average behavior assumptions.
- Memory growth and peak usage are estimated.
- Concurrency implications are explicit (lock scope, contention hotspots).
Workflow
- Define workload model and required guarantees.
- Enumerate feasible structures at the same abstraction level.
- Compare complexity, memory, and concurrency behavior.
- Select one and document rejection reasons for others.
- Define benchmark and edge-case validation plan.
Failure Conditions
- Stop when workload assumptions are missing or contradictory.
- Stop when chosen structure cannot satisfy mandatory operations.
- Escalate when memory or contention risk is unbounded at target scale.
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