EpicenterHQ/epicenter

adversarial-review

Independently challenge a design and its underlying model to find deletion prizes and stronger invariants. Use when asking for an adversarial review, an independent architecture review, or an adversarial checkpoint on a plan or cumulative implementation. Do…

原文の言語: 英語

consult-claude

Get Claude Code's second opinion on a proposal or implementation. Use when the user asks to consult Claude, requests Claude's design judgment or research, or invokes a design-review workflow that includes Claude. Do not enlist Claude merely because a task is…

原文の言語: 英語

abstraction

Shape a complex idea, workflow, or design around the judgment a person needs to make. Use when an explanation obscures its point or makes the user carry unnecessary complexity. Do not use for routine execution of a clear request.

原文の言語: 英語

agent-instructions

Write and maintain repository guidance across AGENTS.md, CLAUDE.md, and .agents/skills. Use when creating or editing skills, deciding where instructions belong, or diagnosing instruction sprawl and skill selection. Do not use merely because another skill is…

原文の言語: 英語

asymmetric-wins

Identify an asymmetric win by refusing a small promise that would eliminate disproportionate complexity. Use when the user asks about asymmetric wins, pixel perfect fidelity, compatibility, fallbacks, modes, duplicate paths, or what would delete…

原文の言語: 英語

cohesion-over-testability

Collapse test-shaped production boundaries while preserving behavior and coverage. Use when a helper, wrapper, injected dependency, or export exists mainly to let a unit test reach internals.

原文の言語: 英語

collapse-pass

Remove indirection that does not earn its boundary across a diff or package. Use when the user asks to run a collapse pass, simplify this broadly, audit dead abstractions, or shrink a surface, not when one function’s branching is the target.

原文の言語: 英語

dialectic

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,…

原文の言語: 英語

english-120-writing

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…

原文の言語: 英語

handoff

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…

原文の言語: 英語

one-sentence-test

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.

原文の言語: 英語

post-implementation-review

Review cumulative implementation for structural collapse, invariant ownership, and correctness. Use for reviewing work after implementation, doing a second pass, or performing a final sweep. Independent structural verdicts belong to adversarial-review.

原文の言語: 英語

pull-request

Draft and review Epicenter pull request titles and bodies, including changelog and merge details. Use when creating a PR or editing its text, not for local commits, branches, or issue replies.

原文の言語: 英語

refactoring

Apply caller-aware, behavior-preserving code simplifications such as inlining, branch collapse, and typed access boundaries. Use when cleaning up code or planning focused refactor commits.

原文の言語: 英語

rethink

Pursue the best possible version of a system, API, or abstraction, develop the vision through dialectic, and work backward to make it real. Use when the user asks for greenfield thinking, radical options, a clean break, first-principles design, or says the…

原文の言語: 英語

specification-writing

Write technical specs that let agents implement autonomously. Use for "write a spec", "plan this feature", "create a planning doc".

原文の言語: 英語

teaching-page

Design a self-contained HTML page that teaches one thing, using space and a single accent instead of boxes and colour. Use when building an explainer, lesson, diagram, or walkthrough page, or when an existing page reads dense, overwhelming, or over-decorated.…

原文の言語: 英語

typescript

Apply project conventions for TypeScript types, imports, generics, factories, and runtime schemas. Use when editing `.ts` files or reviewing TypeScript design and tests.

原文の言語: 英語

writing-voice

Shape prose so it sounds like Braden, with conversational precision, rhythm, humor, and earned poetic turns. Use for substantial drafting or revision, an ear pass, and explicit voice or tone work in prose, UI copy, documentation, or messages. Do not use to…

原文の言語: 英語

auth

Epicenter auth packages: `@epicenter/auth` and the Svelte adapter at `@epicenter/auth/svelte`, OAuth sessions, identity state, auth-owned fetch/WebSocket, and the reload gate that makes a page lifetime one auth generation. Use when editing Epicenter auth…

原文の言語: 英語

publication-pass

Decide whether an authored piece is ready to represent its writer in public by testing recognition, legibility, integrity, and worth. Use before publishing a post, video, essay, or controversial idea; not for platform formatting or audience approval.

原文の言語: 英語

yjs

Apply Epicenter’s Yjs 14 patterns for row documents, transactions, persistence, and synchronization. Use when working with `@y/y`, CRDTs, collaborative editing, awareness, or Yjs storage and providers.

原文の言語: 英語

logging

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.

原文の言語: 英語

svelte

Apply Epicenter’s Svelte 5 patterns for runes, components, lifecycles, and workspace-backed state. Use when editing `.svelte`, `.svelte.ts`, or Svelte UI state.

原文の言語: 英語

monorepo

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.

原文の言語: 英語

tsconfig

TypeScript config conventions for this monorepo: the two-base layering, the seven leaf tiers, and the never-redeclare list. Use when adding a package, editing any tsconfig.json, picking a tier for a new app, or debugging module resolution.

原文の言語: 英語

code-prose

Apply Orwell's rules to the prose inside code — identifiers and comments — without changing behavior. Use when names, word choice, or comments need an editorial pass.

原文の言語: 英語

control-flow

Linearize complex control flow with early returns, guard clauses, nested ifs, and natural-language conditions. Use when flattening nested conditions, linearizing try/catch logic, or separating mixed throw-and-return handlers, not for a broad "simplify this"…

原文の言語: 英語

diagnose

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.

原文の言語: 英語

git

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.

原文の言語: 英語

prototype

Build a throwaway prototype to answer a focused logic, state-model, or UI question before committing to production design. Use when the user asks to prototype, sanity-check a model, mock up UI, explore design options, or try a few designs.

原文の言語: 英語

services-layer

Apply Whispering service-boundary patterns for UI-free capabilities, explicit inputs, Result fallibility, Live objects, lifecycle factories, and platform variants. Use when creating or refactoring services, contracts, provider dispatch, or the `$lib/services`…

原文の言語: 英語

svg-animations

Animate SVGs with SMIL, CSS keyframes, stroke drawing, shape morphing, and motion paths. Use when adding motion to SVGs such as spinners, logos, draw-in effects, or morphing icons, not for static drawing or icon layout.

原文の言語: 英語

tanstack-table

Apply TanStack Table UI-state patterns for Svelte data tables, including columns, rendering, sorting, filtering, pagination, and row identity. Use when building or reviewing data-table UI, not Epicenter workspace storage tables.

原文の言語: 英語

agent-goal

Draft a `/goal` line that gives long-running Codex or Claude Code work an objective, validation evidence, and a stop condition. Use when the user explicitly asks for `/goal`, an agent goal, or a completion condition.

原文の言語: 英語

code-audit

Find recurring Epicenter code smells and scope the cleanup they require. Use for periodic audits, cleanup PRs, post-refactor reviews, or reviews of a primitive’s consumers.

原文の言語: 英語

codex-task-backlog-hygiene

Audit Codex tasks and preserve unowned outcomes in `BACKLOG.md` while closing completed or superseded chats. Use when Codex task ownership or archive state needs cleanup, not generic issue-tracker or project-backlog work.

原文の言語: 英語

drizzle-orm

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.

原文の言語: 英語

error-handling

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.

原文の言語: 英語

google-devdocs-style

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.

原文の言語: 英語