db-logical-design
DB Logical Design
Overview
Use this skill to define schema semantics that preserve integrity and support maintainable application behavior.
Scope Boundaries
- New domain models must be translated into relational schema.
- Existing schema suffers from integrity drift or unclear constraints.
- Teams need consistent key and relationship semantics.
Core Judgments
- Primary and alternate key strategy.
- Nullability and optionality semantics.
- Referential integrity rules and cascade behavior.
- Audit and lifecycle columns (created/updated/deleted/effective time).
Practitioner Heuristics
- Model constraints in the database when they are universal invariants.
- Use explicit unique constraints to encode business identity rules.
- Avoid ambiguous nullable fields that represent multiple meanings.
- For dynamic-language apps, define explicit typed schema mappings to avoid broad
objectpayloads and repetitive casts at repository boundaries.
Workflow
- Map conceptual entities to relational structures.
- Define keys, uniqueness, and relationship cardinality rules.
- Specify integrity constraints and lifecycle semantics.
- Validate design against expected write/read workflows.
- Identify migration implications and compatibility constraints.
- Document deferred trade-offs and boundary assumptions.
Common Failure Modes
- Business identity handled only in application code.
- Soft-delete semantics conflict with uniqueness and reporting.
- Overloaded JSON columns hide core relational structure.
Failure Conditions
- Stop when key strategy cannot guarantee entity identity.
- Stop when critical invariants rely on informal conventions.
- Escalate when logical model conflicts with required consistency semantics.
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