jtmthf
- 8 skills
- 0 followers
- 7 hours ago last updated
- ▌ Graphite · jtmthf bundleStacked PR workflow using the Graphite CLI (gt). Use this skill whenever the user wants to create stacked PRs, break a feature into reviewable chunks, submit or sync branches with Graphite, navigate a stack, or manage PR workflows with gt commands. Also trigger when the user mentions "gt", "graphite", "stacked PRs", "stacked diffs", or wants to split large changes into a chain of dependent pull requests — even if they don't explicitly say "graphite."
- ▌ Agents Md · jtmthf bundleAuthor or improve AGENTS.md / CLAUDE.md agent-instruction files — a lean root, progressive disclosure via nested files, conditional gating, the vendor-neutral AGENTS.md + CLAUDE.md setup, and grounding the file in real pain points mined from Claude Code session logs.
- ▌ Test Writer · jtmthf bundleExpert JavaScript/TypeScript test engineer. MUST use this skill whenever the user asks you to write, add, fix, update, or improve tests — including unit tests, integration tests, component tests, E2E tests, interaction tests, and test coverage. Covers all major JS/TS test frameworks: Vitest, Jest, Node test runner, Playwright, React Testing Library, Vitest browser mode, and Storybook. Also use when users mention test strategy, flaky tests, test structure, mocking approach, testing a component, testing an API, testing a function, testing a hook, or adding test cases for edge cases and bug reproduction. Trigger on any mention of: "write tests", "add tests", "test this", "test coverage", "need tests", "test file", ".test.", ".spec.", "describe(", "it(", "test(", "expect(", "testing library", "playwright test", "vitest", "jest", "storybook play function", or when producing test files even if "test" isn't explicit (e.g., "verify this works", "make sure this doesn't break", "add coverage").
- ▌ Data Modeler · jtmthf bundleInteractive agent for relational database schema design and migration. Guides users through requirements capture, schema analysis, design review, and migration generation. Use when users need to model data, design schemas, add tables or relationships, plan migrations, or discuss database design, entities, foreign keys, or indexes.
- ▌ Voice Writer · jtmthf bundleWrites in Jack Moore's voice and style. Use whenever drafting documents, messages, proposals, announcements, articles, or any text that should sound like Jack. Triggers on "write in my voice", "draft", "write this up", "announcement", "proposal", or when producing text meant to be sent or published as Jack.
- ▌ Ddd Discovery · jtmthf bundleUse this skill whenever the user wants to model a domain, run an event storming workshop, identify bounded contexts, design aggregates, or resolve any DDD modeling challenge. Unlike general DDD knowledge (which you already possess), this skill provides a structured facilitation process — phased discovery, one-question-at-a-time interrogation of domain experts, anti-pattern detection, and brownfield codebase reverse-engineering. Triggers on domain modeling, DDD, event storming, aggregate design, bounded context, context map, domain discovery, or any request to map, untangle, or understand a system's domain structure.
- ▌ GRAPHQL Schema Designer · jtmthf bundleGraphQL schema design, review, and evolution. MUST use this skill whenever the user creates, modifies, extends, reviews, or refactors a GraphQL schema — whether SDL files, code-first frameworks (Pothos, Nexus, TypeGraphQL, gqlgen, Strawberry, graphql-ruby, Hot Chocolate, Juniper), or federation. Trigger on: designing schemas for new apps or features, adding types/queries/mutations, reviewing schema quality, refactoring CRUD to domain mutations, adding payload unions or error types, modeling entity relationships, working with .graphql files, or any task whose output includes GraphQL type definitions. Also trigger on phrases like "GraphQL schema", "add a mutation", "new GraphQL type", "schema for", "design the API types", "review this schema", "payload union", "extend the schema". Do NOT trigger for: writing client queries/fragments, debugging resolvers, codegen config, DataLoaders, CORS, auth middleware, rate limiting, or testing endpoints.
- ▌ Typescript Coding Style · jtmthf bundleApplies Jack Moore's personal TypeScript/TSX coding style — derived from his own pre-2025 open-source code and gists, not a generic style guide. Use this whenever writing, generating, refactoring, or reviewing TypeScript or TSX code: new functions, modules, types, React components, hooks, API handlers, utility libraries, or any code-generation task in a TS/TSX file. Trigger even when the user doesn't explicitly ask for "my style" — it should shape ordinary TypeScript work by default. Key signals: declarative composition over loops, object-param destructuring instead of positional args, plain factory functions over classes, discriminated unions and exhaustive `match` for state, errors modeled as values (Result/Option) instead of scattered try/catch, erasable syntax (no enums/access modifiers/decorators), fully spelled-out identifiers, and minimal comments. Always defers to a project's existing conventions first (lint config, prevailing patterns, framework requirements like NestJS decorators) — this skill fills