Kits

Spacing, type, color, and layout rules that push Cursor toward interfaces a designer would keep. Scoped to UI files so it does not pollute backend work.

Voice and microcopy for product UI and marketing pages. Teaches the agent to write like a person who has used the thing.

Conventions for Next.js 16 App Router: params, metadata, data fetching, and the line between server and client.

A compact accessibility bar for every interface the agent touches: focus, labels, dialogs, and motion.

A user-level communication rule you can keep globally. Cuts the cheerleading and the telegraphic fragments.

Forces every list, search, and async view to ship an empty state, a loading state, and a recoverable error.

A short always-on rule so the agent never commits credentials, writes them into source, or treats a token pasted in chat as something to store.

A repeatable review: generic heroes, interchangeable cards, brochure copy, and weak empty states. Use it before you call a UI done.

A finishing workflow after the feature works. The agent should not invent new scope; it should make the existing UI feel considered.

How to name, describe, and structure a skill so Cursor picks it up for the right jobs and ignores it otherwise.

Structure, copy, and layout for a marketing page that states a job to be done. Built for Next.js and Tailwind.

A workflow for writing tasks, repos, and acceptance checks for Cursor cloud agents.

A small procedure for staging, splitting, and describing work so git history stays usable — including when Cursor made the edits.

Turn a SKILL.md into a Custom Mode so it stays in context for the session. Use when a playbook should last longer than one slash invoke.

Decide when a Cursor cloud agent should subscribe to events versus run once. Use for babysitting PRs, scheduled ingest, or waiting on Slack.

A defensive pass for a pull request: injection, broken auth, secrets, SSRF, unsafe deserialization. Complements Cursor’s Security Review bot; this file is what the agent in the editor should follow.

How to brief and run a Cursor Project: the coordinator stays on planning, shared context, and review. Use for a feature, a migration, or recurring work that should outlive one chat.

A short decision skill for where a cloud agent should execute. Cursor-hosted stays the default. Self-hosted is for code, builds, and secrets that must stay on your network.

How to brief a long Cursor session when Grok 4.7 is the model: hold the goal, verify your own work, do not turn the chat into x.ai news. Use for long coding or knowledge work inside Cursor — not for ChatGPT or Claude kits.

Paste this when you are starting from a blank repo. It forces a usable slice: one job, real copy, running UI.

Point the agent at a specific file or URL and ask for a redesign that still does the same job.

Use when the desktop view is fine and the mobile view is a squeezed dashboard.

A language-only pass for a page or component. No layout changes unless a line break is broken.

Paste with a diff or PR URL. Asks the agent to find breakage and slop, not to summarize the files.

Paste into a new Agent chat after /goal. Forces an objective with a stop condition, a playbook, and what not to expand into.

For a cloud agent on an open pull request. Uses Cursor’s PR subscription instead of you pasting logs.

Paste when you pick Start from scratch in the cloud agent repo picker. Forces a usable product before you save it to an Origin repo or publish to Vercel.

Paste into a Cursor Project. Keeps the coordinator on planning and shared context instead of writing the whole feature in one hop.

Paste with a diff before merge. Writes a monitoring plan a human (or Cursor Rollouts) can follow. Does not enable the Rollouts dashboard.

Install UI craft, product copy, App Router conventions, and a polish skill. This is the pack we would drop into a greenfield Next app on day one.

Pairs the skill-authoring workflow with communication rules so your own kits stay short and trigger correctly.

Pairs the landing-page skill with UI craft, product copy, and the first-slice prompt. Use when the next thing to exist is a page a stranger can understand.

Cloud agent playbook, Custom Mode, and subscriptions. Use when the next job is a long-lived agent, not a one-shot chat.

The files to put in front of the agent when the feature works and the remaining job is to ship it without a surprise. Complements Cursor’s Rollouts and Security Review bots; those stay in the product.

Use when the next job is a Cursor Project — a feature or migration that should keep memory — not a one-shot cloud agent.