db-index-strategy
DB Index Strategy
Overview
Use this skill to choose indexes that improve real workloads while controlling write and storage costs.
Scope Boundaries
- Query latency hotspots are driven by access-path inefficiency.
- New query patterns or sort requirements are introduced.
- Existing indexes show redundancy, bloat, or unstable plans.
Core Judgments
- Query-path priority by business impact and frequency.
- Composite key order by filter selectivity and sort usage.
- Covering/partial/functional index suitability by engine capability.
- Write amplification and maintenance cost tolerance.
Practitioner Heuristics
- Indexes should be justified by concrete query families, not single ad hoc queries.
- Composite index order follows filter-first then sort semantics.
- Prefer fewer high-value indexes over broad index proliferation.
- Consider plan stability across parameter distribution, not one explain sample.
Workflow
- Rank critical queries by frequency, latency impact, and SLA relevance.
- Inspect current plans and identify scans, misestimation, and sort spills.
- Propose candidate indexes with expected plan effects.
- Evaluate write/maintenance/storage impact for each candidate.
- Decide new, modified, and removable indexes as one portfolio.
- Record assumptions that require re-evaluation as data distribution changes.
Common Failure Modes
- Indexes tuned for one tenant or parameter pattern only.
- Redundant indexes remain after query evolution.
- Index design ignores heavy write paths and causes throughput collapse.
Failure Conditions
- Stop when index choices are not tied to prioritized workload.
- Stop when write amplification risk is unbounded.
- Escalate when plan stability remains poor after viable candidates.
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