Persistence Design

Use for database and persistence design, data ownership, transaction boundaries, repositories, CQRS read models, query performance, optimistic concurrency, caching, projections, schema migrations, partitioning, and multi-tenancy.

9 stars 2 forksDatabases Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add eralmansouri/skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add eralmansouri/skills --skill persistence-design
Manual install
git clone --depth 1 https://github.com/eralmansouri/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/persistence-design ~/.claude/skills/persistence-design

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Persistence Design

Start with business capability, ownership, and required consistency. Database
technology, repositories, schemas, caches, and messages follow those decisions.

## Decision Workflow

1. Classify the operation as query, command, simple CRUD, or a business workflow.
2. For a command, identify the data required to decide and whether it can change concurrently.
3. Choose the smallest consistency boundary that can enforce the rule reliably.
4. Design the read path independently around the caller's required shape.
5. Define acceptable staleness and whether read-your-own-write is required.
6. Estimate production growth, result bounds, lifecycle, and partitioning needs.
7. Choose tenant isolation based on the resource and risk being isolated, then enforce tenant context through every data path.
8. Plan backward-compatible schema and application evolution.

## Consistency Choices

| Need | Mechanism |
| --- | --- |
| Atomic local decision and mutation | Database transaction with required isolation |
| Aggregate invariant | Load, decide, and save the aggregate as a unit |
| Infrequent write conflict | Optimistic version or ETag |
| Short serialized database operation | Pessimistic row lock |
| Finite resource in a long workflow | Reserve, confirm, and expire |
| State plus outgoing message | Transactional outbox |
| Multiple independent owners | Explicit eventual workflow or redesigned ownership |
Read the full skill on GitHub

Details

Skill name
persistence-design
Path
skills/persistence-design/SKILL.md
Repo updated
15 October 2026

FAQ

What does the Persistence Design skill do?

Use for database and persistence design, data ownership, transaction boundaries, repositories, CQRS read models, query performance, optimistic concurrency, caching, projections, schema migrations, partitioning, and multi-tenancy.

How do I install the Persistence Design skill?

Claude Code plugin: /plugin marketplace add eralmansouri/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Persistence Design popular?

It lives in eralmansouri/skills, which has 9 GitHub stars and 2 forks.

Related skills

Codebase Design

9

eralmansouri/skills

Use for code-level module design, deep modules, interfaces, seams, adapters, testability, refactoring shallow modules, and finding architecture improvements in an existing codebase.

Software Development

Design Review

9

eralmansouri/skills

Design review of a codebase area, branch, or PR. Maps its bounded contexts, vertical slices, and modules, then judges where rules live and whether flexibility sits where change actually happens. Use when the user asks for a design or architecture review, or when a review should judge structure rather than bugs or style.

Git & Code Review

Domain Driven Design

9

eralmansouri/skills

Use for domain-driven design, domain modeling, ubiquitous language, bounded contexts, aggregates, invariants, entities, value objects, domain services, domain events, and deciding whether a rich domain model is warranted.

AI, LLMs & Agents

SQL Expert

6

techgangboss/agentstore

Use this skill when the user needs help writing SQL queries, optimizing existing queries, understanding execution plans, designing schemas, or debugging database issues. Trigger on phrases like "write a query", "optimize this SQL", "explain this query", "design a schema", "database help", "why is this query slow", etc.

DatabasesIn 1 list

Seekdb

9

oceanbase/oceanbase-skills

Overview skill for OceanBase SeekDB. Routes to specialized sub-skills covering the full SeekDB lifecycle — install/deploy on a target machine, build from source, look up documentation, use the seekdb-cli for SQL/schema/vector ops, import CSV/Excel data, and query/export results. Use as a starting point when the user mentions seekdb, pyseekdb, "install seekdb", "build seekdb", "seekdb docs", "seekdb-cli", "import to seekdb", "query seekdb", or wants a lightweight standalone OceanBase-compatible database.

Databases

Common

9

mark64oswald/healthsim-workspace

Cross-product infrastructure for HealthSim — persistence (cohort save/load), identity correlation (SSN-based cross-product linking), and DuckDB database operations. Use when saving/loading cohorts, linking entities across products, or querying the database directly.

Databases

Browse the most popular Claude skills, all databases skills, or write your own with the skills generator.