claude-skills

Quickly mock up alternative UI / interface designs as a single self-contained HTML file with a built-in view-switcher across variations, then hand it over: download the file, attach it to an email draft, or (if you wire your own static host) publish it to a URL. Runs a short interview (what to mock, how many variations, what dimension varies, any reference) before building, and passes the output through an anti-AI-slop design gate. Also supports a build-only mode (`/mock --local`, "just build the file", "don't publish") that stops after writing the file. Triggers on `/mock`, "mock up an alternative", "mock up some variations of this screen", "build a few design options for X", "show me alternatives to this interface".

Review a GitHub pull request — the PR-review behavior that used to live in the built-in `/review`, split out now that `/review` is the review orchestrator. Fetches the PR with `gh`, reviews the diff at an evidence-graded bar (only a fully-traced finding is blocking), and optionally posts inline PR comments. For your uncommitted working diff use `/review` instead; this command is specifically for a PR. Triggers on `/github-review`, `/github-review <pr>`, "review this pull request", "review PR #N".

Write a rich session handoff to a pause-*.md file — checklist, decisions, files changed, self-critique, and a verbatim-id "coordinate closet" — so a fresh session can resume the work after /clear (via the auto-resume hook, or /session-resume). Use before you /clear with work still in flight. Triggers on `/handoff`, "write a handoff", "snapshot this session so I can resume later".

Write a detailed session handoff file by hand so the next session can pick up where this one left off. Use when the context window is filling up, you're switching phases, or you're stopping for a break.

Get a second opinion on the current change or a plan from a different model (Codex), and enforce its verdict mechanically. Codex returns a structured JSON verdict — findings scored by priority (0 critical, 1 important, 2 minor, 3 nit) against sev.schema.json — and a gate script turns that into a pass/fail exit code, so a critical or important finding gets fixed or escalated rather than re-argued by the model that wrote the code. Infra failures (rate limit, model reject, empty output) are their own outcome and never count as a clean pass. Use after writing tests, before a deploy or merge, or to review a plan before execution. Triggers on `/codex-review`, `/codex-review --plan <file>`, `/codex-review --base <ref>`, "run a codex review", "get an external review of this diff", "codex-review this before I ship".

Run multiple independent code reviewers (Codex + Gemini + a fresh Claude) on the current diff or a plan, merge their structured verdicts, and apply a consensus-gated challenge round — returning a pass/fail exit code. Use for "panel review this", "get a multi-model review before I ship", "second-opinion review this diff", or /review-panel. Complements single-reviewer /codex-review.

The top-level review verb — decide WHETHER, WHEN, WHICH, and HOW HARD to review a change before reaching for a review tool. Assesses the situation (a plan vs a diff, the risk surface, what changed since the last review, rounds already spent), picks the lightest review shape the risk justifies (in-session self-review → cross-model → multi-model panel), sets an initial round budget it will extend only on convergence, and dispatches. Exists to stop review spirals: reviewing before the plan is formed, reviewing after every trivial edit, or looping a reviewer past the point of convergence. Triggers on `/review`, "should I review this", "what review does this need", "is this worth a codex-review / panel".

Delegate a task or question to the OpenAI Codex CLI running as an isolated subagent, then relay its answer. Use when the user invokes /codex <prompt>, says "ask codex", "have codex look at / do X", or wants a second independent model to investigate a question or make a self-contained edit. Read-only by default; /codex --write lets Codex edit the working tree. Distinct from /codex-review, which is the structured JSON review gate — /codex is a general-purpose Codex delegate.

Use when work may have been dropped between sessions — after a crash, a lockup, parallel-session churn, or on a "did we drop anything?" hunch. Crawls worktrees, local AND remote branches, stashes, deploy targets, and intent docs (handoffs, checklists, plans, coordination journals); triages every item against ground truth (patch-id merge equivalence vs fetched origin/main, live BUILD_SHA/bundle provenance, PR state); presents a ranked loose-end ledger for ONE batch approval; then methodically recovers approved items via playbooks (adopt stray WIP, resume handoffs, rebase→test→push→PR). Never deploys, merges to main, force-pushes, or prunes autonomously. Complements /sitrep (read-only state-of-union) and a live project-board skill if you have one (e.g. /pm); triggers on /sweep, "sweep for dropped work", "what did we lose in the crash", "find stranded work", "recover dropped work", "loose ends sweep".

Use when planning how to spend scarce or expiring access to a premium frontier-tier model (usage-capped, deprecation cliff, "how should I spend my remaining premium-model budget", 2x burn rate, model leaving the plan) — before starting any premium-model session or writing a spend plan.

Use when writing or rewriting text that must sound like a specific real person wrote it (their Reddit post, email, blog, bio, social copy) — the user offers a writing sample, asks to "put this in my voice", "make it sound like me", "de-slop this", or complains that a draft reads like AI. Distills a reusable voice profile from the sample and rewrites against it.

Use when a session is about to bulk-read 3+ files or any single file over ~400 lines, generate predictable boilerplate (tests, fixtures, config scaffolds, doc templates), or compress a long session transcript — and a cheap OpenAI-compatible worker model (Kimi, DeepSeek, OpenRouter, local Ollama) is available via the llm-ask/llm-write/llm-extract CLIs.

Fetch a specific public Reddit post (title, body, and top comments) as clean markdown, by driving a real browser session (Playwright) — because Reddit 403s all non-browser fetches AND closed self-serve API access in Nov 2025. Use whenever you need the actual contents of a Reddit thread from a URL or post id — e.g. "fetch this Reddit post", "what does this thread say", "summarize this r/... discussion", or `/get-reddit <url>`. Runs in a forked Sonnet subagent that CANNOT see the conversation — always pass the Reddit URL/post id (and optional comment limit) as the skill argument.

Memorialize something you just built by generating a self-contained "showcase" page for it — a persuasive, good-looking deep dive: what it is, why it's impressive, how it works — with a screenshot if one can be found or captured, and links to related showcase pages. This is the sales/hype-leaning counterpart to /write-post (which drafts a neutral, no-BS technical post); reach for /brag when you want it to sell. Fast by design, like /idea: ask only what's needed, build the page, don't turn it into a project. Triggers on `/brag <subject>`, "brag about this", "make a showcase page for X", "write up what I just did".

Take a GitHub issue and actually resolve it end to end — read the issue, reproduce it, fix it in an isolated branch with a test, verify, and open a PR that closes the issue. The counterpart to /idea (which files issues): /idea captures, /fix-issue clears. Works off `gh` in whatever repo you're in. Triggers on `/fix-issue <number|url>`, "fix issue #N", "resolve this github issue", "pick up and fix issue N".

Get a second-opinion review of the current diff (or a chosen focus — architecture, security, docs, design, performance, tests) from the Gemini CLI, then present its findings alongside your own analysis. Single-reviewer counterpart to /codex-review and /review-panel; needs the `gemini` CLI installed. Triggers on `/gemini-review [focus]`, "gemini review this", "get a gemini second opinion on this diff".

Wrap up a coding session — run a right-sized end-of-session self-critique, optionally curator-verify the claims, prepend a SESSION_LOG.md entry, and print a rename + counter summary. Use before you /clear or stop for the day. Triggers on `/session-end`, "end this session", "wrap up and log what we did".

Use when the user invokes /sitrep — an occasional "state of the union" re-orientation sweep. Verifies what has actually shipped versus what handoffs, specs, memory, and chat history claim shipped (across git in one or more repos, handoff docs, specs, optional chat-history/memory MCPs, and open issues), surfaces loose ends and loss-risk (unpushed commits, stale/stray worktrees & branches, unchecked plan boxes, never-closed handoff pending sections), then resets what matters next as a milestone-anchored list plus a bounded off-roadmap-drift section. Writes a report to docs/digests/ and proposes (never applies) a roadmap diff. Triggers on /sitrep, "state of play", "what's actually shipped", "what did I leave hanging", "re-orient me on this project".

Turn a rough brief into a blog deep-dive draft. Takes a topic or brief, gathers the relevant sources, runs one short focused interview to pin down the angle and the claims, then writes a draft to docs/posts/<date>-<slug>.md. The default output is a rich outline — a dense, factual skeleton meant to be rewritten in your own voice — not finished prose. Pass `--draft` for full prose, `--outline` to force the outline. This is the no-BS technical counterpart to `/brag` (which builds a sales/hype showcase page); reach for write-post when the goal is an accurate deep dive. Triggers on `/write-post <topic>`, "write a blog post about", "draft a deep dive on", "help me write a post on".

Create an isolated git worktree for a task and log it to a shared work journal, so multiple Claude Code sessions run in parallel without racing on HEAD, uncommitted edits, or the index. Subcommands: `list`, `done <slug>`, `update` (heartbeat), `coord <message>` / `coord clear <slug>` (cross-session constraints). Triggers on `/branch`, "start in a worktree", "isolate this work", "parallel session", "heartbeat the journal".

Tear down a third-party product/tool/library from a single URL and answer two questions: (1) is the product worth adopting as-is — installed into your Claude Code workflow (a CLI, MCP server, skill, or dotfile) or otherwise kept around — and (2) are there features or code worth lifting into your current repo. Most evaluations are hunting for one of those two wins. It resolves the URL to its source (repo, README, launch post — with Reddit and paywalled-fetch fallbacks), characterizes the product from its docs, clones the code locally when it's open source, then fans out read-only subagents — each handed a subset of the codebase plus your repo's context — to find liftable features with file:line evidence and portability notes. The calling session merges the findings into a verdict (adopt / lift / partial / skip) with per-finding analysis and writes a report to docs/evaluations/. Use for "is this repo worth anything to me?", "should I start using this", competitive teardowns, "should we adopt X", "evaluate this

Use when asked about Claude Code workflow, prompt caching cost, session economics, CLAUDE.md hygiene, context-window management, plan mode, permission modes, hooks, skills, subagents, checkpointing/rewind, parallel sessions, worktrees, headless/CI usage, the Agent SDK, slash commands, MCP configuration, or "what's the right way to use Claude Code for X". Also use proactively BEFORE suggesting /model, /compact, fast-mode toggle, or editing CLAUDE.md mid-session, since those bust the system cache.

Capture a fix / feature / research idea fast and turn it into a tracked GitHub Issue plus a lightweight planning doc, so nothing gets lost and it shows up next time you list your issues. Runs a short confirm-or-edit interview (infers title/slug/type from your one-liner, you accept or correct), writes docs/ideas/<date>-<slug>.md, files a labelled GitHub Issue via gh, and backlinks the issue URL into the doc. Triggers on `/idea <one-liner>`, `/idea`, "capture this idea", "file an idea", "log a thing to fix/build/research", "remember to look into X".

Use when the user wants to pick up / resume the most recent handoff in an isolated worktree — finds the newest handoff doc, RESUMES the worktree/branch it documents if one exists (re-adding it if parked), otherwise creates a fresh branch + worktree, then loads the handoff's context so work continues where it left off. Triggers on `/pickup`, "pick up the handoff", "resume the latest handoff in a worktree", "branch and continue". Distinct from `session-resume` (loads a handoff in-place, never branches) and `branch` (makes a worktree, loads no handoff) — `/pickup` does both, reusing an existing worktree when one is documented.

Begin a documented coding session — create a per-session log so progress is tracked and later wrap-up (/session-end) has something to append to. Use at the start of a work session. Triggers on `/session-start`, "start a coding session", "begin a session".

Load a session handoff file and resume the work it describes. Use when the auto-resume hook doesn't apply — a new terminal, or an older handoff you want to pick up by hand.

Verify a session's or handoff's factual claims against ground truth before trusting them. Dispatches the read-only `curator` subagent to check claims against git, files, and read-only environment checks, plus the repo's invariants doc if any, and returns a confabulation report for human spot-check. Use at pass boundaries — resuming from a handoff, before a deploy, or whenever a prior session's summary looks suspiciously clean. Triggers on `/curate`, "curate this", "verify these claims", "check the handoff for confabulation", "is this actually done".

Monitors task execution for skill improvement opportunities. Use this skill during ANY multi-step task, agentic workflow, or substantive work session where Claude is using tools and producing deliverables. It captures patterns, user corrections, workflow insights, and methodology worth preserving as reusable skills. Also triggers during post-task feedback discussions and when the user explicitly mentions skill observations, improvements, the observation log, skill taxonomy, or asks Claude to watch for skill opportunities. Also known as "One Skill to Rule Them All" — trigger on this phrase too. IMPORTANT: this skill should be invoked at the start of every task-oriented session — if you are about to use tools to produce deliverables, invoke this skill first.

Detects and removes the visual patterns that make a website look AI-generated or "vibe-coded": the default shadcn/Tailwind look, AI-purple gradients, Inter/Geist fonts, unprompted neon glow, emoji used as icons, the centered hero + three feature cards + CTA layout, and more. Every rule is grounded in a 47-subreddit, 3.2M-post Reddit analysis of what people actually flag as "AI slop." Use this whenever building, designing, styling, reviewing, refactoring, or auditing any website, landing page, marketing page, web app UI, dashboard, or front-end component, and ESPECIALLY when the user wants a site to look custom, human, or professional rather than AI-generated, or mentions "AI slop," "looks AI-made," "generic," "vibe-coded," Tailwind, or shadcn. Trigger even if the user never says "vibe-coded" outright; if they are producing or cleaning up front-end UI and care how it looks, this skill applies.