Turn the spec's tables into D1 migrations with tests.
234 stars
0 votes
0 copies
0 views
Added September 29, 2026
ai-agentsrustsqlgit
Security analysis
A100/100
Scanned September 29, 2026
$npx -y skills add receptron/mulmoterminal --skill data --agent claude-code
Installs into .claude/skills of the current project.
Are you the author of Data?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/receptron-data-mulmoterminal)
---
name: blueprint-cloudflare-data
description: "Turn the spec's tables into D1 migrations with tests."
---
# Data
1. One migration file per change in `migrations/` (`0001_….sql`, …), applied by wrangler. Primary keys, NOT NULL and
UNIQUE as the spec's table says; foreign keys as the spec's relations say.
2. A small data-access module per table with bound statements only (`env.DB.prepare("… ?").bind(value)`).
3. `test/data.test.ts`: in the Workers runtime, every table can be written and read back, and every NOT NULL and UNIQUE
is refused when broken.
Done when the check passes: `yarn build` and `yarn test` succeed and `test/` has the data tests.
## Always
- Read `.blueprint/spec.md` first. It is the agreed specification; do not widen it.
- When you need a decision, ask it through the blueprint question tool and stop. Do not guess.
- Do not run `git init`: a new repository loses the folder's trust and the next unattended step stops at Claude
Code's trust prompt. The user adds git themselves after the build if they want it.
- Say you are done by stopping; the executor runs the check. Do not claim success yourself.
