A tool that creates Cursor rules from your real project stack
Payo is a tool that asks about a project and then creates rule files for Cursor. Cursor can make its own guesses about data handling, file locations, and naming rules when those details are not written down. `` and `.cursor/rules/**` can reduce those guesses, but keeping them updated by hand is easy to neglect.
Payo turns a one-time questionnaire into rules that match the project’s conventions, so Cursor can follow them from the . It can be run with `npx @uge/payo` or `bunx @uge/payo`. The same questionnaire can also produce matching setup files for Claude, Copilot, Codex, Windsurf, and .
It covers TypeScript and , Python, Go, and Rust, with support for 25 , 24 , and 4 databases.
Key points
- Payo creates Cursor rule files from answers about the actual project.
- The goal is to stop Cursor from guessing file structure, naming, and data handling rules.
- It can be run with `npx @uge/payo` or `bunx @uge/payo`.
- It can also output similar setup files for Claude, Copilot, Codex, Windsurf, and .
- It supports TypeScript and , Python, Go, Rust, plus many , , and databases.