J-PsterCursor rulePsters_AI_Workflow / rules
J-Pster/Psters_AI_Workflow/.cursor/rules/commits.mdc
Commit message standards and conventions
Cursor rules examples
The rules real projects give Cursor's agent, from .cursor/rules.
Best matches · from page 12Worked for most · soon
J-PsterCursor rule
HoangP8Cursor ruletokless / rules
HoangP8/tokless/.cursor/rules/build-discipline.mdc
This rule guides simple, focused implementations that reuse existing solutions and avoid unnecessary work.
HoangP8Cursor ruletokless / rules
HoangP8/tokless/.cursor/rules/response-style.mdc
This rule provides standards for concise, direct, and technically accurate communication.
przeprogramowaniCursor ruleai-rules-builder / rules
przeprogramowani/ai-rules-builder/.cursor/rules/supabase.mdc
type CookieOptionsWithName } from '@supabase/ssr'; import type { Database } from '../db/database.types.ts'; export const cookieOptions: CookieOptionsWithName = { path: '/', secure: true, httpOnly: true, sameSite: 'lax', }; export const createSupabaseServerInstance = (context: { headers: Headers; cookies: AstroCookies; }) => { const supabase
przeprogramowaniCursor ruleai-rules-builder / rules
przeprogramowani/ai-rules-builder/.cursor/rules/supabase-migrations.mdc
alwaysApply: false --- # Database: Create migration You are a Postgres Expert who loves creating secure database schemas. This project uses the migrations provided by the Supabase CLI. ## Creating a migration file
terragon-labsCursor ruleterragon-oss / rules
terragon-labs/terragon-oss/.cursor/rules/project-conventions.mdc
Terragon AI coding assistant platform development conventions and guidelines
MCP-DefenderCursor ruleMCP-Defender / rules
MCP-Defender/MCP-Defender/.cursor/rules/mcp-defender-overview.mdc
description: globs: alwaysApply: true --- # MCP Defender Overview MCP Defender is a security application designed to monitor and protect Model Context Protocol (MCP) communications. It intercepts tool calls and responses, verifying
redongreenCursor ruleuSpec / rules
redongreen/uSpec/.cursor/rules/mintlify.mdc
using 8.8.8.8 as DNS server ```javascript const config = { performance: { cache: true, timeout: 30000 }, security: { encryption: 'AES-256' } }; ``` ### Cards and columns for emphasizing information Example of cards and card groups: Complete
danielvm-gitCursor rulebigpowers / rules
danielvm-git/bigpowers/.cursor/rules/audit-code.mdc
Self-review checklist for the coding agent to run before dispatching a reviewer. Checks CONVENTIONS.md compliance, Boy Scout Rule, test coverage, types, and SOLID. Produces a pass/fail checklist. Use before request-review, before committing, or when user asks for a code quality check.
danielvm-gitCursor rulebigpowers / rules
danielvm-git/bigpowers/.cursor/rules/build-epic.mdc
Eight-step epic build cycle — reads state.yaml, execution-status.yaml, and one epic capsule; updates status via bp-yaml-set or direct edit. Resume mode runs one step per invocation. Use instead of ad-hoc execute-plan for release work.
danielvm-gitCursor rulebigpowers / rules
danielvm-git/bigpowers/.cursor/rules/change-request.mdc
Add a new requirement or reorder epics by WSJF against specs/release-plan.yaml and epic capsule directories. Modes Add and Reorder. Use when a new requirement arrives mid-release or the plan needs prioritization.
danielvm-gitCursor rulebigpowers / rules
danielvm-git/bigpowers/.cursor/rules/compose-workflow.mdc
Chain multiple bigpowers skills into a custom workflow recipe saved in specs/. Use when a project repeats a non-standard skill sequence, or user wants a documented playbook beyond orchestrate-project modes.
danielvm-gitCursor rulebigpowers / rules
danielvm-git/bigpowers/.cursor/rules/delegate-task.mdc
Delegate one complex task to a single subagent, review its work in two stages before merging back. Sequential — one agent at a time, with oversight. Use when a task is complex and requires careful review before the result is accepted. Distinct from dispatch-agents (no parallelism here; reviewer sees full diff before proceeding).
danielvm-gitCursor rulebigpowers / rules
danielvm-git/bigpowers/.cursor/rules/dispatch-agents.mdc
Dispatch multiple subagents in parallel on independent tasks. No waiting between them — all run concurrently. Use when tasks are truly decoupled and speed matters. Distinct from delegate-task (concurrent here, no inter-task review gate).
danielvm-gitCursor rulebigpowers / rules
danielvm-git/bigpowers/.cursor/rules/generate-allure-report.mdc
Generate Allure-ready reports from bigpowers YAML metadata. Reads execution-status.yaml, release-plan.yaml, epic capsules, task YAMLs, cycle-times.yaml, and bug registry to produce allure-results/junit-results.xml, categories.json, and executor.json. Use when preparing progress dashboards, integrating with Allure TestOps, or generating CI reports.
danielvm-gitCursor rulebigpowers / rules
danielvm-git/bigpowers/.cursor/rules/inspect-quality.mdc
Interactive QA session where user reports bugs or issues conversationally, and the agent logs them to specs/bugs/registry.yaml with a structured audit schema. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, or mentions \"QA session\".
danielvm-gitCursor rulebigpowers / rules
danielvm-git/bigpowers/.cursor/rules/investigate-bug.mdc
Investigate a bug or issue by exploring the codebase to find root cause, then write a TDD-based fix plan to specs/bugs/BUG-*.md. Use when user reports a bug, wants to investigate a problem, mentions \"triage\", or wants to plan a fix.
danielvm-gitCursor rulebigpowers / rules
danielvm-git/bigpowers/.cursor/rules/migrate-spec.mdc
Detect GSD, spec-kit, or BMAD spec artifacts and transform them into bigpowers YAML layout (state.yaml, release-plan.yaml, epics/, requirements/, plans/, ADRs). Use when migrating foreign spec docs.
danielvm-gitCursor rulebigpowers / rules
danielvm-git/bigpowers/.cursor/rules/plan-release.mdc
RELEASE-INDEX BUILDER — Sequence elaborated epics into specs/release-plan.yaml with WSJF ordering and BCP baselines. NOT a planning-spine substitute: it does not scope work (scope-work) or write story tasks (plan-work). Use after elaborate-spec when the user wants a versioned release index of epics.
danielvm-gitCursor rulebigpowers / rules
danielvm-git/bigpowers/.cursor/rules/plan-work.mdc
PLANNING SPINE STEP 3 of 3 — Plan the work: write detailed implementation tasks into the active epic capsule (specs/epics/eNN-slug/). Produces countable-story-format .md specs and runnable -tasks.yaml files. Use after slice-tasks (step 2). Not a substitute for scope-work (step 1) or slice-tasks (step 2).
About cursor rules
What are cursor rules?
Instruction files for Cursor's agent, kept in .cursor/rules/ as .mdc files.
How are they different from AGENTS.md?
A rule can apply only to files matching a pattern, or only when the agent asks for it. AGENTS.md always applies.
How do I use one?
Copy the .mdc file into your project's .cursor/rules/ directory and adjust its globs.
Which ones worked?
Open a rule to see its discussion. Reports from people and their agents are coming.