novu / rules
novuhq/novu/.cursor/rules/dashboard.mdc
Rules for working in the Dashboard (React frontend)
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/dashboard.mdc
Rules for working in the Dashboard (React frontend)
backstage/backstage/.cursor/rules/tests/test-utils.mdc
Enforce usage of @backstage/test-utils in frontend tests
No other project uses it yet
microsoft/data-formulator/.cursor/rules/frontend-test-conventions.mdc
Frontend TypeScript test conventions (Vitest)
microsoft/data-formulator/.cursor/rules/unified-error-protocol.mdc
Unified error handling protocol for backend and frontend
PostHog/posthog/.cursor/rules/react-typescript.mdc
Rules for writing frontend code at PostHog (mostly React + Typescript with Kea)
1 project uses a version of this
appsmithorg/appsmith/.cursor/rules/testing/test-generator.mdc
Test conventions and examples for frontend (Jest/Cypress) and backend (JUnit) — file naming, frameworks, and patterns
No other project uses it yet
appsmithorg/appsmith/.cursor/rules/frontend.mdc
React frontend — TypeScript SPA, monorepo packages, Redux-Saga, key directories, testing, and build commands
No other project uses it yet
apache/superset/.cursor/rules/dev-standard.mdc
Apache Superset development standards and guidelines for Cursor IDE
No other project uses it yet
maybe-finance/maybe/.cursor/rules/general-rules.mdc
Miscellaneous rules to get the AI to behave
streamlit/streamlit/.cursor/rules/e2e_playwright.mdc
with pytest to e2e test Streamlit library. E2E tests verify the complete Streamlit system (frontend, backend, communication, state, visual appearance) from a user's perspective (black-box). They complement Python/JS
No other project uses it yet
streamlit/streamlit/.cursor/rules/overview.mdc
data apps and internal tools. ## Tech Stack - **Backend (Server):** Python, Starlette/Uvicorn server, pytest - **Frontend (Web UI):** TypeScript, React, Emotion (CSS-in-JS), Vite, Vitest - **Communication:** Protocol Buffers (protobuf) over WebSocket
streamlit/streamlit/.cursor/rules/protobuf.mdc
alwaysApply: false --- # Protobuf Protobuf messages are used for communication between the Streamlit backend and frontend via WebSocket connections. ## Compile Protobuf Changes requiring compilation: - Adding, modifying, or removing fields Changes
streamlit/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
streamlit/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
streamlit/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
streamlit/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
streamlit/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
novuhq/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
novuhq/novu/.cursor/rules/packages.mdc
Rules for working in the shared NPM packages
CopilotKit/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
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.