Cursor rules examples

simstudioaiCursor rule

sim / rules

simstudioai/sim/.cursor/rules/sim-api-contracts.mdc

API contracts, route builders, boundary annotations, and the requestJson client boundary

No other project uses it yet

simstudioaiCursor rule

sim / rules

simstudioai/sim/.cursor/rules/sim-testing.mdc

Test layers, naming, and Vitest mechanics for Sim

No other project uses it yet

HumanSignalCursor rule

label-studio / rules

HumanSignal/label-studio/.cursor/rules/storage-provider.mdc

How to add a new storage or data connector for Label Studio

eyaltoledanoCursor rule

claude-task-master / rules

eyaltoledano/claude-task-master/.cursor/rules/git_workflow.mdc

Git workflow integrated with Task Master for feature development and collaboration

eyaltoledanoCursor rule

claude-task-master / rules

eyaltoledano/claude-task-master/.cursor/rules/new_features.mdc

Guidelines for integrating new features into the Task Master CLI

albumentations-teamCursor rule

albumentations / rules

albumentations-team/albumentations/.cursor/rules/coding-guidelines.mdc

under `tests/` - Follow existing test patterns and naming conventions - Use pytest fixtures when appropriate ## Code Review Guidelines Before submitting your PR: 1. Run all tests 2. Run pre-commit hooks

alibabaCursor rule

hooks / rules

alibaba/hooks/.cursor/rules/git.mdc

从保护分支（通常是 `master`）创建新的功能分支 2. 在新分支上进行开发 3. 提交 Pull Request 到目标分支 4. 等待 Code Review 和 CI 通过 5. 合并到目标分支 ## 分支命名规范 - 功能开发：`feat/description-of-feature` - 例如：`feat/add-dark-mode` - 例如：`feat/improve-table-performance` - 问题修复：`fix/issue-number-or-description` - 例如

No other project uses it yet

567-labsCursor rule

instructor / rules

567-labs/instructor/.cursor/rules/documentation-sync.mdc

when making code changes or adding documentation

No other project uses it yet

Chia-NetworkCursor rule

chia-blockchain / rules

Chia-Network/chia-blockchain/.cursor/rules/context-routing.mdc

Read Before You Grep Pre-built deep context exists in `.cursor/context/`. **Before running broad code searches** (semantic search, grep, glob) to understand how a subsystem works, read the matching context

No other project uses it yet

woocommerceCursor rule

woocommerce / rules

woocommerce/woocommerce/.cursor/rules/avoid-regex.mdc

This rule discourages the use of regular expressions in favor of more readable and maintainable alternatives.

No other project uses it yet

EvolutionAPICursor rule

evolution-api / rules

EvolutionAPI/evolution-api/.cursor/rules/core-development.mdc

Core development principles and standards for Evolution API development

mftsCursor rule

papermark / rules

mfts/papermark/.cursor/rules/no-excessive-comments.mdc

Keep comments and docstrings minimal and intentional

airweave-aiCursor rule

airweave / rules

airweave-ai/airweave/.cursor/rules/connector-development-end-to-end.mdc

Wait for human feedback. If tests fail, review the error logs and fix the code. --- ## Phase 4: Debugging & Iteration ### Common Issues #### Issue 1: Source connector runs but entities aren

apacheCursor rule

nifi / rules

apache/nifi/.cursor/rules/ending-conditions.mdc

Task completion checklist that must be verified before considering any task done

dmno-devCursor rule

varlock / rules

dmno-dev/varlock/.cursor/rules/env-graph-tests.mdc

expected behavior. ## Rationale - Ensures tests are easy to read, extend, and maintain. - Reduces code duplication and encourages consistent patterns across the codebase. - Makes it easier to add new test cases

No other project uses it yet

dmno-devCursor rule

varlock / rules

dmno-dev/varlock/.cursor/rules/root-decorator-tests.mdc

across all root decorator tests. - Makes it easy to add new cases and reduces code duplication. - Matches the style used in PR #47 and root-decorators.test.ts. ## Requirements - Each root decorator test

No other project uses it yet

usesendCursor rule

useSend / rules

usesend/useSend/.cursor/rules/polylane.mdc

Investigating production with Polylane

No other project uses it yet

VRSENCursor rule

agency-swarm / rules

VRSEN/agency-swarm/.cursor/rules/writing-docs.mdc

file. 4. Ask the user to review the changes and provide feedback. ## Writing New Pages 1. Analyze the information or the relevant code provided by the user. - If critical information

No other project uses it yet

prestCursor rule

prest / rules

prest/prest/.cursor/rules/agentic-loop.mdc

pREST agentic develop→validate loop — follow on every coding task

No other project uses it yet

prestCursor rule

prest / rules

prest/prest/.cursor/rules/planning-and-delegation.mdc

Plan every task first, parallelise independent work, and staff each task with the cheapest model that can do it well

No other project uses it yet