Playbook for investigating a slow read-model query in the standard-reader feed (home / latest / discover / tag / search). Covers finding the slow span in Honeycomb, reproducing against prod-scale Neon data, running and reading EXPLAIN ANALYZE, the known regression patterns (correlated cutoff subquery, inlined aggregation across a join), the fix templates, and how to verify. Use when a feed/home/latest query "feels slow", a perf budget is blown, or a Honeycomb p95/p99 tail needs explaining. Pairs with the gated EXPLAIN benchmark at `src/server/reader/queries.explain.test.ts` (`pnpm perf:explain`).
Implement internationalization with Lingui in React and JavaScript applications. Use when adding i18n, translating UI, working with Trans/useLingui/Plural, extracting messages, compiling catalogs, or when the user mentions Lingui, internationalization, i18n, translations, locales, message extraction, ICU MessageFormat, or working with .po files.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Conduct rigorous, security-focused code reviews with zero tolerance for mediocrity.
Inspect the Standard Reader Railway deployment using the Railway CLI — view project status, list deployments, stream logs, and triage failures across the web, tap, ingest, and recompute-cron services. Use when the user asks to "check Railway", "inspect the deployment", "what deployed", "check logs", "is the deploy healthy", "why did the deploy fail", "debug Railway", "railway status", "railway logs", or mentions Railway, a deploy, a service healthcheck, or a deployment failure/crash.
Guides AT Protocol record attestations per badge.blue in Rust, TypeScript, or Go: inline ECDSA signatures, remote strongRef proof records, CID-first signing, low-S normalization, and the two-CID model. Use when the user mentions sign an atproto record, inline attestation, remote attestation, badge.blue, $sig metadata, content CID for signing, proof record, low-S signature, ECDSA r‖s, replay protection, atproto-attestation, @noble/curves, k256, or p256.
Guides AT Protocol / DASL CID work in Rust, TypeScript, or Go: parsing, constructing, validating, and debugging CIDs. Use when the user mentions CID mismatch, tag 42 in DAG-CBOR, base32lower, bafyrei / bafkrei, $link format, DASL CID profile, BLAKE3 / BDASL, or libraries like multiformats, @ipld/dag-cbor, atproto-dasl, github.com/ipfs/go-cid, or go-multihash.
Guides AT Protocol identity resolution in Rust, TypeScript, or Go: handles, DIDs, DNS TXT / well-known resolution, DID document validation, bidi verification, and handle.invalid. Use when the user mentions resolve a handle, _atproto DNS, .well-known/atproto-did, DID document, atproto_pds, alsoKnownAs, handle.invalid, @atproto/identity, @atproto/syntax, IdResolver, or indigo/atproto/identity.