persistence SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
persistence from ddd-ts-kit/ddd-ts-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ddd-ts-kit/ddd-ts-kit/persistence@git:20261112.9dfff55Pins git:20261112.9dfff55 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ddd-ts-kit/ddd-ts-kit
- Path
plugin/skills/persistence/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261112.9dfff55, committed Nov 12, 2026
- First version recorded
- Oct 31, 2026
- Size
- 8,637 bytes
- Repository stars
- 24
- License
- MIT
Use when adding a table, a repository, a lookup, a read model or a migration, replacing the in-memory adapter by a real one, choosing an ORM, or when persistence types leak out of infrastructure. Mapper, unit of work, optimistic concurrency, Drizzle, Knex, Prisma, TypeORM, OpenSearch.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Persistence Subject: `$ARGUMENTS` ```bash npx ddd-ts-kit generate repository <ctx> <Aggregate> [--tenant-scoped] [--personal <column>,... [--subject <column>] [--erasure pseudonymise|row]] --json ``` writes the port (an abstract class extending the kernel `Repository<Aggregate>` in `domain/repositories/`), the adapter of the project's ORM with its mapper and table in `infrastructure/persistence/`, the fake, and one `repositoryContract` spec that both must pass. `generate command --aggregate` creates it when missing. Fill the `todos` places: the lookups of the port, the columns, the mapper. Read model of a projection: `generate read-model <ctx> <Name> --field <name>:<type>...` writes port (over `ReadModelStore<Row>`), table, store adapter, fake and `readModelContract` spec, not `port` then `adapter`. ## Rules, whatever the technology - **One repository per aggregate root**, whole-aggregate load and save. Add only the lookups a use case needs, named in the ubiquitous language; a screen reads through a read port. - **Rows stay inside.** The mapper translates row to aggregate (`rehydrate`) and back; it is the one place for a type assertion. No ORM type crosses the port. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_hebmjzacvm5tkd5o/dd521726f896bf53f3748beb95700dd9ea73b49101ed0b49c1cd0207bbea344b.json
Then /plugin install persistence@markdownregistry-hebmjzacvm5tkd5o in Claude Code. It installs git:20261112.9dfff55, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add ddd-ts-kit/ddd-ts-kit/persistence@sha256:dd521726f896bf53The line at the top of this page pins the label git:20261112.9dfff55, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_hebmjzacvm5tkd5o)
0 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in ddd-ts-kit/ddd-ts-kit/persistence since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of persistence from somewhere else? Ask it: where did my persistence come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Oct 31, 2026 and Nov 12, 2026, about one every 3 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261112.9dfff55 latest | 2026-11-12 | 9dfff55 | 8,637 B | A | view · diff |
| git:20261111.9f19e3f | 2026-11-11 | 9f19e3f | 8,613 B | A | view · diff |
| git:20261111.f313e7b | 2026-11-11 | f313e7b | 8,572 B | A | view · diff |
| git:20261101.5c9e371 | 2026-11-01 | 5c9e371 | 8,549 B | A | view · diff |
| git:20261031.8ab7ca4 | 2026-10-31 | 8ab7ca4 | 8,507 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/persistence/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8637 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ddd-ts-kit/ddd-ts-kit · 24 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hebmjzacvm5tkd5o GET https://markdownregistry.com/api/v1/resolve?ref=ddd-ts-kit/ddd-ts-kit/persistence GET https://markdownregistry.com/api/v1/blob/dd521726f896bf53f3748beb95700dd9ea73b49101ed0b49c1cd0207bbea344b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from ddd-ts-kit/ddd-ts-kit
Every file in ddd-ts-kit/ddd-ts-kit