claude-task-master / rules
eyaltoledano/claude-task-master/.cursor/rules/git_workflow.mdc
Git workflow integrated with Task Master for feature development and collaboration
Coolinginterest down 32% this month
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.
eyaltoledano/claude-task-master/.cursor/rules/git_workflow.mdc
Git workflow integrated with Task Master for feature development and collaboration
Coolinginterest down 32% this month
eyaltoledano/claude-task-master/.cursor/rules/mcp.mdc
Guidelines for implementing and interacting with the Task Master MCP Server
Coolinginterest down 32% this month
eyaltoledano/claude-task-master/.cursor/rules/new_features.mdc
Guidelines for integrating new features into the Task Master CLI
Coolinginterest down 32% this month
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
Coolinginterest down 32% this month
eyaltoledano/claude-task-master/.cursor/rules/taskmaster/dev_workflow.mdc
Guide for using Taskmaster to manage task-driven development workflows
Coolinginterest down 32% this month
eyaltoledano/claude-task-master/.cursor/rules/taskmaster.mdc
Comprehensive reference for Taskmaster MCP tools and CLI commands.
Coolinginterest down 32% this month
eyaltoledano/claude-task-master/.cursor/rules/taskmaster/taskmaster.mdc
Comprehensive reference for Taskmaster MCP tools and CLI commands.
Coolinginterest down 32% this month
eyaltoledano/claude-task-master/.cursor/rules/tasks.mdc
Guidelines for implementing task management operations
Coolinginterest down 32% this month
eyaltoledano/claude-task-master/.cursor/rules/telemetry.mdc
Guidelines for integrating AI usage telemetry across Task Master.
Coolinginterest down 32% this month
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
Coolinginterest down 32% this month
eyaltoledano/claude-task-master/.cursor/rules/utilities.mdc
server/src/core/utils) (e.g., `path-utils.js`). - Tool Execution/Response Helpers: [`mcp-server/src/tools/utils.js`](mdc:mcp-server/src/tools/utils.js). ## Documentation Standards - **JSDoc Format**: - ✅ DO: Document all parameters and return values - ✅ DO: Include descriptions for complex
Coolinginterest down 32% this month
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
vercel/ai-chatbot/.cursor/rules/ultracite.mdc
Ultracite Rules - AI-Ready Formatter and Linter
14 projects use a version of this
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
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
Steady2 mentions in 2 weeks
No other project uses it yet
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
triggerdotdev/trigger.dev/.cursor/rules/repo.mdc
understanding the structure of the monorepo
Steady6 mentions in 2 weeks
No other project uses it yet
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
1 project uses a version of this
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
1 project uses a version of this
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
1 project uses a version of this
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.