← LeaderboardThe Skill Leaderboard

designing-data-intensive-applications

Apply Martin Kleppmann-inspired data-system rules when designing reliability, scalability, consistency, replication, transactions, streams, or schema evolution.

Published by ciembor ↗ciembor/agent-rules-books

Try your first task

designing-data-intensive-applications

Start a fresh conversation. Replace the highlighted placeholders.

Use designing-data-intensive-applications to produce a data-system design recommendation for [system or change], explicitly defining the source of truth, consistency and durability semantics, retry/replay behavior, and schema-evolution approach using [workload and invariants].

Required inputs

  • [system or change]
  • [workload and invariants]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: designing-data-intensive-applicationsdescription: Apply Martin Kleppmann-inspired data-system rules when designing reliability, scalability, consistency, replication, transactions, streams, or schema evolution.license: MIT

Designing Data-Intensive Applications Skill

Use this skill when a task involves data ownership, consistency semantics, event flows, replication, partitioning, transactions, streams, batch processing, fault tolerance, or schema evolution.

Before making design or code decisions, read and apply designing-data-intensive-applications.mini.md. Use designing-data-intensive-applications.md only as a deeper reference when the mini rules are not enough for the current data-system tradeoff.