Teaches your AI the reflexes of a senior backend engineer.
Workflows, disciplines, and opinionated defaults for data modeling, migrations, queries, idempotency, error handling, observability, performance, security, authentication and authorization, debugging, and testing. Covers APIs, workers, CLIs, ETL, consumers, and cron jobs as first-class citizens.
Skills 13 in the Claude listing
Auth and authorization Use when designing or modifying any auth flow, permission check, session, token issuance, multi-tenant data scope, or admin path. Boring by default Use when choosing a database, queue, language, deployment shape, auth scheme, or any infrastructure piece. Data modeling discipline Use whenever creating or changing a database schema, defining an entity, writing an ORM model, or designing a data structure that will be persisted. Debugging discipline Use when the user reports something broken, slow, flaky, or wrong in production or staging ("it's slow", "it crashes", "it doesn't work", "we're seeing 500s", "the data is wrong"). Error handling as design Use when designing or implementing any backend component, BEFORE the happy path. Idempotency and side effects Use when designing any operation that changes state, sends a message, makes a payment, calls a third party, emits an event, or writes to multiple stores. Migration safety Use whenever writing, reviewing, or running a database migration (SQL files, ORM migrations, schema changes). Observability by default Use when building or modifying any backend component (endpoint, worker, consumer, CLI, cron, daemon), BEFORE the code ships. Performance and scaling Use when building or modifying any backend component, BEFORE making perf or scaling choices. Query discipline Use when writing, reviewing, or generating any database query (raw SQL, ORM call, query builder). Security discipline Use on every diff, every new endpoint, every change to a backend component. Testing with discernment Use when writing, reviewing, or planning tests for any backend code. Think before coding Use BEFORE writing any backend code (endpoint, worker, CLI, script, consumer, cron, pipeline, daemon, webhook handler, integration).