Tear down the ephemeral dev artifacts an agent session created in the Rabbithole repo — stop background dev servers, delete throwaway test users / secrets from the shared dev deployment, remove scratch files, and (on request) remove the git worktree + merged branches and delete that worktree's own private dev deployment. Use when the user says "clean up", "cleanup", "teardown", "tear it down", "clean up after yourself", or when wrapping up a worktree session. NEVER touches production.
Ship the current branch's PR — rebase onto fresh master if needed, squash-merge the PR (CI is the merge gate); prod then auto-deploys on merge — Vercel via its own GitHub integration, Convex via .github/workflows/deploy.yml — so the agent mainly sequences migrations + verifies the deploys went green. Use when the user says "ship it", "ship this", "/ship", "land it", "merge and deploy", or otherwise wants the current work merged to master AND live. Touches PRODUCTION — any manual prod command (a data migration, or an out-of-band deploy) gates on explicit per-turn approval.
Generate, fact-check, and ship "world-connection stories" (story-bearing bridge edges) for practice-graph knowledge nodes, using the tournament pipeline that won the 2026-07-11 prompt×model experiment. Use when the user asks to add/refresh/improve world-connection stories, hooks, or "wow" content for math skills, or to run the story pipeline on new nodes/domains. Ships via storyRegistry.ts + seedRegistry; prod writes gate on explicit approval.
Spin up a fresh dev environment in one shot — create a new git worktree off the latest master, provision it with the regular `pnpm worktree:up` (a private CLOUD dev deployment + seed), then start BOTH dev servers (Next + Convex watcher) as background tasks and verify the app responds. Use when the user says "/up", "spin up dev", "spin up a worktree", "new worktree", "start a fresh worktree", or otherwise wants a ready-to-use dev environment at the state of master. Dev-only — never touches production.
Use when working on Slack agent/bot code, Chat SDK applications, Bolt for JavaScript projects, or projects using @chat-adapter/slack or @slack/bolt. Provides development patterns, testing requirements, and quality standards.
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form, dashboard, navbar, card, landing section, pricing table, or layout using Chakra UI; wants to add Chakra UI to a project, set up ChakraProvider, run CLI snippets, configure color mode, or fix provider wrapping; or asks about theming — defining brand colors, design tokens, semantic tokens, dark mode values, component recipes, slot recipes, typegen, or ejecting the default theme. Trigger on any Chakra UI building, setup, or theming or charts request, however casually phrased — "add my brand colors", "make a reusable card style", "build a bar chart", "show me a line chart", "make me a login form", "build a sidebar", "add Chakra to my app".
Review, convert, and improve UI code using Chakra UI v3. Use this skill whenever a user wants to review Chakra UI code for issues, convert plain HTML/CSS, Tailwind, CSS Modules, or styled-components to Chakra UI, clean up messy Chakra components, fix layout structure or token usage, or asks anything like "is this correct", "what's wrong with this", "review my component", "refactor this", "clean up", "convert", or "chakra-ify this" — even without the words "review" or "refactor". Trigger on any request to check, improve, or convert Chakra UI code, however casually phrased.
Model Context Protocol (MCP) tools for Capacitor mobile development. Covers Ionic/Capacitor component APIs, plugin documentation, CLI commands, and AI-assisted development via MCP. Use this skill when users want to integrate AI agents with Ionic/Capacitor tooling.