data-systems-coding-lens
Installation
SKILL.md
Data Systems Coding Lens
Catch data failure modes before they reach production. Apply it when a change touches persistent data, background work, or production operational risk; UI copy, styling, and throwaway scripts do not need it.
Two leitwörter anchor every pass. Say them by name as you work:
- Source of truth: the one place that durably owns each fact. Caches, indexes, and read models are derived and must be rebuildable from it.
- Idempotent: a retried or replayed write produces the same result the second time: no duplicate money, emails, jobs, or records.
First pass: the state boundary
- What data is created, updated, deleted, cached, derived, or emitted, and what is its source of truth?
- Which paths are asynchronous, retried, replayed, or user-visible?
- Which invariant makes the feature wrong if it breaks, and where does the code enforce it?
- Which failure would be silent, expensive, or hard to repair?
On a small change, fold this into the work. When shared data contracts or production records are involved, write the answers down before editing.