alti3/advanced-alchemy-types
plugins/advanced-alchemy/skills/advanced-alchemy-types/SKILL.md
Apply Advanced Alchemy custom SQLAlchemy types such as `DateTimeUTC`, encrypted fields, `GUID`, `JsonB`, password hashing, and stored file objects with backend-aware behavior and migration compatibility. Use when modeling non-trivial persistence concerns, securing sensitive columns, or choosing database-portable data types. Do not use for general model design that does not require custom column behavior.
$ install --global
skillsauthnpx skillsauth add alti3/litestar-skills advanced-alchemy-typesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 3:21 PM1.7s1 file scanned
SKILL.md
- name:
- advanced-alchemy-types
- description:
- Apply Advanced Alchemy custom SQLAlchemy types such as `DateTimeUTC`, encrypted fields, `GUID`, `JsonB`, password hashing, and stored file objects with backend-aware behavior and migration compatibility. Use when modeling non-trivial persistence concerns, securing sensitive columns, or choosing database-portable data types. Do not use for general model design that does not require custom column behavior.
Types
Execution Workflow
- Choose the column type based on storage semantics, not convenience.
- Use
DateTimeUTCfor timezone-aware timestamps that must normalize to UTC. - Use
EncryptedStringorEncryptedTextonly after choosing the encryption backend and key source. - Use
GUID,JsonB,PasswordHash, andStoredObjectwhere the database contract truly requires them. - Check migration and dialect behavior before committing to a custom type in a widely used model.
Implementation Rules
- Require timezone-aware input for UTC datetime fields.
- Never hardcode real encryption keys in model definitions.
- Keep type constructor arguments hashable and cache-safe when custom decorators participate in SQLAlchemy statement caching.
- Treat file-object and password-hash columns as lifecycle-bearing fields, not plain strings.
Example Pattern
from advanced_alchemy.types import DateTimeUTC, EncryptedString, GUID, JsonB
class User(DefaultBase):
__tablename__ = "users"
id: Mapped[UUID] = mapped_column(GUID, primary_key=True)
created_at: Mapped[datetime] = mapped_column(DateTimeUTC)
secret: Mapped[str] = mapped_column(EncryptedString(key="secret-key"))
preferences: Mapped[dict] = mapped_column(JsonB)
Validation Checklist
- Confirm the selected type behaves correctly on the target database dialect.
- Confirm encrypted and password-hash fields use the intended backend and key management path.
- Confirm stored datetimes are timezone-aware and normalized to UTC.
- Confirm migrations can render and replay the custom types cleanly.
Cross-Skill Handoffs
- Use
advanced-alchemy-modelingto place these types on the right models. - Use
advanced-alchemy-cachingwhen custom type configuration affects SQLAlchemy cacheability. - Use
advanced-alchemy-litestarif file-object or DTO behavior must line up with Litestar transport contracts.
Advanced Alchemy References
- https://advanced-alchemy.litestar.dev/latest/usage/types.html
- https://docs.advanced-alchemy.litestar.dev/latest/reference/types.html
Related Skills
alti3/litestar-websockets
development
VerifiedTrustedCommunity
Build Litestar WebSocket endpoints with low-level websocket handlers, websocket listeners, websocket streams, dependency injection, custom websocket classes, transport-mode control, and graceful connection lifecycle handling. Use when implementing bidirectional real-time communication, reactive websocket message handling, or proactive server push over WebSockets. Do not use for server-side pub/sub fanout that is better expressed with channels alone.
5SKILL.mdUpdated Apr 3, 2026
alti3/litestar-testing
tools
VerifiedTrustedCommunity
Test Litestar applications with TestClient, AsyncTestClient, create_test_client, websocket test helpers, dependency overrides, mocked dependencies, lifecycle-aware fixtures, and deterministic success and failure assertions. Use when adding or fixing Litestar test coverage, including exception contracts, override precedence, websocket behavior, event-bus side effects, or live-server-only response patterns. Do not use as a substitute for production observability or runtime debugging strategy.
5SKILL.mdUpdated Apr 3, 2026
alti3/litestar-templating
development
VerifiedTrustedCommunity
Configure Litestar templating with `TemplateConfig`, Jinja/Mako/MiniJinja engines, file-or-string `Template` responses, request and CSRF-aware context, template callables, and custom engine integration. Use when implementing or fixing server-rendered HTML in Litestar. Do not use for static asset serving or pure JSON API endpoints.
5SKILL.mdUpdated Apr 3, 2026
alti3/litestar-stores
development
VerifiedTrustedCommunity
Configure Litestar stores and the store registry for caching, server-side sessions, rate limiting, and other key-value state with explicit backend selection, bytes-safe data handling, TTL and renewal policy, namespacing, registry wiring, and lifecycle cleanup. Use when a Litestar app depends on `MemoryStore`, `FileStore`, `RedisStore`, `ValkeyStore`, or `StoreRegistry`. Do not use for relational persistence, domain repositories, or response-caching policy details that belong in database or caching-focused skills.
5SKILL.mdUpdated Apr 3, 2026