epicenterhq
- 78 skills
- 0 followers
- 4.8k repo stars
- 2 days ago last updated
- ▌ 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 bundleFind and carry through worthwhile code simplifications across recent edits, named files, or a subsystem. Use when asked for a collapse pass, a refactoring pass, another simplification pass, "simplify this", to clean up code, or to hunt for indirection and dead abstractions. Specific transformations, planning requests, review-only requests, and explicit file limits determine the work. Use control-flow for a request limited to one function's branching.
- ▌ 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.
- ▌ Asymmetric Wins · epicenterhqEvaluate whether refusing a small promise would eliminate disproportionate complexity. Use when judging asymmetric wins or a proposed refusal of fidelity, compatibility, fallbacks, modes, or duplicate paths; use product-collapse to develop simpler product workflows.
- ▌ Worktree Hygiene · epicenterhqDelete local Git worktrees and branches once their work is on GitHub, with `bun run worktrees`. Use when cleaning up worktrees or local branches, or deciding whether one is safe to delete, not when creating branches or commits.
- ▌ 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/.
- ▌ Adversarial Review · epicenterhq bundleIndependently form and test models of what a system should do, challenge the design against them, and work as a review group toward an agreed direction. Use when asking for an adversarial review, an independent architecture review, or an adversarial checkpoint on a plan or cumulative implementation. Do not use for routine final code inspection, which belongs to post-implementation-review.
- ▌ Skills And Instructions · epicenterhq bundleDesign, write, and maintain skills and agent instructions. Use when the user asks to create, revise, evaluate, or troubleshoot skills or agent instructions, including investigating selection behavior to improve the guidance and deciding where guidance belongs.
- ▌ Specification Writing · epicenterhq bundleWrite technical specs that let agents implement autonomously. Use for "write a spec", "plan this feature", "create a planning doc".
- ▌ 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.
- ▌ 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.
- ▌ 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.
- ▌ Dialectic · epicenterhq bundleWork out an unsettled idea together through its intent, proposed form, and consequences in practice. Use when the user explicitly requests standalone dialectic, or another active skill invokes it within its task.
- ▌ 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.
- ▌ 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.
- ▌ 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, including constraints that need to name an invalid literal key or string in a compiler error.
- ▌ Query Layer · epicenterhqCompose Result-returning services into TanStack Query with Wellcrafted's resultQueries and resultMutations, one invalidation rule per QueryClient, and composition by spread. Use when editing createQuery, createMutation, resultQueries, resultMutations, resultQueryOptions, resultMutationOptions, runQuery, runMutation, a QueryClient or MutationCache, cache keys, invalidation, or optimistic updates.
- ▌ 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.
- ▌ 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.
- ▌ Post Implementation Review · epicenterhqReview the combined implementation for correctness, clear ownership, and unnecessary complexity. Use when finishing substantial code implementation or refactoring, reviewing changes across callers or public APIs, or asked for a second pass or final sweep. Small edits need proportionate checks; independent architectural review belongs to adversarial-review.
- ▌ Factory Function Composition · epicenterhq bundleFactory function patterns to compose clients and services. Use when wrapping resources with domain methods, refactoring mixed client/service/method options, or documenting returned factory methods.
- ▌ 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.
- ▌ 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.
- ▌ Platform Seams · epicenterhqApply Epicenter's one-build rule, where a capability package decides at run time whether the page is in a Tauri window and loads its desktop implementation when it connects or first acts, and apps branch on what a capability offers. Use when adding or changing a desktop implementation, a capability only some surfaces have, a view only they show, or the desktop shell's build.
- ▌ Services Layer · epicenterhq bundleApply Epicenter's service-boundary patterns for UI-free capabilities, explicit inputs, Result fallibility, lifecycle factories, and a capability package that picks its browser or desktop implementation when the page runs. Use when creating or refactoring an app's services or their contract, provider or connection dispatch, or a desktop service over the shell, the credentials file, or the account.
- ▌ Writing Voice · epicenterhq bundleHelp the author give their thought a convincing expression that feels unmistakably theirs. Use when drafting or revising prose, developing voice or tone, doing an ear pass, or comparing passages and integrating selected wording.
- ▌ Consult Claude · epicenterhq bundleGive Claude Opus 5.5 responsibility for reasoning, design judgment, read-only investigations, recommendations, or finished text drafts. Use when the result benefits from thoughtful reasoning or taste, when asked to consult Claude, or when supplying the Claude seat of an independent review. Completed edits and executable experiments belong to delegate-claude.
- ▌ Error Handling · epicenterhq bundleDefine tagged errors and apply Wellcrafted Result patterns from fallible operation to final presentation. Use when a task involves error handling in TypeScript, defining defineErrors variants, replacing try/catch, adding trySync or tryAsync, choosing whether to propagate, recover from, or present a failure, or consuming Results with unwrap. For recording diagnostics, use logging; for cache lifecycle, use query-layer.
- ▌ 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.
- ▌ 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.
- ▌ 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.
- ▌ Abstraction · epicenterhqShape a complex idea, workflow, design, or report on work into the smallest complete surface a person needs for the next judgment. Use when summarizing, reporting on, or explaining complex work to someone who must judge or act on it, when proposing a change that is easier to judge shown than described, or when an explanation obscures its point or makes the user carry unnecessary complexity.
- ▌ 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.
- ▌ 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.
- ▌ Testing · epicenterhq bundleChoose useful regression coverage and apply Epicenter test conventions for setup, Result assertions, type tests, naming, and pruning. Use when writing, reviewing, deleting, or reorganizing tests, especially `*.test.ts` files.
- ▌ Handoff · epicenterhqDraft 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.
- ▌ 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.
- ▌ Arktype · epicenterhqArktype: runtime validation, discriminated unions with .merge()/.or(), spread keys. Use when mentioning arktype, type(), union types, command/event schemas.
- ▌ Auth · epicenterhqEpicenter account package: `@epicenter/account`, the auth client Svelte reads through `reactive`, OAuth sign-in for browser and desktop apps, the Account lifetime, account-bound fetch, and hosted resource authorization. Use when editing Epicenter auth clients, session state, hosted sign-in, or how a route boots from auth.
- ▌ 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.
- ▌ Delegate Claude · epicenterhqDelegate a bounded implementation, prototype, benchmark, or file artifact to Claude Code, which owns the reasoning and delivery in the current checkout or a selected standalone clone, directing a Codex helper as sole code writer for substantial changes. Use when an authorized task benefits from Claude's reasoning, design judgment, or taste, or when asked to delegate execution to Claude. Answer-only investigations, recommendations, and text drafts belong to consult-claude.
- ▌ English 120 Writing · epicenterhq bundleTrigger 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.
- ▌ Conversation Hygiene · epicenterhq bundleTriage and archive accumulated Codex conversations without losing wanted work. Use when cleaning up old Codex threads, deciding which conversations still need attention, or resuming a large conversation cleanup. Do not use for ordinary backlog capture, feature implementation, or issue-tracker cleanup.
- ▌ Learn From Corrections · epicenterhq bundleExplicitly invoked review of a conversation to update the skills responsible for avoidable corrections. Work backward from disagreements, inspect the skills actually invoked, and develop and verify appropriate skill changes. Use only when directly invoked; ordinary corrections during a task do not select this workflow.
- ▌ Computer Use Driven Iteration · epicenterhqImprove an interactive product through repeated computer-use simulations, bounded Claude implementation, verification, and reflection to find opportunities to collapse complexity. Use when asked to keep exercising and improving a UI across implementation waves. Skip one-off browser actions, routine fixes, and API-only work without an interactive product to exercise.
- ▌ Rethink · epicenterhq bundleDevelop the strongest grounded vision of a system, API, or abstraction through dialectic, then work backward to make it real. Use when the user asks for greenfield thinking, radical options, a clean break, first-principles design, or questions the current organizing idea or boundaries.
- ▌ 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.
- ▌ 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.
- ▌ 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.
- ▌ 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".
- ▌ 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.
- ▌ 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.
- ▌ 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.
- ▌ 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.
- ▌ Define Errors · epicenterhqdefineErrors from wellcrafted: variant factories, extractErrorMessage, InferErrors/InferError, call site patterns. Use when creating error types or reviewing error patterns.
- ▌ 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.
- ▌ 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.
- ▌ 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.
- ▌ 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.
- ▌ 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.
- ▌ 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.
- ▌ 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.