db-normalization
DB Normalization
Overview
Use this skill to decide normalization depth intentionally, preserving integrity without ignoring workload realities.
Scope Boundaries
- Duplicate mutable data causes inconsistency bugs.
- Schema design needs explicit normalization versus denormalization trade-offs.
- Teams are preparing for domain growth and evolving query patterns.
Core Judgments
- Normal form target per entity group (3NF/BCNF and justified deviations).
- Redundancy acceptance criteria and ownership.
- Denormalization scope and refresh semantics.
- Constraint placement for anomaly prevention.
Practitioner Heuristics
- Normalize data that changes frequently or has strict consistency needs.
- Denormalize only for measured read-path benefit with explicit maintenance strategy.
- Prefer derived data pipelines over ad hoc duplicated writable columns.
- Document who repairs divergence when denormalized copies drift.
Workflow
- Identify update anomalies and redundancy hotspots.
- Model normalized alternatives and expected consistency behavior.
- Evaluate read/write trade-offs for selective denormalization.
- Define synchronization semantics for intentional redundancy.
- Document accepted anomalies and mitigation mechanisms.
Common Failure Modes
- Denormalization introduced without ownership of refresh logic.
- Over-normalization creates excessive joins for latency-critical paths.
- Hidden duplicated columns diverge silently over time.
Failure Conditions
- Stop when anomaly prevention responsibilities are undefined.
- Stop when denormalization has no measurable performance rationale.
- Escalate when required consistency cannot be maintained at chosen form.
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