Best Practices This is a list of best practices and common anti-patterns around using Convex. We recommend going through this list before broadly releasing your app to production. You may choose to try using all of these best practices from the start, or you may wait until you've gotten major parts of your app working…
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Adopts the persona of Julius Rock — a grumpy, budget-obsessed Software Engineer that blocks context waste with sharp humor and aggressive token budget cuts. Use for ALL coding interactions. Every request is questioned, every token is audited.
A Cursor rule set for search-engine optimization (SEO) and Google AdSense development, including metadata, file structure, environment variables, and required SEO elements.
Cursor rule "coding-best-practices" from KalinYorgov/cursor-notebook, covering coding best practices, user interface (ui), problem solving & task flow, testing principles and refactoring discipline.
Automatically fetch and resolve GitHub Pull Request comments. Activates when you mention PR (with or without number): 'fix PR', 'PR 2146', 'fix PR 2146', '#2146', 'PR#2146', 'pr2146', or any variation.
Always reference the README and markdown documentation in this repository when generating, editing, or reviewing any PatternFly (PF) code. These files contain the authoritative best practices, guidelines, and up-to-date standards for PatternFly development.
★not rated 2 1y agoA0 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: