Book Ddia Data Design

Guides data-intensive design checks for consistency, reliability, schema evolution, and data flow risks. In strict tasks, mandatory before design stabilizes or implementation begins when changing persisted/shared data, schemas, migrations, shared/persistent/cross-request/cross-process caches, async or cross-service flows, data ownership, or recovery; in default/lite tasks, use on demand when those risks or explicit delivery requirements are present.

559 stars 13 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add KunoLu/640-skills --skill book-ddia-data-design
Manual install
git clone --depth 1 https://github.com/KunoLu/640-skills.git /tmp/640-skills
mkdir -p ~/.claude/skills
cp -r /tmp/640-skills/sbtd-workflow-onboard/templates/skills/book-ddia-data-design ~/.claude/skills/book-ddia-data-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

# Book DDIA Data Design

Use this Skill when a change can fail because of data semantics, distributed behavior, or operational reality rather than ordinary code structure.

It is derived from the `mini` rule style of `agent-rules-books` and should complement project architecture, task design, source/LSP/contract impact analysis, tests, and production validation.

## Strict Development Gate

In a strict task, run this Skill before design artifacts become stable or implementation begins when the task changes any of the following:

- Persisted or shared data, databases, schemas, or migrations.
- shared, persistent, cross-request, or cross-process caches; queues, events, streams, jobs, ETL, or analytics pipelines.
- Cross-service data flow or API ownership.
- Data ownership, source of truth, transaction boundaries, or read / write paths.
- Backfill, replay, rollback, or recovery behavior.

Emit a separate visible review:

```text
DDIA Data Design Review
Status: confirmed | needs-design-change | blocked
Data owner and source of truth: ...
Write / read / async / failure paths: ...
Consistency model: ...
Idempotency / ordering / retry / deduplication: ...
Schema / migration / backfill / rollback / replay: ...
Observability and repair: ...
Required tests: ...
```

- `confirmed`: the data design and failure / recovery behavior are explicit enough to implement safely.
- `needs-design-change`: update the design or task artifacts, then rerun this Skill before implementation.
Read the full skill on GitHub

Details

Skill name
book-ddia-data-design
Path
sbtd-workflow-onboard/templates/skills/book-ddia-data-design/SKILL.md
License
Apache-2.0
Repo updated
13 November 2026

FAQ

What does the Book Ddia Data Design skill do?

Guides data-intensive design checks for consistency, reliability, schema evolution, and data flow risks. In strict tasks, mandatory before design stabilizes or implementation begins when changing persisted/shared data, schemas, migrations, shared/persistent/cross-request/cross-process caches, async or cross-service flows, data ownership, or recovery; in default/lite tasks, use on demand when those risks or explicit delivery requirements are present.

How do I install the Book Ddia Data Design skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add KunoLu/640-skills --skill book-ddia-data-design. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Book Ddia Data Design popular?

It lives in KunoLu/640-skills, which has 559 GitHub stars and 13 forks.

Related skills

Handoff

559

KunoLu/640-skills

Compact the current conversation into a handoff document for another agent to pick up.

AI, LLMs & AgentsIn 2 lists13

Codebase Design

559

KunoLu/640-skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Software DevelopmentIn 2 lists13

Diagnosing Bugs

559

KunoLu/640-skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

Software DevelopmentIn 2 lists13

Book Legacy Change Safety

559

KunoLu/640-skills

Guides safe changes to legacy or weakly tested code by characterizing behavior before editing. In strict tasks, mandatory before the first behavior-changing edit for existing-behavior bug fixes or existing code with unclear behavior, low coverage, hidden dependencies, or high regression risk; in default/lite tasks, use on demand when those risks or explicit delivery requirements are present.

Productivity & Notes13

Zendesk Automation

581

claude-office-skills/skills

Automate customer support workflows with Zendesk ticket management, routing, and analytics

Productivity & Notes105

Ponytail

559

KunoLu/640-skills

Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.

Productivity & Notes13

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.