atuljha23

Safe schema-migration patterns for systems under live traffic, including expand/contract, backfill, double-write, shadow-read, and online DDL. These patterns are used when authoring, reviewing, or sequencing a migration that cannot take a maintenance window.

WCAG 2.2 AA quick reference — semantics, keyboard, names, states, contrast, motion, errors. Use when building or reviewing UI components.

Apply the Write/Select/Compress/Isolate framework to manage the context window. Use when the task is long, the transcript is bloated, the model is drifting, or before /holocron:handoff.

Hypothesis-driven debugging involves reproducing, hypothesizing, probing, locating, fixing, and guarding. Use this method when something is broken and the cause is unknown.

A quick reference for performance, covering Core Web Vitals, bundle size, rendering, database queries, and caching. Useful during implementation or review when performance is a key concern.

Staff-level PR review rubric: correctness, contract, clarity, tests, and blast radius. Use when reviewing code (yours or others') before merge.

OWASP-style quick reference — authn/authz, injection, secrets, sessions, crypto, dependencies. Use during code review and before committing security-sensitive changes.

Reference for writing tests that actually protect against regressions, focusing on deep assertions over spies, table-driven tests, fixture hygiene, and AAA structure. Use when writing, reviewing, or refactoring tests.

Good observability involves structured logs, trace spans, metrics, correlation IDs, and instrumentation rules to derive answers from logs. It's useful for adding features, reviewing services, or debugging production issues.

A rubric for keeping Claude Code sessions cheap without losing quality, covering model tiering, cache hygiene, Read discipline, MCP pruning, and subagent isolation. Apply it when costs seem off, before setting a budget, or when onboarding a new teammate.

REST and GraphQL API design conventions, covering resource modeling, pagination, error handling, versioning, and idempotency. Apply these when adding, changing, or reviewing API endpoints.