skills

Build and deploy sites and Spot Show card/block visual reports on Spot, the internal hosting platform. Use when creating or updating a Spot site, showing plans, architecture diagrams, diffs, terminal output, JSON, screenshots, or when a site needs identity, database, realtime, file uploads, text AI, AI image generation, or Slack notifications.

Manage git worktrees with the gt utility for parallel feature development — create, switch, merge, and clean up worktrees without stashing or branch-switching.

Codex code review closeout: local dirty changes, PR branch vs main, parallel tests.

Use before any creative work or significant changes. Activates on "brainstorm", "let's brainstorm", "deep analysis", "analyze this feature", "think through", "help me design", "explore options for", or when user asks for thorough analysis of changes, features, or architectural decisions. Guides collaborative dialogue to turn ideas into designs through one-at-a-time questions, approach exploration, and incremental validation.

Prove and counter-prove a statement using parallel agents to eliminate confirmation bias. Use when someone says "dialectic", "prove/disprove", "stress test this claim", "is this really true", "argue both sides", or when a statement needs objective analysis from opposing viewpoints.

Run an LLM code review (OpenAI Codex + Anthropic Claude in parallel) on uncommitted changes or against a base ref. Use when user asks to "review my changes", "review uncommitted", "review against <ref>", "code review", "LLM review", "review branch vs <ref>", "second opinion on this diff".

Use after a fix or PR branch is already implemented when the user asks Codex to independently reproduce the original issue on a pre-fix baseline, apply the current branch's fix, reload/reset local data if needed, verify the actual corrected behavior through both data-level checks and realistic browser/UI flows when user-visible behavior is involved, investigate any remaining failures, and report evidence back without changing product code. Triggers include "reproduce then test the fix", "verify this branch locally", "prove the issue is gone", "use local dev env", "test API and browser", "make screenshots", "human test this", or "generate a report".