glunty

AI tool cheat sheets / Guided paths / Ship a dev feature with Cursor

Ship a dev feature with Cursor

Cursor is only as good as the rules you give it. This path sets up conventions the agent will actually follow, scopes rules to the right files, and leans on a couple of glunty utilities to sanity-check what it writes.

You will make: A small feature shipped with Cursor that follows your conventions and passes a quick review.

  1. Cursor: set the conventions

    Add an AGENTS.md in the repo root describing your stack, conventions, and do-not-touch areas so the agent starts with context.

  2. Scope rules to files

    Put file-scoped rules in .cursor/rules/*.mdc with a globs field. A plain .md in the rules folder is ignored, so use .mdc.

  3. Set tone and precedence

    Use User Rules for tone, but note they do not apply to Cmd+K inline edits. Team Rules override when enforced: Team, then Project, then User.

  4. Verify the output

    Before you commit, run anything you do not fully understand through Code Explainer, and check tricky patterns with the Regex Tester.

Pass check: The feature follows your AGENTS.md conventions and you understand every line before committing.

Share your result

Finished something? Frame it in Beautify a Screenshot and shrink it with Compress Image before you post. It all runs in your browser.

Guides used in this path

Cursor tips, Code explainer, Regex tester.

Browse all AI tool cheat sheets or the copy-paste AI prompt library.

Embedded tool from glunty.com