novu / rules
novuhq/novu/.cursor/rules/api-property-optionality-hygiene.mdc
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits
No other project uses it yet
The rules real projects give Cursor's agent, from .cursor/rules.
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.
novuhq/novu/.cursor/rules/api-property-optionality-hygiene.mdc
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits
No other project uses it yet
novuhq/novu/.cursor/rules/pullrequest.mdc
When creating a new pull request on GitHub, use this to specify the contents
No other project uses it yet
novuhq/novu/.cursor/rules/worker.mdc
Rules for working in the Worker service (background job processing)
No other project uses it yet
CopilotKit/CopilotKit/.cursor/rules/agent-development.mdc
simple agent template 2. Define clear actions and interfaces 3. Handle errors gracefully 4. Test with the corresponding UI example 5. Use shared utilities from [examples/shared/](mdc:examples/shared/) 6. Follow
Steady3 mentions in 2 weeks
No other project uses it yet
CopilotKit/CopilotKit/.cursor/rules/copilotkit-architecture.mdc
references - [package.json](mdc:package.json) contains workspace configuration - Scripts in [scripts/](mdc:scripts/) for development, testing, and releases
Steady3 mentions in 2 weeks
No other project uses it yet
CopilotKit/CopilotKit/.cursor/rules/development-workflow.mdc
Development Scripts - **[develop/](mdc:scripts/develop)** - Development environment setup - **[qa/](mdc:scripts/qa)** - Quality assurance and testing scripts - **[release/](mdc:scripts/release)** - Release automation scripts ### Documentation Scripts - **[docs/](mdc:scripts/docs)** - Documentation generation
Steady3 mentions in 2 weeks
No other project uses it yet
CopilotKit/CopilotKit/.cursor/rules/frontend-development.mdc
component registry for reusable components 3. Implement responsive design 4. Provide clear user feedback ### Testing and Quality 1. Test components with different agent configurations 2. Use the E2E testing setup
Steady3 mentions in 2 weeks
No other project uses it yet
CopilotKit/CopilotKit/.cursor/rules/quick-reference.mdc
scripts in [scripts/](mdc:scripts) - Check [utilities/](mdc:utilities) for shared configurations ### Run Tests - Use [examples/e2e/](mdc:examples/e2e) for end-to-end testing - Check [playwright.config.ts](mdc:examples/e2e/playwright.config.ts) for configuration ### Build
Steady3 mentions in 2 weeks
No other project uses it yet
CopilotKit/CopilotKit/.cursor/rules/suggestions-development.mdc
When working with suggesitons, always load this up.
Steady3 mentions in 2 weeks
No other project uses it yet
jdx/mise/.cursor/rules/conventional_commits.mdc
how to write commit and PR titles
No other project uses it yet
jdx/mise/.cursor/rules/development.mdc
cargo build --all-features` - build the project - `target/debug/mise` - run the built binary - `mise run test:e2e [test_filename]...` - run e2e tests - `mise run test:unit` - run unit tests - `mise
No other project uses it yet
surrealdb/surrealdb/.cursor/rules/bug-investigation.mdc
Read the issue description completely and think about the submitted issue - Check existing language tests in `language-tests/tests/` that relate to the reported functionality - If related to or referencing
No other project uses it yet
surrealdb/surrealdb/.cursor/rules/pull-requests.mdc
solves the problem. Be specific about the approach taken. ### What is your testing strategy? If there is a specific testing strategy, and new tests are added, describe the changes. Otherwise
Steady2 mentions in 2 weeks
No other project uses it yet
surrealdb/surrealdb/.cursor/rules/rust-code-quality.mdc
unwrap_or_default()` or similar coding conventions when debugging - it masks errors ## 5. Testing and linting - Run `cargo make fmt` to format all of the code before submitting changes
Steady2 mentions in 2 weeks
No other project uses it yet
ankitects/anki/.cursor/rules/building.md
folder (or check.bat on Windows) - This will format files, then run lints and unit tests
No other project uses it yet
simstudioai/sim/.cursor/rules/landing-seo-geo.mdc
SEO and GEO guidelines for the landing page
Steady47 mentions in 2 weeks
No other project uses it yet
simstudioai/sim/.cursor/rules/sim-api-contracts.mdc
API contracts, route builders, boundary annotations, and the requestJson client boundary
Steady47 mentions in 2 weeks
No other project uses it yet
simstudioai/sim/.cursor/rules/sim-caching.mdc
In-process caching with lru-cache and a ceiling, never hand-rolled TTL maps
Steady47 mentions in 2 weeks
No other project uses it yet
simstudioai/sim/.cursor/rules/sim-list-ordering.mdc
List and menu ordering that mirrors the toolbar or settings nav, encoded once, with one separator before the destructive action
Steady47 mentions in 2 weeks
No other project uses it yet
simstudioai/sim/.cursor/rules/sim-sandbox.mdc
Isolated-vm sandbox worker security policy. Hard rules for anything that lives in the worker child process that runs user code.
Steady47 mentions in 2 weeks
No other project uses it yet
Instruction files for Cursor's agent, kept in .cursor/rules/ as .mdc files.
A rule can apply only to files matching a pattern, or only when the agent asks for it. AGENTS.md always applies.
Copy the .mdc file into your project's .cursor/rules/ directory and adjust its globs.
Open a rule to see its discussion. Reports from people and their agents are coming.