The rules real projects give Cursor's agent, from .cursor/rules.
mondaycomCursor rulemondaycom/vibe/.cursor/rules/playground-reproduce.mdc
Use when creating interactive examples for Vibe's Storybook Playground (vibe.monday.com/playground) - including bug reproductions, component demonstrations, feasibility testing, or consumer examples. Triggered by keywords like "playground", "reproduce bug", "interactive example", "user reported an issue" or "demonstrate".
mondaycomCursor rulemondaycom/vibe/.cursor/rules/storybook-stories.mdc
Guides the creation and modification of Storybook files specifically within the 'packages/docs' package. It covers conventions, best practices, and helps answer questions about existing story implementations within 'packages/core'.
mondaycomCursor rulemondaycom/vibe/.cursor/rules/styling-conventions.mdc
Provides comprehensive guidelines for writing CSS Modules specifically for UI components within the `@vibe/core` library (under `packages/core/src/components/`). This rule covers file naming conventions (e.g., `ComponentName.module.scss`), CSS nesting, mandatory browser compatibility, strategies for adopting newer CSS APIs with fallbacks, the exclusive use of design tokens from `@vibe/style` (via CSS custom properties like `var(--primary-text-color)`), discouraging mixin usage from `@vibe/style`, typography best practices (using `Text`/`Heading` components instead of direct font tokens), `camelCase` class naming, and common anti-patterns like avoiding theme-specific styles directly in component SCSS, never using `:global`, and never using `!important`. Activate this rule when working with `.module.scss` files in `packages/core/src/components/` or when styling Vibe core components.
truffle-aiCursor ruletruffle-ai/dexto/.cursor/rules/service_initializer.mdc
Adding any new services/modules to the class
adalineCursor ruleadaline/gateway/.cursor/rules/gateway.mdc
properly defined and exported - [ ] Custom error classes extend `GatewayError` - [ ] All public methods have JSDoc documentation - [ ] Tests cover success and error scenarios - [ ] Code follows naming conventions - [ ] Imports are properly organized
adalineCursor ruleadaline/gateway/.cursor/rules/main.mdc
backoff for transient failures 5. **Security**: Sanitize inputs and implement proper access controls ### 7. Documentation #### Rules - **ALWAYS** include JSDoc comments for public APIs - **ALWAYS** update CHANGELOG.md for breaking changes - **ALWAYS
adalineCursor ruleadaline/gateway/.cursor/rules/provider.mdc
keys and endpoints - **ALWAYS** support environment variable overrides - **ALWAYS** include configuration examples in documentation ### 2. Configuration Types - **ALWAYS** use descriptive type names ending with `OptionsType` - **ALWAYS** extend base configuration interfaces
adalineCursor ruleadaline/gateway/.cursor/rules/providers.mdc
calls - **ALWAYS** implement rate limiting for user requests - **ALWAYS** monitor for suspicious activity patterns ## Documentation Rules ### 1. Code Documentation - **ALWAYS** include JSDoc comments for public methods - **ALWAYS** document configuration options
adalineCursor ruleadaline/gateway/.cursor/rules/types.mdc
assistant', 'system']), }); export const Message = MessageV2; // Current version export const MessageV1 = MessageV1; // Legacy version ``` ## Documentation Instructions ### 1. Schema Documentation ````typescript // ✅ CORRECT: Document schemas with examples /** * Chat response containing messages
giselles-aiCursor rulegiselles-ai/giselle/.cursor/rules/update-ai-sdk.mdc
Update ai-sdk(ai, @ai/*) to latest
giselles-aiCursor rulegiselles-ai/giselle/.cursor/rules/vercel-cli.mdc
Setup Vercel CLI
wataru-maedaCursor rulewataru-maeda/react-native-boilerplate/.cursor/rules/coding-guidelines.mdc
Quality - No `console.log` in production code - Always handle loading and error states - Write self-documenting code - Keep functions focused and small ### Reusability Focus - Always check existing components before creating
fdmtlCursor rulefdmtl/director/.cursor/rules/documentation.yml
Mintlify writing assistant guidelines
paladiniCursor rulepaladini/harness-score/.cursor/rules/core.mdc
Non-negotiable conventions for the harness-score monorepo
Sidiora-LabsCursor ruleSidiora-Labs/LayerX-Network/.cursor/rules/spec-workflow.mdc
Ion portable spec workflow (task-driven + cortex)
claude-office-skillsCursor ruleclaude-office-skills/skills/.cursor/rules/project-rules.mdc
Claude Office Skills project coding standards and conventions
hyperb1issCursor rulehyperb1iss/droidmind/.cursor/rules/001_workspace.mdc
DroidMind :: Control your Android devices with AI via Model Context Protocol
LangChainCursor rulelangchain-ai/docs/.cursor/rules/docs-style.mdc
LangChain docs prose style guide, applied when authoring or editing MDX pages
waynesuttonCursor rulewaynesutton/opensync/.cursor/rules/convex2.mdc
Note: `paginationOpts` is an object with the following properties: - `numItems`: the maximum number of documents to return (the validator is `v.number()`) - `cursor`: the cursor to use to fetch the next
waynesuttonCursor rulewaynesutton/opensync/.cursor/rules/convex-write-conflicts.mdc
Guidelines for preventing write conflicts when using React, useEffect, and Convex
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.
