jonmumm/skills
Skill Claude CodeCodex
Invoke this skill anytime you are creating a plan—such as crafting an RFC, writing a PRD, starting a new app, or proposing an architecture change. It will relentlessly interview the user to resolve all dependencies and edge cases.
jonmumm/skills
Skill Claude CodeCodex
Enforce a hard-cut cleanup policy: keep one canonical implementation and delete compatibility, migration, fallback, adapter, coercion, and dual-shape code. Use for pre-release or internal-draft refactors where the goal is one final shape, especially when changing schemas, contracts, persisted state, routing…
jonmumm/skills
Skill Claude CodeCodex
Configure and troubleshoot MCP servers in Claude Code. Quick reference for installing, verifying, and debugging MCP connections (Slack, Sentry, PostHog, Figma, Frame0, Playwright, Neon, Linear, qmd). Use when asked to "set up MCP", "add MCP", "connect to", "why isn't MCP working", "/mcp", or when an MCP tool call…
jonmumm/skills
Skill Claude CodeCodex
Multi-milestone autonomous development for large goals. Decomposes a big objective into milestones with validation gates. Orchestrator plans, workers build via TDD in isolated worktrees, independent validators exercise the system as a black box against a validation contract. Fix features close gaps. Converges until…
jonmumm/skills
Skill Claude CodeCodex
Run and interpret Stryker mutation testing; kill survivors to reach ≥95% score. Use when running mutation tests, setting up Stryker, interpreting survivors, or verifying test quality after TDD.
jonmumm/skills
Skill Claude CodeCodex
Autonomous AFK development loop. Sequentially works through a specs/bugs backlog: grill-me preflight → evals-first surface → pick task → testing-trophy TDD → progressive commits → eval stack (hooks → integration → e2e + screenshots → LLM judges → codex review) → commit → morning briefing. Use when going AFK — lunch…
jonmumm/skills
Skill Claude CodeCodex
Invoke this skill when setting up new tech stacks, configuring project architecture, or replacing untyped boundaries with strict, compiler-enforced constraints. Treat types as a development accelerator. Prefer tools like TanStack Router, Zod, and Drizzle to build end-to-end type safety.
jonmumm/skills
Skill Claude CodeCodex
Apply George Orwell's six rules for clear writing to any prose you produce — PR descriptions, commit messages, code comments, docs, RFCs, Slack updates, emails, and writeups. Cut jargon, prefer short words, kill needless words, favor the active voice, and drop stale metaphors. Use when writing or editing prose, when…
jonmumm/skills
Skill Claude CodeCodex
Enforce the "parse, don't validate" discipline at every system edge. Data crossing a trust boundary must be parsed through a schema before entering application logic. Language-agnostic — covers TypeScript, Python, Go, Swift, and Kotlin. Use when writing code that receives external data (API responses, HTTP requests…
jonmumm/skills
Skill Claude CodeCodex
The 10 operating principles for building software with AI agents — when to use them, what failure mode each one prevents, and which skills operationalize them. Use when bootstrapping a new project, reviewing an agent workflow that drifted, deciding between tactical fixes and structural changes, or whenever the…
jonmumm/skills
Skill Claude CodeCodex
Sharpen product design judgment for software UI/UX, interaction flows, jobs-to-be-done, hierarchy, trust, governance surfacing, and competitor-informed critique. Use when Codex needs to critique or shape a product surface, card, panel, workflow, chat experience, or design strategy instead of merely suggesting visual…
jonmumm/skills
Skill Claude CodeCodex
Create AFK Ralph loop scripts for any task. Interrogates the user to nail down requirements, then generates a complete .ralph/ directory with loop script, backlog, progress tracking, and lessons file. Use when the user wants to run an autonomous Claude loop, create a ralph script, go AFK on a task, run something in a…
jonmumm/skills
Skill Claude CodeCodex
Write and refactor React components to be small, composable, and customizable, doing one thing well. Improve rendering performance, maintainability, and reusability by leveraging compound components, prop spreading, and utility class merging. Apply these patterns when authoring new components or breaking down large…
jonmumm/skills
Skill Claude CodeCodex
Minimize unnecessary React re-renders when consuming external state (XState, @xstate/store, Zustand, Redux, Nanostores, context). Prefer selector-based subscriptions over useState(wholeObject). Use when dealing with external state in React, optimizing re-renders, choosing state patterns, or integrating with these…
jonmumm/skills
Skill Claude CodeCodex
Focuses exclusively on writing robust integration tests at system boundaries (seams) rather than writing brittle, shallow unit tests. Use when adding test coverage to an existing system, or testing an integration between two distinct modules.
jonmumm/skills
Skill Claude CodeCodex
Split an oversized PR (or local branch) into a few small, independently green, reviewer-aligned PRs using GitHub's native stacked pull requests (gh-stack), and retire the original PR gracefully. Use when asked to "split this PR", "break this up into smaller PRs", "stack this", "this PR is too big", or when a diff…
jonmumm/skills
Skill Claude CodeCodex
Storybook play function integration testing for TanStack Start/Router apps. Covers Vite config for blocking server code, router/query/theme decorators, state mocking strategies (props, collections, React Query cache, actor-kit), play function patterns, viewport coverage, and vitest browser test runner. Use when…
jonmumm/skills
Skill Claude CodeCodex
A multi-agent AI development workflow. Front-loads planning questions (grill-me), then launches parallel agents in Git worktrees: a Feature agent builds from a backlog via TDD, while CRAP, Mutation, and Acceptance agents continuously harden the codebase using deterministic metrics. Use when the user says "swarm", "run…
jonmumm/skills
Skill Claude CodeCodex
Pull all Jira tickets assigned to me that aren't done and help create copy-pasteable prompts to kick them off in other Claude Code or Cursor sessions. Use when asked to "plan my tasks", "what should I work on", "task planner", "generate prompts for my tickets", or "kick off my Jira tickets".
jonmumm/skills
Skill Claude CodeCodex
After finding a bug caused by insufficient test coverage, brainstorm test cases across the entire feature area that could uncover similar bugs. Systematically explores edge cases, boundary conditions, state transitions, and integration points to identify coverage gaps before they become production incidents.
jonmumm/skills
Skill Claude CodeCodex
Kent C. Dodds' Testing Trophy: write more integration tests, fewer unit tests, confidence over coverage. Covers React (Storybook + play functions), Cloudflare Workers (vitest-pool-workers + D1), and Swift (XCTest UI + snapshot). Use when deciding test strategy, writing new tests, or reviewing test quality.
jonmumm/skills
Skill Claude CodeCodex
Formal verification of system designs using TLA+ and the TLC model checker. Models concurrent state machines, finds race conditions, deadlocks, and invariant violations before any code is written. Also verifies pure algorithm invariants by exhaustively checking all input combinations. Use when the user says "tlaplus"…
jonmumm/skills
Skill Claude CodeCodex
Verify UI changes visually using browser automation before telling the user it's done. Use when making CSS, layout, or visual changes to web apps — especially Starlight docs sites, landing pages, or any frontend work. Triggers on "does this look right", "verify the UI", "check the layout", or after any CSS/HTML change.
jonmumm/skills
Skill Claude CodeCodex
Verified Spec-Driven Development (VSDD) — a rigorous AI-native engineering methodology that fuses Spec-Driven Development, Test-Driven Development, and adversarial verification into a single pipeline. Use when the user says "vsdd", "spec-driven", "verified spec", "adversarial review", "zero-slop", "full verification"…