agentleFS
waynesuttonwaynesutton/markdown-site/.cursor/rules/rulesforconvex.mdc

markdown-site / rules

Cursor rule628 starsChanged 7 months agoMITView on GitHub

description: Convex guidelines globs: alwaysApply: true - always follow Convex schemas best practices - https://docs.convex.dev/database/schemas - check the convex schema for updates and errors - always understand Convex - https://docs.convex.dev/understanding/ - understand environment-variables https://docs.convex.dev/production/environment-variables - always follow and understand and follow Convex best-practices https://docs.convex.dev/understanding/best-practices/ - Follow best practices https://docs.convex.dev/understanding/best-practices/typescript - Always use query-functions https://docs.convex.dev/functions/query-functions - Always usehttps://docs.convex.dev/functions/mutation-functions - expert https://docs.convex.dev/functions/mutation-functions - Always use https://docs.convex.dev/functions/actions - knows https://docs.convex.dev/functions/validation - knows https://docs.convex.dev/functions - Expert in Clerk https://docs.clerk.com/ - you are an expert…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this rulesforconvex.mdc into the rules it gives an agent

11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    always follow Convex schemas best practices - https://docs.convex.dev/database/schemas

    line 17
  2. Distinctive:

    check the convex schema for updates and errors

    line 18
  3. Distinctive:

    always understand Convex - https://docs.convex.dev/understanding/

    line 19
  4. Distinctive:

    always follow and understand and follow Convex best-practices https://docs.convex.dev/understanding/best-practices/

    line 21
  5. Distinctive:

    Follow best practices https://docs.convex.dev/understanding/best-practices/typescript

    line 22
  6. Distinctive:

    Always use query-functions https://docs.convex.dev/functions/query-functions

    line 23
  7. Distinctive:

    Always usehttps://docs.convex.dev/functions/mutation-functions

    line 24
  8. Distinctive:

    Always use https://docs.convex.dev/functions/actions

    line 26
  9. Distinctive:

    do not use emoji in the readme or app

    line 41
  10. Distinctive:

    do not over engineer the code but make it type-safe

    line 42
  11. Distinctive:

    do not do more than what the user ask for unless it related to fixing, adding, or updating the code to what the user is asking for

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
rulesforconvex.mdc
---
description:
globs:
alwaysApply: true
---

---

description: Convex guidelines
globs:
alwaysApply: true

---

## Function guidelines

- always follow Convex schemas best practices - https://docs.convex.dev/database/schemas
- check the convex schema for updates and errors
- always understand Convex - https://docs.convex.dev/understanding/
- understand environment-variables https://docs.convex.dev/production/environment-variables
- always follow and understand and follow Convex best-practices https://docs.convex.dev/understanding/best-practices/
- Follow best practices https://docs.convex.dev/understanding/best-practices/typescript
- Always use query-functions https://docs.convex.dev/functions/query-functions
- Always usehttps://docs.convex.dev/functions/mutation-functions
- expert https://docs.convex.dev/functions/mutation-functions
- Always use https://docs.convex.dev/functions/actions
- knows https://docs.convex.dev/functions/validation
- knows https://docs.convex.dev/functions
- Expert in Clerk https://docs.clerk.com/
- you are an expert in setting up apps with Resend for email https://resend.com/docs/introduction
- you are an expert in using Resend API for email https://resend.com/docs/api-reference/introduction
- you know all things about Resend email https://resend.com/docs/knowledge-base/introduction
- expert in convex auth https://docs.convex.dev/auth/convex-auth
- convex auth docs https://labs.convex.dev/auth
- For all designs I ask you to make, have them be beautiful, not cookie cutter. Make webpages that are fully featured and worthy for production.
- you are an expert in understanding how Uploading and Storing Files with convex https://docs.convex.dev/file-storage/upload-files
- you are an expert in convex auth - https://docs.convex.dev/auth/convex-auth
- you are an expert in setting up convex auth https://labs.convex.dev/auth/setup
- you an an expert in convex vector search https://docs.convex.dev/search/vector-search
  getting-started
- do not use emoji in the readme or app
- do not over engineer the code but make it type-safe
- do not do more than what the user ask for unless it related to fixing, adding, or updating the code to what the user is asking for

waynesutton@WS-Convex merge2 %

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.