Cursor rules examples

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

eyaltoledanoCursor rule

claude-task-master / rules

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

description: globs: scripts/modules/* alwaysApply: false --- # Tagged Task Lists Command Patterns This document outlines the standardized patterns that **ALL** Task Master commands must follow to properly support the tagged task lists

eyaltoledanoCursor rule

claude-task-master / rules

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

Guidelines for implementing task management operations

eyaltoledanoCursor rule

claude-task-master / rules

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

Guidelines for integrating AI usage telemetry across Task Master.

eyaltoledanoCursor rule

claude-task-master / rules

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

Directories**: Organized by test type and mirroring source structure #### **TaskMaster Integration for Any Framework** **Document Testing Setup in Subtasks:** ```bash # Update subtask with testing framework setup task-master update-subtask

cube-jsCursor rule

cube / rules

cube-js/cube/.cursor/rules/writing-documentation.mdc

alwaysApply: true globs: docs-mintlify/** --- This repo only contains code for Cube Core and documentation. Our cloud product codebase is located in ~/code/cubejs-enterprise (at least that is where

No other project uses it yet

VercelCursor rule

ai-chatbot / rules

vercel/ai-chatbot/.cursor/rules/ultracite.mdc

Ultracite Rules - AI-Ready Formatter and Linter

transitive-bullshitCursor rule

agentic / rules

transitive-bullshit/agentic/.cursor/rules/general.mdc

silently; always log or handle caught errors appropriately ## Comments Comments should be used to document and explain code. They should complement the use of descriptive variable and function names

koelCursor rule

koel / rules

koel/koel/.cursor/rules/laravel-boost.mdc

concise in your explanations - focus on what's important rather than explaining obvious details. ## Documentation Files - You must only create documentation files if explicitly requested by the user. === boost rules

No other project uses it yet

MicrosoftCursor rule

data-formulator / rules

microsoft/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

triggerdotdevCursor rule

trigger.dev / rules

triggerdotdev/trigger.dev/.cursor/rules/repo.mdc

understanding the structure of the monorepo

No other project uses it yet

explodinggradientsCursor rule

ragas / rules

explodinggradients/ragas/.cursor/rules/docs-diataxis-guidelines.mdc

globs: docs/** --- # Diátaxis Documentation Guidelines When writing or editing documentation, categorise each page as **one** of the four Diátaxis modes and follow its specific guidance. *Do not mix modes

explodinggradientsCursor rule

ragas / rules

explodinggradients/ragas/.cursor/rules/docs-structure.mdc

globs: docs/** --- # Documentation Structure & Workflow Follow these conventions when creating or editing documentation: 1. **Docs live in [docs/](mdc:docs/)** • Use Markdown (`.md`) files. • Images and other assets

explodinggradientsCursor rule

ragas / rules

explodinggradients/ragas/.cursor/rules/project-structure.mdc

extra • Local development: `uv pip install -e . -e ./examples` • Usage: `python -m ragas_examples.benchmark_llm.prompt` Shared documentation for all projects is located under [docs/](docs/). Root-level [Makefile](Makefile) provides combined commands

albumentations-teamCursor rule

albumentations / rules

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

description: globs: alwaysApply: true --- # Coding Guidelines This document outlines the coding standards and best practices for contributing to Albumentations. ## Important Note About Guidelines These guidelines represent our current best practices

567-labsCursor rule

instructor / rules

567-labs/instructor/.cursor/rules/readme.md

behavior ## Available Rules Currently, the following rules are defined: ### `simple-language.mdc` - **Purpose**: Ensures documentation is written at a grade 10 reading level - **Applies to**: Markdown files (*.md) - **Auto Apply

No other project uses it yet

Open-LLM-VTuberCursor rule

Open-LLM-VTuber / rules

Open-LLM-VTuber/Open-LLM-VTuber/.cursor/rules/olv-core-rules.mdc

integrated into the `frontend/` directory of this backend repository via a git submodule. - Documentation Repository: The official documentation site is hosted in the `open-llm-vtuber.github.io` repository. When asked to generate documentation

No other project uses it yet

elie222Cursor rule

inbox-zero / features

elie222/inbox-zero/.cursor/rules/features/schedule.mdc

with schedule checks ### Validation & Types - `apps/web/app/api/ai/digest/validation.ts` - API validation schemas - `apps/web/types/schedule.ts` - TypeScript type definitions --- ## Related Documentation - **[Digest Feature](mdc:digest.mdc)** - Primary use case for Schedule - **[Prisma Documentation](mdc:https:/prisma.io/docs)** - Database

No other project uses it yet

elie222Cursor rule

inbox-zero / rules

elie222/inbox-zero/.cursor/rules/task-list.mdc

implementation 4. Maintain the "Relevant Files" section with accurate file paths and descriptions 5. Document implementation details, especially for complex features 6. When implementing tasks one by one, first check

elie222Cursor rule

inbox-zero / rules

elie222/inbox-zero/.cursor/rules/ultracite.mdc

switch clauses. - Don't use variables that haven't been declared in the document. - Don't write unreachable code. - Make sure super() is called exactly once on every code path

No other project uses it yet