💾 Core Philosophy: Data is the most valuable asset; protect its integrity and optimize its retrieval.
When to use
Use this skill when defining SQLite/PostgreSQL schemas, ORM models, Redis key schemas, local app storage (SwiftData, CoreData, IndexedDB), sync models, cache-aside strategies, and transaction logic.
When not to use
Do not use this skill for layout styling, UI interactions, API transport conventions (HTTP details), or provisioning.
Trigger cues
- Key terms: database, cache, transactional, ACID, BASE, PostgreSQL, SQLite, SwiftData, CoreData, Redis, IndexedDB, transaction, migration, query, indexing, TTL, invalidation.
- Designing schema models, implementing cache layers, writing complex queries, or offline sync logic.
Routing boundary
- Primary for database layout, storage performance, cache eviction, transactions, and data structures.
- Secondary to
system-architecture-rules for domain boundaries.
Inputs required
- Target storage engines (PostgreSQL, SwiftData, Redis, etc.)
- Strict read/write ratios and low latency limits
- Source of truth:
references/source.md
Instructions
- Detect Stack: Inspect the workspace files to identify the project's existing technology stack (e.g., Prisma, TypeORM, SQLAlchemy, CoreData, PostgreSQL, SQLite).
- Do Not Migrate: Never propose or force a technology stack change. Apply the principles in this skill using the project's current tooling.
- Read references/source.md to understand storage systems and cache invalidation.
- Outline database schemas and queries using the project's existing database tools and libraries.
- Design caching strategies including cache eviction policies (LRU) and stampede mitigation.
- Establish transaction boundaries to guarantee ACID behavior where required.
- In mobile apps (iOS), enforce separate background concurrency context rules for CoreData/SwiftData.
Output format
- Primary decision/output: Database schema/migrations, indexing strategy, and caching topology.
- Summary: One-paragraph overview of persistence and cache strategy.
- Actions: Validation checklist for performance, concurrency safety, and cache consistency.
1---2name: data-persistence-caching3description: Trigger: database schema, indexing, cache asidePattern, Redis caching, ORM models, Drizzle schema. Scope: Database query tuning, indexing, and data cache designs. Boundary: Excludes user identity validation.4---56# 💾 Core Philosophy: Data is the most valuable asset; protect its integrity and optimize its retrieval.78## When to use910Use this skill when defining SQLite/PostgreSQL schemas, ORM models, Redis key schemas, local app storage (SwiftData, CoreData, IndexedDB), sync models, cache-aside strategies, and transaction logic.1112## When not to use1314Do not use this skill for layout styling, UI interactions, API transport conventions (HTTP details), or provisioning.1516## Trigger cues1718- Key terms: database, cache, transactional, ACID, BASE, PostgreSQL, SQLite, SwiftData, CoreData, Redis, IndexedDB, transaction, migration, query, indexing, TTL, invalidation.19- Designing schema models, implementing cache layers, writing complex queries, or offline sync logic.2021## Routing boundary2223- Primary for database layout, storage performance, cache eviction, transactions, and data structures.24- Secondary to `system-architecture-rules` for domain boundaries.2526## Inputs required2728- Target storage engines (PostgreSQL, SwiftData, Redis, etc.)29- Strict read/write ratios and low latency limits30- Source of truth: `references/source.md`3132## Instructions33341. **Detect Stack**: Inspect the workspace files to identify the project's existing technology stack (e.g., Prisma, TypeORM, SQLAlchemy, CoreData, PostgreSQL, SQLite).352. **Do Not Migrate**: Never propose or force a technology stack change. Apply the principles in this skill using the project's current tooling.363. Read [references/source.md](references/source.md) to understand storage systems and cache invalidation.374. Outline database schemas and queries using the project's existing database tools and libraries.385. Design caching strategies including cache eviction policies (LRU) and stampede mitigation.396. Establish transaction boundaries to guarantee ACID behavior where required.407. In mobile apps (iOS), enforce separate background concurrency context rules for CoreData/SwiftData.4142## Output format4344- Primary decision/output: Database schema/migrations, indexing strategy, and caching topology.45- Summary: One-paragraph overview of persistence and cache strategy.46- Actions: Validation checklist for performance, concurrency safety, and cache consistency.
coreyone