Awesome Rules

This collection focuses on rules written in standard markdown format with YAML frontmatter, compatible with various AI coding assistants like Cursor, Continue.dev, and others following the amplified.dev standard.

Why Rules?

Rules are more than just suggestions; they’re essential building blocks that shape how your assistant interprets your requests. Clear, actionable rules help the agent consistently produce code that meets your standards, avoids common pitfalls, and aligns with your team’s workflows.

Read the Anatomy of Good Rules

Rules

General

• Agent Enablement
• Coding Standards
• Error Handling
• Performance
• Security
• Task Management

Language Specific

• Erlang
• Go
• Lua
• Python
• Ruby
• Rust
• TypeScript
• Zig

Framework Specific

• Express
• FastAPI
• Next.js
• React
• Supabase
• LanceDB
• tailwind
• trpc
• Vue.js
• Zuplo

Code Quality

• Clean Code
• ESLint Configuration
• Prettier Formatting
• Type Safety Guidelines
• Code Review Standards
• Refactoring Patterns

Documentation

• API Documentation
• Changelog
• Code Comments
• Post-mortems
• README Standards

Testing

• Jest Testing
• Unit Testing Guidelines
• Integration Testing
• End-to-End Testing
• Test Data Management
• TDD Guidelines
• Cypress Testing
• React Testing Library
• Recurse ML

DevOps

• CI/CD
• Docker
• Monitoring
• Terraform

Using Rules Locally

rules CLI

The rules CLI helps you fetch and manage rules locally, across any AI coding assistant.

Install rules

The rules CLI can be installed using NPM:

npm i -g rules-cli

Adding Rules to Your Project

To download rules to your repository you can use rules add. For example:

rules add starter/nextjs-rules

This will add them to your project in a local .rules folder.

You can also download from GitHub rather than the rules registry:

rules add gh:continuedev/rules

From there you can use rules render to translate into the format of your choice:

For Cursor:

rules render cursor

will create the following folder structure:

your-project/
├── .cursor/
    └── rules/
        ├── coding-standards.mdc
        ├── testing-guidelines.mdc
        └── documentation-rules.mdc

For Continue:

rules render continue

will create the following folder structure:

your-project/
├── .continue/
│   └── rules/
│       ├── coding-standards.md
│       ├── testing-guidelines.md
│       └── documentation-rules.md

For other AI assistants: See the docs for the full list of supported formats.

Contributing

We welcome contributions, especially if you have great rules to share.

1. Fork this repository
2. Create your rule in the rules folder. The folder name should follow this pattern: technology-focus-description For example: typescript-type-standards-practices
3. Update the main README.md file, adding your contribution to the appropriate category.
4. Ensure your contribution follows the guidelines in the CONTRIBUTING.md file in the .continue/rules file at the root of this repository.
5. Submit a pull request with a description, PRs with no description or clear title will be marked as spam and closed.

Please refer to the CONTRIBUTING.md file in the .continue/rules for details on how to submit rules, report issues, and contribute to the project.

License

This project is licensed under CC0 1.0 Universal - see the LICENSE file for details.

Acknowledgments

• amplified.dev, the coding manifesto that inspired this repo
• PatrickJS/awesome-cursorrules was an inspiration for the structure of this repo
• All contributors who help make this list awesome

---

Note: This is a community-maintained collection of rules. To read and sign the amplified.dev pledge, visit amplified.dev.