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.
streamlitCursor rulestreamlit/streamlit/.cursor/rules/python_lib.mdc
error_id`. ## Theming and Layout - **Theming and layout calculations must be done in the frontend, not the Python backend.** - Do not use `get_option("theme.primaryColor")` or similar theme options
streamlitCursor rulestreamlit/streamlit/.cursor/rules/skills.mdc
specific tasks in the Streamlit codebase. These skills are for **Streamlit library development** (backend, frontend, protobufs), not for building Streamlit applications. User-facing skills that ship with the library live
streamlitCursor rulestreamlit/streamlit/.cursor/rules/specs.mdc
address` returns `None` on SiS—that's a valid design choice. ## 37. Consider the Frontend-Backend Split Some data lives in the browser (theme type, viewport size) and some
streamlitCursor rulestreamlit/streamlit/.cursor/rules/typescript.mdc
fine — the rule applies only to files whose sole purpose is re-exporting. ## Key Frontend Principles - Leverage all of best practices of React 18. - Follow the [Rules of React
streamlitReads credentialsCursor rulestreamlit/streamlit/.cursor/rules/workflows.mdc
unit tests, linting, type checking across all supported Python versions | | `js-tests.yml` | Push/PR to `develop` | Frontend TypeScript linting, type checking, Knip unused-export and unused-dependency analysis (PR-blocking), and Vitest
novuhqCursor rulenovuhq/novu/.cursor/rules/novu.mdc
components/auth-wizard`) - Named exports for all components - TypeScript: `interface` on the backend, `type` on the frontend — this is the project convention and overrides any general "prefer interfaces" guidance - Blank line before
novuhqCursor rulenovuhq/novu/.cursor/rules/packages.mdc
Rules for working in the shared NPM packages
CopilotKitCursor ruleCopilotKit/CopilotKit/.cursor/rules/agent-development.mdc
Simple agents that handle specific tasks: - File structure: `agent/main.py` or `agent/index.js` - Direct communication with frontend - Good for focused use cases ### Multi-Agent (Coagents) Pattern Complex systems with multiple cooperating agents
No other project uses it yet
CopilotKitCursor ruleCopilotKit/CopilotKit/.cursor/rules/copilotkit-architecture.mdc
examples/) and typically follow this pattern: - `agent/` or `agent-py/` - Backend agent implementation - `ui/` - Frontend Next.js application - `README.md` - Setup and usage instructions ## Development Workflow - Examples use the local packages
No other project uses it yet
CopilotKitCursor ruleCopilotKit/CopilotKit/.cursor/rules/examples-and-demos.mdc
collaborative editing ### CrewAI Integration Examples - **[coagents-starter-crewai-flows/](mdc:examples/coagents-starter-crewai-flows)** - CrewAI flows integration ### Frontend-Focused Examples - **[chat-with-your-data/](mdc:examples/v1/chat-with-your-data)** - Chat interface with custom data - **[form-filling
No other project uses it yet
CopilotKitCursor ruleCopilotKit/CopilotKit/.cursor/rules/frontend-development.mdc
description: globs: alwaysApply: false --- # CopilotKit Frontend Development Guide ## Core React Packages ### React Components - **[react-core/](mdc:packages/react-core/)** - Core React components and hooks - `CopilotProvider` - Main provider component - `useCopilotChat` - Chat functionality hook
No other project uses it yet
CopilotKitCursor ruleCopilotKit/CopilotKit/.cursor/rules/quick-reference.mdc
Code workspace settings - **[examples/shared/](mdc:examples/shared)** - Shared utilities and templates ## Common Patterns 1. **Frontend**: Next.js app with CopilotProvider and CopilotChat 2. **Backend**: Python or Node.js agent with actions and state
No other project uses it yet
blakeblackshearCursor ruleblakeblackshear/frigate/.cursor/rules/frontend-always-use-translation-files.mdc
globs: ["**/*.ts", "**/*.tsx"] alwaysApply: false --- Never write strings in the frontend directly, always write to and reference the relevant translations file
No other project uses it yet
HumanSignalCursor ruleHumanSignal/label-studio/.cursor/rules/react.mdc
React coding standards and best practices for the LabelStudio clientside application
HumanSignalCursor ruleHumanSignal/label-studio/.cursor/rules/storage-provider.mdc
How to add a new storage or data connector for Label Studio
transitive-bullshitCursor ruletransitive-bullshit/agentic/.cursor/rules/general.mdc
external modules or partial function arguments, referencing the usage guidelines in the TypeScript section. - Frontend react code does not need unit tests ### Test Coverage - Test critical business logic and edge
koelCursor rulekoel/koel/.cursor/rules/laravel-boost.mdc
base folders without approval. - Do not change the application's dependencies without approval. ## Frontend Bundling - If the user doesn't see a frontend change reflected in the UI, it could
No other project uses it yet
MicrosoftCursor rulemicrosoft/data-formulator/.cursor/rules/dataframe-serialization.mdc
DataFrame Serialization All DataFrame-to-records conversion for API responses, streaming events, or frontend-visible data MUST use the centralized helpers in `data_formulator.datalake.parquet_utils`: | Source type | Helper | |---|---| | `pd.DataFrame
No other project uses it yet
MicrosoftCursor rulemicrosoft/data-formulator/.cursor/rules/dev-guides-first.mdc
Require reading dev-guides before development and keeping docs in sync
No other project uses it yet
MicrosoftCursor rulemicrosoft/data-formulator/.cursor/rules/i18n-no-hardcoded-strings.mdc
No hardcoded UI strings — use i18n translation keys
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.
