cursor/plugins

---

name: advisor

description: Advisor mode. Consult a stronger (or different) model at key checkpoints: before major decisions, when stuck on an error, and before declaring a task done. Use when the user types /advisor, asks to turn the advisor on or off, picks an advisor model, or explicitly asks for a second opinion from a stronger or different model. Never enable it on your own.

---

name: check-agent-compatibility

---

name: cli-for-agents

description: Designs or reviews CLIs so coding agents can run them reliably: non-interactive flags, layered --help with examples, stdin/pipelines, fast actionable errors, idempotency, dry-run, and predictable structure. Use when building a CLI, adding commands, writing --help, or when the user mentions agents, terminals, or automation-friendly CLIs.

---

name: continual-learning

description: Orchestrate continual learning by delegating transcript mining and AGENTS.md updates to `agents-memory-updater`.

---

name: create-plugin-scaffold

description: Create a new Cursor plugin scaffold with a valid manifest, component directories, and marketplace wiring. Use when starting a new plugin or adding a plugin to a multi-plugin repository.

---

name: review-plugin-submission

description: Audit a Cursor plugin for marketplace readiness. Use when validating manifests, component metadata, discovery paths, and submission quality before publishing.

---

name: cursor-sdk

description: Guide users building apps, scripts, CI pipelines, or automations on top of the Cursor TypeScript SDK (`@cursor/sdk`). Use this skill whenever the user mentions integrating, installing, or writing code against the Cursor SDK; whenever they say `Agent.create`, `Agent.prompt`, `Agent.resume`, `agent.send`, `run.stream`, `CursorAgentError`, or `@cursor/sdk`; whenever they ask to run Cursor agents programmatically from a script, CI/CD pipeline, GitHub Action, backend service, or any other code that isn't the Cursor IDE itself; and whenever they want to pick between local and cloud runtime, configure MCP servers for an SDK agent, or handle streaming, cancellation, or errors from an SDK agent. Also trigger when a user is wiring Cursor into an automation, writing a bot that runs Cursor, or porting REST `/v1/agents` calls to the SDK, even if they don't explicitly name the package. Use this eagerly rather than answering from memory; the SDK surface evolves and this skill plus its references are the source of truth for the external package.

---

name: check-compiler-errors

description: Run compile and type-check commands and report failures

---

name: control-cli

description: Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services. Use for CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos.

---

name: control-ui

description: Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI. Use for local UI verification, screenshots, accessibility snapshots, perf profiles, visual diffs, or reproducing UI bugs.

---

name: deslop

description: Remove AI-generated code slop and clean up code style

---

name: fix-ci

description: Find failing PR checks, inspect logs or external check links, and apply focused fixes

---

name: fix-merge-conflicts

description: Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution

---

name: get-pr-comments

description: Fetch and summarize review comments from the active pull request

---

name: loop-on-ci

description: Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.

---

name: make-pr-easy-to-review

description: Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".

---

name: new-branch-and-pr

description: Create a fresh branch, complete work, and open a pull request

---

name: pr-review-canvas

description: Generate an interactive PR review walkthrough as an HTML page. Fetches PR data via gh API, categorizes files into core vs mechanical changes, adds reviewer annotations, and renders diffs with moved-code detection. Use when the user pastes a GitHub PR URL and asks for a review, walkthrough, or summary, or says "review this PR".

---

name: review-and-ship

description: Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.

---

name: run-smoke-tests

description: Run Playwright smoke tests, debug failures, and verify fixes

---

name: thermo-nuclear-code-quality-review

description: Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.

---

name: verify-this

description: Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.

---

name: weekly-review

description: Produce a weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work

---

name: what-did-i-get-done

description: Summarize authored commits over a user-specified time period into a concise update

---

name: workflow-from-chats

description: Extract durable working preferences from recent Cursor chats and convert them into skills, rules, or workflow docs. Use when asked to learn preferences, mine feedback, personalize workflows, or generate team/person-specific agent guidance.

---

name: docs-canvas

description: Render a documentation-style Cursor Canvas that organizes architecture notes, API references, walkthroughs, and how-tos into a navigable layout with sections, tables of contents, and cross-references. Use when the user asks for a docs canvas, documentation overview, architecture walkthrough, API reference page, or wants to render structured documentation as an interactive canvas.

---

name: build-figma

description: Use for "/build-figma", a figma.com/design URL with node-id, or "implement this Figma" into a web, desktop, or shared UI. Orchestrates Figma MCP intake, maps nodes to the repo's own design system, then a verify-this visual judge. Do not paste Figma Tailwind.

---

name: dyl-mode

description: Dylan's agent style on top of pstack: concise verified delivery, root causes over symptom patches, The Algorithm before design, plain /bro replies, live UI proof, reuse/simplify, and hard merge gates. Use for Dylan, /dyl-mode, or his style. "Get PR green" → /dyl-ready-pr. "Review this PR like me" → /dyl-review. Figma URL → /build-figma.

---

name: dyl-ready-pr

description: Get a PR merge-ready for Dylan: deep /dyl-review till 🟢, mark it ready, resolve conflicts, then babysit CI and comments. Use for /dyl-ready-pr, "get PR green", "make the PR mergeable", "/dyl-review till green then ready", or ready-to-merge asks under /dyl-mode.

---

name: dyl-review

description: Review one or more PRs in Dylan's style: up to 7 copy-pasteable asks and one 🟢/🟡/🔴 call. Quick by default; "deep" adds thermos and Bugbot. Use for /dyl-review, "review this PR like me", or terse design/correctness comments. Never posts to the PR.