35 Cursor Slash Commands I Actually Use to Ship SaaS

If you retype a prompt twice, it is a command. If you retype it daily and it still drifts, it is a bad command.

This article is a field guide. The canonical directory for cursor commands is the Cursor slash commands pillar, which lists every / workflow with its pipeline steps and the skills it loads.

Cursor custom commands are markdown files in .cursor/commands/ (project) or ~/.cursor/commands/ (your machine). Type / in Agent and they show up. AgenticKit ships 35 of them. This is when to use each, when not to, and one example. It is not 35 essays. Skills vs commands is a separate comparison.

Cursor has also been moving some of this surface toward Skills (SKILL.md, /migrate-to-skills in recent versions). The idea is the same. A named, on-demand playbook. I will keep saying "command" because that is what you type.

The takeaway

Group commands by job. The hero is /ship. The discipline is knowing when not to use it.

• Build a slice
• Verify it
• Operate the repo
• Grow the product

Do not run a grow command inside an engineering-only kit and wonder why brand voice is empty. Do not run /ship on a stack trace.

How to read this

Each entry is: use when / do not use when / example. Details and pipeline steps live on the command pages.

Build (12)

/feature-spec

Use when the work is bigger than one file and you do not have acceptance criteria. Do not use when you already know the file and the change. Example: /feature-spec Team invites with owner-only access and email accept.

/ship

Use when you want plan through gate on a complexity S or M full-stack slice. Do not use for a bug, a page-only change, API-only work, or complexity L (split first). Example: /ship Invite teammate by email with org scoping. This is the pipeline in the workflow article.

/build-api

Use when the contract is clear and you need a route. Do not use when the schema does not exist yet and you also need UI. Example: /build-api POST /api/invites with owner check and Zod email.

/build-page

Use when the API exists and you need a view. Do not use to invent data access in a Client Component. Example: /build-page Settings team tab with pending invites and empty state.

/auth-system

Use when you are introducing login, sessions, or RBAC. Do not use to "quickly add a password field" on an existing NextAuth app. Example: /auth-system Google OAuth and owner/member roles on /dashboard.

/stripe-billing

Use when you need Checkout, Customer Portal, webhooks, and a tier field. Do not use for a one-off Payment Link you will handle by hand. Example: /stripe-billing Monthly Pro plan, portal, invoice.payment_failed.

/ai-feature

Use when the slice is an LLM call with streaming UI. Do not use to add a single fetch to OpenAI inside an existing route. Example: /ai-feature Support chatbot with streamed answers and citation list.

/rag-pipeline

Use when you must ingest documents and retrieve them. Do not use for a keyword search you can do with SQL. Example: /rag-pipeline Ingest docs/ and answer with source links.

/llm-chat

Use when you need a chat endpoint and UI, not a full RAG system. Do not use if /ai-feature or /rag-pipeline already covers it. Example: /llm-chat Authenticated /api/chat with token cap per user.

/realtime-feature

Use when the product needs sockets or live presence. Do not use for polling every 30 seconds. Example: /realtime-feature Live doc presence and comment stream.

/mobile-screen

Use when the Expo app needs a screen that talks to the existing API. Do not use to start a Swift rewrite. Example: /mobile-screen Login and dashboard tabs sharing the web types.

/data-pipeline

Use when something must run on a schedule (ETL, nightly sync). Do not use for a one-time backfill script you will throw away. Example: /data-pipeline Sync Stripe events to analytics tables nightly.

Verify (6)

/fix

Use when you have a stack trace, a failing test, or a hydration error. Do not use to redesign the feature. Example: /fix Null session on /api/invites after Google callback.

/audit

Use before a release, or when you inherited a folder of routes. Do not use as a daily linter. Example: /audit API handlers and tenant filters.

/e2e-suite

Use when a path is user-money or user-auth and unit tests are not enough. Do not use to snapshot every page. Example: /e2e-suite Invite accept path as owner and as outsider.

/compliance-audit

Use when you have a real SOC2 / GDPR question and a human will read the output. Do not use to generate a badge for the marketing site. Example: /compliance-audit Retention and DPA notes for workspace exports.

/write-docs

Use when the behavior is stable and a human will maintain the doc. Do not use to document a spike. Example: /write-docs Invite API and owner permissions.

/release

Use when you are about to tag and you need a changelog from git. Do not use as a daily diary. Example: /release Changelog since v1.2.0.

Operate (5)

/ci-pipeline

Use when you need CI that runs the scripts in CURSOR.md. Do not use to invent a second test runner. Example: /ci-pipeline GitHub Actions for lint, test, build.

/dockerize

Use when you deploy a container. Do not use on a site that only exists on Vercel. Example: /dockerize API and worker with production env only.

/cloud-infra

Use when you need a first cut of cloud resources and you will review the plan. Do not use as unattended production apply. Example: /cloud-infra Staging VPC and managed Postgres.

/ml-finetune

Use when you actually have a fine-tune job and a dataset. Do not use because "AI" is in the pitch. Example: /ml-finetune Classifier for inbound support tags.

/sre-incident

Use when something is down or burning error budget. Do not use for a typo on the pricing page. Example: /sre-incident 500s on /api/invites since 14:10 UTC.

Grow (12)

These write under docs/marketing/ (or page files for /seo-fix). They assume the marketing kit and a filled brand section.

/positioning

Use once, when you cannot say who the product is for. Do not use every time you tweak a headline. Example: /positioning Cursor kit for solo founders who already write TypeScript.

/define-brand-voice

Use once, then edit by hand. Do not regenerate it because you did not like one sentence. Example: /define-brand-voice Direct, specific, no 'revolutionary'.

/landing-page

Use when the page does not exist yet. Do not use to dodge reading your own homepage. Example: /landing-page Hero, three benefits, pricing table for the engineering kit.

/landing-fix

Use when the page exists and conversion is the question. Do not use as a first draft. Example: /landing-fix Hero and CTA on /.

/seo-audit

Use to get a report. Do not use expecting files to change. Example: /seo-audit /pricing and /docs.

/seo-fix

Use after /seo-audit, when you are ready to change tags and JSON-LD. Do not use to stuff keywords. Example: /seo-fix Title, description, SoftwareApplication schema on /.

/blog-post

Use when you have a real reader problem and sources. Do not use to mass-produce 30 posts. This series is the opposite of that command used badly.

/email-sequence

Use when signup exists and you will actually send the mail. Do not use as fictional onboarding. Example: /email-sequence 5-day activate-the-first-slash-command.

/linkedin-post

Use for one founder note with a real lesson. Do not use as a daily content mill. Example: /linkedin-post What broke when one chat did billing and launch copy.

/reddit-reply

Use to answer a specific thread helpfully. Do not use to spray the product. Check the subreddit rules first. Example: /reddit-reply r/cursor thread about rules being ignored.

/competitive-analysis

Use when you need a battlecard you will maintain. Do not use to obsess over a competitor's changelog. Example: /competitive-analysis Kits vs a blank .cursorrules file.

/launch

Use when the date is on the calendar. Do not use two months early as a substitute for product. Example: /launch Product Hunt, Show HN, and X thread for the engineering kit.

A week mapped to commands

Mistakes

• /ship on L complexity. You will get a tour of the repo and a half feature.
• Marketing commands in an engineering-only install. The playbooks are not there.
• Two commands that mean the same thing in your own folder (/review and /audit). Pick one.
• A command that is just "be careful." That is a rule, not a command.
• Running /launch from the same chat that just wrote SQL. New chat. Different kit.

If you want to start from a blank file, the Slash Prompt Builder will give you a legal markdown command. Add three you already type every week. Do not invent 35. The agent article is who those 35 call. The solo founder OS is how they sit in a week.