epicenterhq
- 70 skills
- 0 followers
- 4 hours ago last updated
- ▌ Grill With Docs · epicenterhq bundleStress-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.
- ▌ Git · epicenterhqApply 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.
- ▌ Yjs · epicenterhq bundleApply 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.
- ▌ Auth · epicenterhqEpicenter 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 clients, session state, hosted sign-in, or how a route boots from auth.
- ▌ Hono · epicenterhqHono 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.
- ▌ Tauri · epicenterhqTauri commands, permissions, capabilities, security config, path handling, cross-platform file ops, and native filesystem APIs. Use when mentioning Tauri, desktop apps, Rust commands, invoke, capabilities, permissions, ResourceId, file paths, or platform differences.
- ▌ Autumn · epicenterhqAutumn billing in Epicenter: `autumn.config.ts`, `autumn-js` credit checks, `atmn` CLI, plan gates, and metered AI usage. Use when changing billing, pricing, credits, plan access, refunds, or usage events.
- ▌ Svelte · epicenterhq bundleApply Epicenter’s Svelte 5 patterns for runes, components, lifecycles, and workspace-backed state. Use when editing `.svelte`, `.svelte.ts`, or Svelte UI state.
- ▌ Arktype · epicenterhqArktype: runtime validation, discriminated unions with .merge()/.or(), spread keys. Use when mentioning arktype, type(), union types, command/event schemas.
- ▌ Handoff · epicenterhqDraft a cold-start prompt for a manually operated Claude Code session. Use when the user asks for a handoff, continuation prompt, or something to copy and paste into Claude Code, not when the active agent should ask Claude to review or implement the work.
- ▌ Logging · epicenterhqwellcrafted/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.
- ▌ Styling · epicenterhqCSS and Tailwind, cn(), flex layouts. Use for "style this", "fix the CSS", "add classes", "not scrolling", "overflow", Tailwind utilities.
- ▌ Testing · epicenterhq bundleApply Epicenter test-file conventions for setup, factories, Result assertions, type tests, naming, and pruning. Use when writing, reviewing, deleting, or reorganizing tests, especially `*.test.ts` files.
- ▌ Typebox · epicenterhqTypeBox patterns for runtime schema validation and JSON Schema generation. Use when mentioning TypeBox, Standard Schema, or schema-based validation.
- ▌ Diagnose · epicenterhq bundleDiagnose 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.
- ▌ Grill Me · epicenterhqInterview 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".
- ▌ Monorepo · epicenterhqMonorepo 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 · epicenterhqTypeScript 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.
- ▌ Dialectic · epicenterhq bundleMake an unsettled model intelligible through the deliberate collision of concrete articulations. Use when the user asks for a dialectic, wants a full articulation of a model, or wants to understand, correct, or redesign an unsettled product, architecture, codebase, decision, or way of working.
- ▌ Prototype · epicenterhq bundleBuild 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.
- ▌ Sveltekit · epicenterhqApply SvelteKit patterns for routing, server modules, form actions, hooks, cookies, adapters, and invalidation. Use when editing route files, hooks, `app.d.ts`, or SvelteKit behavior.
- ▌ UI Design · epicenterhq bundleDesign and review Epicenter interfaces while collapsing local UI primitives into the shared component system. Use when co-designing, exploring comparable apps, turning a feature idea into Svelte UI, or changing `packages/ui`, not for a tiny CSS repair.
- ▌ Wayfinder · epicenterhqPlan work too large for one agent session as decision tickets resolved one at a time. Use when the user asks for a multi-session roadmap or long-running plan.
- ▌ Agent Goal · epicenterhqDraft 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 · epicenterhqFind 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.
- ▌ Code Prose · epicenterhqApply 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.
- ▌ Typescript · epicenterhq bundleApply project conventions for TypeScript types, imports, generics, factories, and runtime schemas. Use when editing `.ts` files or reviewing TypeScript design and tests.
- ▌ Abstraction · epicenterhqShape a complex idea, workflow, or design into the smallest complete surface a person needs for the next judgment.
- ▌ Drizzle Orm · epicenterhqApply 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.
- ▌ Query Layer · epicenterhq bundleQuery boundaries with TanStack Query and Wellcrafted Results. Use when editing createQuery, createMutation, resultQueryOptions, resultMutationOptions, defineQuery, defineMutation, defineKeys, shared cache identity, mutation lifecycle, or service-to-TanStack adapters.
- ▌ Refactoring · epicenterhqApply 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.
- ▌ Rust Errors · epicenterhqRust to TypeScript error handling for Tauri apps. Use when mentioning Rust errors, Tauri command errors, invoke errors, or defining Rust error types for TS consumption.
- ▌ Control Flow · epicenterhqLinearize 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" pass over a diff or package, which belongs to collapse-pass.
- ▌ Pull Request · epicenterhq bundleDraft 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.
- ▌ Social Media · epicenterhqDraft social posts for LinkedIn, Reddit, or Twitter/X. Use when asked to write a post, tweet, announcement, or platform-specific version.
- ▌ Collapse Pass · epicenterhq bundleRemove 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.
- ▌ Define Errors · epicenterhqdefineErrors from wellcrafted: variant factories, extractErrorMessage, InferErrors/InferError, call site patterns. Use when creating error types or reviewing error patterns.
- ▌ Documentation · epicenterhqIn-code documentation, folder READMEs, code comments. Use when: "document this", "add JSDoc", "write a README", "explain this code", or writing README.md/JSDoc.
- ▌ Github Issues · epicenterhqGitHub issue comment guidelines for community interaction. Use when: "respond to this issue", "reply to this bug report", "close this issue", or any GitHub discussion.
- ▌ Teaching Page · epicenterhq bundleDesign 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. Not for authored Vault pages, which belong to page-writing, and not for a dialectic turn asking for a judgment.
- ▌ Writing Voice · epicenterhqRevise substantial prose so it sounds like Braden while preserving his vocabulary, humor, certainty, and emphasis. Use when prose no longer sounds like me or needs a voice, tone, or ear pass in UI copy, documentation, or messages.
- ▌ Consult Claude · epicenterhq bundleRun Claude Code as an independent reviewer or research laboratory while you keep ownership of the live repository. Use when the user asks to consult Claude, requests a Claude review, or asks Claude to investigate or research independently.
- ▌ Error Handling · epicenterhq bundleApply 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.
- ▌ Platform Seams · epicenterhqApply Epicenter’s `#platform/*` build-time seam across browser, Tauri, and host targets. Use when adding or changing a seam, build condition, typecheck leaf, or deciding whether code belongs behind one.
- ▌ Services Layer · epicenterhq bundleApply 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` barrel.
- ▌ Spec Execution · epicenterhqExecute `specs/*.md` plans through working checkpoints. Use when the user says "execute this spec", "implement this plan", "run the spec", or points at a spec file.
- ▌ Svg Animations · epicenterhq bundleAnimate 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 · epicenterhqApply 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.
- ▌ Asymmetric Wins · epicenterhqIdentify 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 disproportionate complexity.
- ▌ Change Proposal · epicenterhqShow a proposed code change with before/after diffs, diagrams, or comparison tables. Use when the user asks to compare approaches or wants a visual proposal before a multi-file edit.
- ▌ Radical Options · epicenterhqCompare a current approach with a cleaner design from first principles before editing. Use when an abstraction feels wrong, a fix becomes a band-aid, or complexity spreads across layers.
- ▌ Publication Pass · epicenterhqDecide 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.
- ▌ Worktree Hygiene · epicenterhqSafely reap merged Git worktrees and branches across Epicenter harnesses. Use when cleaning `git worktree list`, removing orphaned or detached worktrees, or deciding whether one is safe to delete, not when creating branches or commits.
- ▌ One Sentence Test · epicenterhqTest 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.
- ▌ Agent Instructions · epicenterhq bundleDesign, audit, and validate repository guidance across AGENTS.md, CLAUDE.md, and `.agents/skills`. Use when creating skills, tuning descriptions, or reviewing instruction sprawl and routing.
- ▌ Cloudflare Workers · epicenterhqCloudflare Workers patterns for Worker runtime APIs, Durable Objects, KV, R2, D1, Queues, WebSockets, streaming responses, bindings, wrangler configuration, and deployment limits. Use when users mention Cloudflare Workers, Durable Objects, KV, R2, D1, Queues, wrangler, or edge runtime behavior.
- ▌ Standalone Commits · epicenterhq bundleSplit work into reviewable, auditable commits ordered by dependency. Use when planning commit waves, staging changes, or deciding whether a commit is too broad, tiny, incomplete, or hard to revert.
- ▌ Technical Articles · epicenterhqTechnical articles and blog posts with honest trade-offs. Use when: "write a blog post", "draft an article", "write about this", creating articles in docs/articles/.
- ▌ Google Devdocs Style · epicenterhq bundleWrite 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.
- ▌ Specification Writing · epicenterhq bundleWrite technical specs that let agents implement autonomously. Use for "write a spec", "plan this feature", "create a planning doc".
- ▌ Method Shorthand Jsdoc · epicenterhqMethod 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.
- ▌ Greenfield Clean Breaks · epicenterhq bundleReconsider 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.
- ▌ Cohesion Over Testability · epicenterhq bundleCollapse 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.
- ▌ Type Level Error Messages · epicenterhqMake TypeScript errors readable with template-literal constraint messages. Use when constraining literal object keys or string shapes and the error should point to the offending value.
- ▌ Better Auth Best Practices · epicenterhqBetter Auth server/client setup: `auth.ts`, generated schema, DB adapters, sessions, cookies, env vars, and plugins. Use when mentioning Better Auth, betterauth, auth handlers, OAuth, email/password, or session configuration.
- ▌ Codex Task Backlog Hygiene · epicenterhq bundleAudit 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.
- ▌ Post Implementation Review · epicenterhqReview completed implementation work for dead paths, stale imports, invariant ownership, and API shape, then delegate focused checks. Use when reviewing work after implementation, doing a second pass, or performing a final sweep.
- ▌ Factory Function Composition · epicenterhq bundleFactory function patterns to compose clients and services. Use when wrapping resources with domain methods or refactoring mixed client/service/method options.
- ▌ Improve Codebase Architecture · epicenterhq bundleScan 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.
- ▌ Better Auth Security Best Practices · epicenterhq bundleBetter Auth security hardening: rate limits, secrets, CSRF, trusted origins, cookies, sessions, OAuth tokens, and audit logging. Use when reviewing auth security, brute-force protection, token handling, or deployment safety.