Cursor rule Cursor
Interactive idea refinement using Socratic method to develop fully-formed designs.
Cursor rule Cursor
Interactive idea refinement using Socratic method to develop fully-formed designs.
Cursor rule Cursor
Replace arbitrary timeouts with condition polling for reliable async tests.
Cursor rule Cursor
Validate at every layer data passes through to make bugs impossible.
Cursor rule Cursor
Guidelines for generating concise, well-structured GitHub PR descriptions with clear issue tracking, solution summaries, and testing instructions. Use fixed emoji section headings (Issue, Solution, To Test, and Screenshots when the change is user-facing UI). Write To Test steps for non-dev QA: plain language…
Cursor rule Cursor
Recognize when disagreements reveal valuable context, preserve multiple valid approaches instead of forcing premature resolution.
Cursor rule Cursor
Systematically trace bugs backward through call stack to find original trigger.
Cursor rule Cursor
Defines principles and structure for generating technical specification documents appropriate for principal-level developers who value clarity, testing, and following established patterns over custom solutions.
Cursor rule Cursor
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
Cursor rule Cursor
Write the test first, watch it fail, write minimal code to pass.
Cursor rule Cursor
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking. Avoid unreachable assertions and dead branches in tests that confuse coverage.
Cursor rule Cursor
Run verification commands and confirm output before claiming success.
Cursor rule Cursor
Write clear, concrete prose; avoid AI fingerprints and prefab phrasing. Sources: Orwell (Politics and the English Language), tropes.fyi.
Cursor rule Cursor
Five-step TDD flow for Linear issue plans - RED, GREEN, REVERT, REWRITE, REFACTOR. Use when creating a plan for a new Linear issue.
Cursor rule Cursor
Use actions for mutations and redirects (faster time to paint), loaders only for initial GET requests with minimal data. Actions run before loaders on POST requests.
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: