epicenter

Diagnose hard bugs and performance regressions with a reproduce-to-regression-test feedback loop. Use when the user reports broken, throwing, failing, or slow behavior or explicitly asks to diagnose or debug it.

Work out an unsettled idea together through concrete attempts to articulate and express it. Use when the user asks for a dialectic, wants to explore what a skill or workflow should do, is finding a direction for writing, wants to judge a proposed change, wants to think through an uncertain model or decision, or needs help articulating a thought they cannot quite express. Do not use for routine execution of a settled request, a standalone explanation of settled material, or a code review.

In-code documentation, folder READMEs, code comments. Use when: "document this", "add JSDoc", "write a README", "explain this code", or writing README.md/JSDoc.

Apply Drizzle ORM patterns for schemas, migrations, queries, branded types, and Postgres or D1 boundaries. Use when working with Drizzle or typed SQL, not raw `bun:sqlite` or non-Drizzle engines.

Trigger a dialectic about reader agency in Braden's essays, narratives, profiles, analytical papers, and humor writing. Use when applying English 120 ideas such as show-not-tell, subtlety, concrete detail, tension, or not telling the reader what to think. Do not use for generic proofreading, citation research, or non-writing questions.

Apply Wellcrafted Result patterns to fallible operations and preserve failures at boundaries. Use when replacing try/catch, adding trySync or tryAsync, choosing fallback or propagation, or mapping errors.

Factory function patterns to compose clients and services. Use when wrapping resources with domain methods or refactoring mixed client/service/method options.

Apply Epicenter Git conventions for commits, branches, and history. Use when staging files, writing or splitting commits, creating branches, or inspecting history, not for pull request text or merge guidance.

GitHub issue comment guidelines for community interaction. Use when: "respond to this issue", "reply to this bug report", "close this issue", or any GitHub discussion.

Write and review developer documentation in Google Developer Documentation Style. Use when drafting guides, API reference, READMEs, procedures, or release notes, not UI strings, commit messages, PR bodies, or code comments.

Reconsider a system from a clean-slate target and identify legacy or compatibility paths to delete. Use when evaluating a greenfield redesign, clean break, no users, or removal of old behavior.

Interview the user relentlessly about a plan to reach shared understanding, resolving each branch of the decision tree. Use when stress-testing a plan or "grill me".

Stress-test a plan against the project’s domain model and update its documentation as terminology settles. Use when a plan needs to be challenged against existing context or ADRs.

Draft a self-contained prompt for a fresh ChatGPT, Claude Code, or other agent session. Use when the user asks for a handoff, continuation prompt, or something to copy and paste into another session. Do not use for a progress summary or for asking another agent to review or implement work within the active session.

Hono patterns for TypeScript API routes, middleware, request and response typing, streaming, WebSockets, and Cloudflare Workers deployment. Use when users mention Hono, honojs, Cloudflare Worker handlers, Hono middleware, or Hono route typing.

Scan a codebase for architectural deepening opportunities and present them in a visual HTML report. Use when the user asks for an architecture review or wants candidates to grill before choosing a refactor.

wellcrafted/logger for library diagnostics: 5 levels, typed errors, injected sinks, and host-owned durability. Use for attach primitives, background errors, durable host logs, or replacing console.* in library code.

Method shorthand in return objects for JSDoc preservation. Use when factory functions have internal helpers that should expose docs, or hovering over returned methods shows no JSDoc.

Monorepo scripts, package boilerplate, conventions. Use when: "how do I run", "bun run", "build this", "run tests", "typecheck", "create a new package", linting, scaffolding packages.

Test a product, API, utility, or design by stating what it actually does in one sentence. Use when auditing coherence or looking for orphaned surfaces, duplicate verbs, or inert abstractions, not for plain code-comprehension questions.