What is the best Cursor command?

/ship if you are implementing a slice. /fix if something is on fire. /positioning if you cannot say who it is for.

Where should Google send “cursor commands”?

The /commands pillar, not a five-minute features post.

← All comparisons

Best Cursor slash commands

The hero is /ship. The discipline is knowing when not to run it. These are the commands that survive a real week.

Build

/ship: full-stack slice. Not for bugs.
/build-api: routes only.
/build-page: UI only.
/feature-spec: before anything M or L.

Verify

/fix: stack traces.
/audit: before a release.
/seo-audit: titles, H1, schema.

Grow

/positioning: already appearing in search for us; protect it.
/launch: PH / HN / X timeline.
/blog-post: cluster articles, not filler.
/seo-fix: after the audit, not instead of it.

A week mapped to slashes

Monday: /feature-spec. Tuesday–Wednesday: /ship or the narrower build command. Thursday: /audit. Friday: /landing-fix or /launch. The longer version is the field guide.

Where “cursor commands” should rank

The commands pillar is the URL that should win that query. A five-minute features post is a satellite, not the hub. If you landed here from a feature list, go to the directory next.

Frequently asked questions

What is the best Cursor command?
/ship if you are implementing a slice. /fix if something is on fire. /positioning if you cannot say who it is for.
Where should Google send “cursor commands”?
The /commands pillar, not a five-minute features post.

See all 47 commands

Each page has the example prompt, pipeline, and the skills it loads.

Cursor Commands directory →Pricing