Loading the repository README…
Showing 40 of 63 collected skills.
Find and carry through worthwhile code simplifications across recent edits, named files, or a subsystem. Use for a collapse pass, a refactoring pass, another simplification pass, "simplify this", clean up code, or a hunt for indirection and dead abstractions.…
Apply Epicenter’s Svelte 5 patterns for runes, components, lifecycles, and workspace-backed state. Use when editing `.svelte`, `.svelte.ts`, or Svelte UI state.
Independently pursue the strongest greenfield design, challenge the underlying model, and find concrete deletion prizes. Use when asking for an adversarial review, an independent architecture review, or an adversarial checkpoint on a plan or cumulative…
Improve 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…
Assign Claude Code a read-only investigation, recommendation, or finished text draft. Use when asked to consult Claude or when a design-review workflow includes Claude. Completed edits and executable experiments belong to delegate-claude.
Delegate a bounded implementation, prototype, benchmark, or file artifact to Claude Code, then verify and integrate its completed work. Use when the user explicitly authorizes Claude to own execution. Read-only advice belongs to consult-claude.
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…
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…
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.
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.
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.
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"…
Factory 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.
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.
Use when the user asks whether there is a better or simpler way, wants to zoom out, questions why existing concepts or boundaries exist, or asks for rethink, redesign, greenfield thinking, first principles, radical alternatives, or a clean break. Also use…
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,…
Choose 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.
Epicenter auth packages: `@epicenter/auth` and the Svelte adapter at `@epicenter/auth/svelte`, direct sessions, identity state, account-bound fetch/WebSocket, and fixed library page bootstrap and deliberate departure. Use when editing Epicenter auth clients,…
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.
Apply Epicenter’s `#platform/*` build-time seam across browser and host targets. Use when adding or changing a seam, build condition, typecheck leaf, or deciding whether code belongs behind one.
Use when editing TanStack Query integration: createQuery, createMutation, resultQueryOptions, resultMutationOptions, defineQuery, defineMutation, defineKeys, shared cache identity, mutation lifecycle, or service-to-TanStack adapters.
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`…
Tauri 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…
Use when a task mentions error handling, Wellcrafted Results, result types, defineErrors, trySync, tryAsync, unwrap, thrown exceptions, or deciding whether to propagate, recover from, or present a failure. For recording diagnostics, use logging; for cache…
Use for wellcrafted/logger, logger sinks, library diagnostics, typed logging, background errors, durable host logs, or replacing console.* in library code.
CSS and Tailwind, cn(), flex layouts. Use for "style this", "fix the CSS", "add classes", "not scrolling", "overflow", Tailwind utilities.
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.
Apply 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…
Triage 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,…
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.
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…
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…
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.
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.
Write technical specs that let agents implement autonomously. Use for "write a spec", "plan this feature", "create a planning doc".
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.…
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…
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.
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.
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.
Copy this prompt into the AI assistant you're using.
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/EpicenterHQ/epicenter.The repository README could not be loaded. You can still explore its Skills below.