sqlalchemy-orm-patterns
Sqlalchemy Orm Patterns
Overview
Use this skill to design SQLAlchemy usage that remains correct, efficient, and maintainable under production load.
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.
Shared References
- ORM loading and session rules:
references/orm-loading-and-session-rules.md
Templates And Assets
- ORM modeling template:
assets/sqlalchemy-modeling-template.py
- Session/transaction checklist:
assets/sqlalchemy-session-transaction-checklist.md
Inputs To Gather
- Domain model and relationship constraints.
- Transaction consistency requirements.
- Query access patterns and performance constraints.
- Session lifecycle boundaries.
Deliverables
- ORM model and relationship design.
- Session and transaction boundary policy.
- Query loading strategy with hotspot validation.
Workflow
- Draft model structure using
assets/sqlalchemy-modeling-template.py. - Define session/transaction boundaries.
- Apply loading strategy rules from
references/orm-loading-and-session-rules.md. - Validate SQL behavior for hot queries.
- Finalize with
assets/sqlalchemy-session-transaction-checklist.md.
Quality Standard
- Session ownership is explicit and leak-free.
- Transaction boundaries preserve business atomicity.
- Query strategy avoids N+1/overfetch patterns.
- ORM abstractions remain transparent for critical SQL paths.
Failure Conditions
- Stop when session ownership is ambiguous across layers.
- Stop when ORM hides critical SQL behavior on hot paths.
- Escalate when transaction guarantees cannot be met safely.
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