Cursor Project Rules Generator for Your Repo's Stack
Has Cursor inspect your repository and write 3-5 scoped .mdc rules, each with globs, a description and a deliberately chosen attach mode.
74 prompts
Prompts for coding agents and agent workflows, from Claude Code, Codex and Cursor to multi-agent pipelines. They read like task briefs: the goal, the scope, the tools allowed and the checks that prove the work is done.
8 results
Has Cursor inspect your repository and write 3-5 scoped .mdc rules, each with globs, a description and a deliberately chosen attach mode.
Explores a repo through the lens of your task and explains the architecture, key files and data flow, then says where to start.
A SKILL.md that makes Claude write and edit in your brand's voice: it reads a VOICE.md in the project, or builds one from samples, then checks every draft against it.
Has Codex inspect your repository and write a short, accurate AGENTS.md with the real build, test and lint commands, conventions and boundaries, checked by actually running them.
A ready-to-save SKILL.md that makes your coding agent write Conventional Commits messages and pull request descriptions from the staged diff, never from guesses.
A save-ready SKILL.md that has your coding agent review a branch before merge: correctness, security, tests and migrations, with findings ranked by severity and no style nitpicks.
A SKILL.md that writes release notes from the commits between two tags, split into a plain-language section for users and a technical changelog for developers.
A SKILL.md that forces your coding agent to reproduce a bug with a failing test before changing code, apply the smallest fix, and prove it with the test suite.
An agent acts: it reads files, runs commands and edits code. So the prompt sets limits and a way to verify the result, not only the answer you want.
Coding agents such as Claude Code, Codex, Cursor and Copilot's agent mode, plus prompts for designing your own multi-agent pipelines. Each prompt lists its tools.
Yes. Run agents in a branch or a sandbox, read the diff and the commands they ran, and keep approval on for anything that deletes data or deploys.