AI Integrations for Development

As of version 2025.4, Pegasus includes tooling for integrating with AI-powered coding assistants and tools. These will be constantly edited, expanded on, and improved as the community is able to provide more feedback on them.

Video overview

See below for a demo of how you can use these tools to help you with development.

Rules Files

Pegasus ships with a set of rules files that are designed to be used with coding assistants. These rules are broken out into various sections—e.g. architecture, general guidelines, and guidelines for specific programming languages and frameworks. The rules have been custom developed for Pegasus applications and contain best-practices and information for building on Pegasus.

When the tool supports it (e.g. in Cursor), these rules files will be organized and labeled in ways that allow for them to be automatically included in the appropriate contexts.

You can edit your rules freely after downloading your project. They are provided as a quick way to get started.

MCP

Pegasus also includes a default MCP setup containing two tools, a database inspector (Postgres builds only), and a web browser. You can use these tools to give your AI assistants access to your database + schema and let them work directly with your application in a browser.

See the demo video above for more detail.

Working with Cursor

Cursor is an AI code editor (IDE). If you enable the Cursor integration, your rules files will be saved to the /.cursor/rules/ directory and will be labeled to be automatically included based on the context. For example, the Python coding guidelines will be included anytime you’re editing a .py file.

The MCP setup for Cursor will be saved to .cursor/mcp.json, and should be discoverable by Cursor there.

You can modify the rules files and MCP set up in your Cursor settings or by editing the files by hand.

Working with Claude Code

Claude Code is a command-line coding assistant built by Anthropic. If you enable the Claude code integration, your rules will be collapsed into a single, organized CLAUDE.md file for Claude to use.

Additionally, the MCP setup will be saved to .mcp.json and should be automatically discovered by claude.

Other tools

If you’re using a different tool, it is recommended to choose one of the two above when building your project and then copy the files to wherever your tool expects them. Choose “Cursor” if you want the rules files split up, and “Claude” if you prefer a single rules file.

Also, if you’d like support or help configuring a different tool, email support@saaspegasus.com and let me know!