Relational databases (Postgres, MySQL) — ACID, SQL, joins, isolation levels, MVCC vs locking, indexes, JSONB, HA topologies. Reach for this when you see lost updates, phantom reads, double-billed customers, "duplicate charges" after a retry, deadlocks under load, p99 query spikes from missing indexes, replication lag breaking read-your-writes, foreign-key cascading failures, or someone reaching for Mongo/DynamoDB to avoid "writing SQL" when they actually need transactions.
EnglishTest-Driven Development and Behavior-Driven Development as design tools, not just verification. Use when shipping changes that "worked locally" but break in CI, when refactors are terrifying because no one trusts the test suite, when bug fixes keep regressing, when stack traces point at code with no covering test, when product and engineering disagree on what "done" means, when mocks have grown so deep that tests pass while production crashes, or when coverage is 90% but defects per release keep climbing. Covers red-green-refactor, classicist (Detroit) vs mockist (London) schools, Given/When/Then specs, when TDD pays back vs when it's overhead, and the most common ways teams botch it.
English
AGENT SKILLS ATLASIncludes Relational and other workflows.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLISupported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Relational
Relational databases (Postgres, MySQL) — ACID, SQL, joins, isolation levels, MVCC vs locking, indexes, JSONB, HA topologies. Reach for this when you see lost updates, phantom reads, double-billed customers, "duplicate charges" after a retry, deadlocks under load, p99 query spikes from missing indexes, replication lag breaking read-your-writes, foreign-key cascading failures, or someone reaching for Mongo/DynamoDB to avoid "writing SQL" when they actually need transactions.
TDD Bdd
Test-Driven Development and Behavior-Driven Development as design tools, not just verification. Use when shipping changes that "worked locally" but break in CI, when refactors are terrifying because no one trusts the test suite, when bug fixes keep regressing, when stack traces point at code with no covering test, when product and engineering disagree on what "done" means, when mocks have grown so deep that tests pass while production crashes, or when coverage is 90% but defects per release keep climbing. Covers red-green-refactor, classicist (Detroit) vs mockist (London) schools, Given/When/Then specs, when TDD pays back vs when it's overhead, and the most common ways teams botch it.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Relational skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- License details are not provided in these listings. Check the author’s terms before using the skills.