TechNickAICursor rule100x / python
TechNickAI/100x/.cursor/rules/python/pytest-what-to-test-and-mocking.mdc
When writing tests
Cursor rules examples
The rules real projects give Cursor's agent, from .cursor/rules.
Best matches · from page 16Worked for most · soon
TechNickAICursor rule
ujjwal502Cursor ruledebugduck / rules
ujjwal502/debugduck/.cursor/rules/debug.mdc
Systematic root-cause debugging. Use whenever something is broken, failing, flaky, slow, crashing, or behaving unexpectedly — bug reports, stack traces, failing or flaky tests, regressions, hangs, memory leaks, wrong output, CI-only failures, "works on my machine".
Surya8991Cursor ruleAgentMaster / rules
Surya8991/AgentMaster/.cursor/rules/security-audit.mdc
Security auditing skill for web applications and codebases. Scans for OWASP Top 10, dependency vulnerabilities, secrets exposure, XSS/CSRF/injection flaws, auth weaknesses, and misconfigurations. Use when task involves security scan, vulnerability assessment, pen test review, threat modeling, or hardening a codebase.
2612evgenii-hueCursor rulebusiness-idea-evaluator / rules
2612evgenii-hue/business-idea-evaluator/.cursor/rules/business-idea-evaluator.mdc
Objective, evidence-based business idea evaluation via 18 real subagents and a deterministic Business Reality Score. Apply when the user asks to evaluate, validate, score, or stress-test a business idea, startup concept, SaaS idea, side project, or monetization plan.
Zulut30Cursor ruledart-mobile-game-studio / agents
Zulut30/dart-mobile-game-studio/.cursor/rules/agents/code-auditor.mdc
Whole-codebase code auditor for Flutter/Dart mobile games (iOS + Android). Use to audit the ENTIRE project (not just a diff) for correctness, architecture conformance, consistency, dead code, and test coverage. Complements code-reviewer (which reviews a single diff/PR). Read-only — reports findings.
RagnarPitlaCursor rulemicrosoft-agent-skills-private-archive / rules
RagnarPitla/microsoft-agent-skills-private-archive/.cursor/rules/copilot-studio-production-patterns.mdc
The patterns that separate a Copilot Studio agent that demos well from one that survives production. Use when an agent is being designed for or promoted to production, when an agent works in test but fails with real users, when calls to slow backend systems time out, when context is lost across a multi-agent handoff, or when preparing a production readiness review.
MANVENDRA-githubCursor ruleerror-handling
MANVENDRA-github/agentry/.cursor/rules/rust/error-handling.mdc
Rust error-handling discipline — return `Result`, keep `unwrap`/`expect`/`panic!` out of library and request paths, propagate with `?` and typed errors. Apply when working in any Rust file. Skip for prototypes, examples, and tests where a panic on failure is acceptable.
MANVENDRA-githubCursor ruleoptionals-and-memory
MANVENDRA-github/agentry/.cursor/rules/swift/optionals-and-memory.mdc
Swift optionals- and memory-safety discipline — unwrap with `guard let`/`if let`/`??` not force-unwrap, break ARC retain cycles with `[weak self]`/`unowned`. Apply when working in any Swift file. Skip for a throwaway playground or a test where a trap on failure is acceptable.
katalon-labsCursor ruletrue-skills / rules
katalon-labs/true-skills/.cursor/rules/playwright-execute.mdc
Run Playwright tests or suites and upload the resulting report to Katalon True Platform. Use when you need to execute Playwright scripts, package scripts, spec files, projects, or suites, configure or verify @katalon/playwright-reporter, upload Playwright reports with Katalon CLI/reporter commands, and verify uploaded Katalon Platform runs or reports. Written for the automation tester who wants the suite driven and the results landed in the platform in one step. For a report from a run that has already finished, or from any other framework, use upload-report.
mchittineniCursor rulecloud-platform-skills / skills
mchittineni/cloud-platform-skills/.cursor/rules/skills/performance-load-testing.mdc
Performance engineering with k6 and Locust: load, stress, spike and soak profiles, virtual users (VUs), latency percentiles (p95/p99), threshold-gated tests in CI, and bottleneck profiling. Use when writing a k6 or Locust script, deciding whether an API can handle a peak traffic event, capacity planning before launch, or investigating why average latency looks fine while users report slowness.
mchittineniCursor rulecloud-platform-skills / skills
mchittineni/cloud-platform-skills/.cursor/rules/skills/chaos-engineering-resilience-testing.mdc
Chaos engineering practice: steady-state hypotheses tied to SLIs, blast-radius containment, pre-agreed abort criteria and automated rollback, fault injection with AWS FIS, Chaos Mesh or LitmusChaos, and GameDay facilitation that produces fixes. Use when a failover or redundancy claim has never actually been tested, when planning a GameDay or resilience exercise, or when deciding whether it is safe to inject failure into production and how to bound it.
MANVENDRA-githubCursor ruleeval-harness
MANVENDRA-github/agentry/.cursor/rules/eval-harness.mdc
Discipline of knowing whether a change to an LLM or agent system actually improved its output — build a fixed eval set, define graders, measure a baseline, gate regressions. Invoke when tuning a prompt, model, tool, or agent whose quality is otherwise judged by eyeballing. Skip for deterministic code where a normal test suite already proves correctness.
edhoferdianCursor ruleEEF / rules
edhoferdian/EEF/.cursor/rules/dead-code-cleanup-edho-ferdian.mdc
Staged dead-code removal workflow — detect (stack-appropriate tooling: knip/depcheck/ts-prune, vulture/deptry, cargo-udeps, deadcode, ...), classify by removal risk (SAFE/CAREFUL/RISKY), cross-check every \"unused\" hit against Salak's repo-graph.json reverse-dependency data when available, then delete in ordered categories (deps → exports → files → duplicates) running the test suite between each category. Use this whenever the user wants dead code, unused exports, unused dependencies, or duplicate code actually REMOVED — \"bersihkan kode mati\", \"hapus yang tidak dipakai\", \"cleanup unused code/deps\", \"remove dead code\", \"consolidate duplicates\". Not for finding-only review — see the scope note below for the boundary with code-review-edho-ferdian's CQ-07.
edhoferdianCursor ruleEEF / rules
edhoferdian/EEF/.cursor/rules/language-code-review-edho-ferdian.mdc
Language- and framework-specific code review lenses layered on top of the general four-domain review in code-review-edho-ferdian — idioms, framework security misconfigurations, ORM/query correctness, performance traps, and testing conventions, auto-detected across ~20 stacks (React, Python, Go, Java/Spring, Ruby, and more — see the reference table below for the full list). Use whenever a review touches a specific language/framework and the generic checklist isn't enough — \"review kode Go/Python/React ini\", \"audit Django models\", \"cek FastAPI endpoint ini\", or when the user names a stack while asking for review. Loads only the lens file(s) matching the detected stack. Inherits Reflection and Critique-Correction gates from code-review-edho-ferdian.
edhoferdianCursor ruleEEF / rules
edhoferdian/EEF/.cursor/rules/dev-kickoff-edho-ferdian.mdc
Kickoff and execute a development project from ANY specification or planning documents (PRD, SRS, WBS, tech spec, RFC, ADRs, and more — see the Phase 0 role table below for the full list). Classifies docs by role, cross-validates them, extracts a binding Project Decision Register, generates an Execution Context Pack plus a project-fit agent roster, then builds task-by-task through a seven-stage PLAN→TEST→IMPLEMENT→REVIEW→ VERIFY→REMEMBER→IMPROVE loop — auto-invoking this ecosystem's other skills as needed. Use whenever the user wants to build from specs, or says \"mulai proyek\", \"kickoff\", \"buat context pack\", \"handoff ke Cursor\" — or wants to RESUME: \"lanjutkan proyek\", \"resume\", \"lanjut dari snapshot\". Also use when a repo has /project-memory/ and the user asks to continue it.
n-shadlooCursor rulefrontend-production-engineer / rules
n-shadloo/frontend-production-engineer/.cursor/rules/frontend-production-engineer.mdc
Production-grade frontend engineering for Next.js and TypeScript against a Django/DRF backend — plan first, verify the installed versions, never invent an API, keep the diff minimal, run the checks, and hold the work to a stated definition of done. Covers routing and rendering, the server/client boundary, the React component tree, the typed backend contract, and the non-functional guarantees (accessibility, security, performance, testing) that gate completion. All twenty-four domains are integrated; the router in SKILL.md is the authoritative list of what is loadable. Canonical instructions live in SKILL.md and references/.
rlaopeCursor rulenen / rules
rlaope/nen/.cursor/rules/nen-vow.mdc
Pre-commitment engineering — declare falsifiable vows before the work starts and audit every one before claiming done, discipline pledges distilled from the engaged skills' Done means plus scope pledges bounding the blast radius. Use when the user says \"don't touch anything else\", \"only this file\", \"stay in scope\", \"no new dependencies\", \"don't tell me it's done until\", \"commit to your constraints\", or \"show me the failing test first\"; when a previous attempt was declared done and was not; when a diff wandered into files nobody asked about; when en announces an engagement (the announcement is the vow moment); or when delegated work needs acceptance criteria the delegate can be audited against.
edhoferdianCursor ruleEEF / rules
edhoferdian/EEF/.cursor/rules/code-review-edho-ferdian.mdc
Senior-engineer code review across five domains — Code Quality, Security, Performance, Blueprint/Spec Consistency, and Test Quality — plus conditional lenses auto-detected from scope (database, accessibility, RAG, ML, healthcare, agent/LLM — see Phase 0 below for the full list). Produces an evidence-backed findings report with confidence-labeled severities and an adaptive fix. Use whenever the user wants code reviewed, audited, or checked before merge/deploy: \"review this\", \"audit\", \"cek kode\", \"review PR\", \"is this production-ready\", \"find bugs/security issues\" — even without the word \"review\". Includes Reflection and a Critique-Correction Loop to suppress false positives. If the request is entirely about security (\"security audit\", \"cek keamanan kode ini\"), route to `security-review-edho-ferdian` instead — that skill is the single source of truth for security review criteria.
Zulut30Cursor ruledart-mobile-game-studio / agents
Zulut30/dart-mobile-game-studio/.cursor/rules/agents/release-engineer.mdc
Dual-store release engineer for Flutter/Dart mobile games (iOS + Android). Use to make a finished game submission-ready and avoid review rejections on BOTH the App Store and Google Play — app icons & splash, Info.plist + AndroidManifest, version/build (pubspec `version: x.y.z+n`), `flutter build ipa` / `flutter build appbundle`, signing (iOS provisioning profiles & certificates, Android upload keystore/key.properties/signingConfigs), App Store Connect + Play Console metadata, privacy nutrition label + Play Data safety, TestFlight + Play internal testing, and common rejection/suspension traps. Produces a release plan + dual-store checklist; the actual upload is done by the user. NOT a guarantee of approval.
adammatthewsteinbergerCursor ruleclaudeloop / rules
adammatthewsteinberger/claudeloop/.cursor/rules/claudeloop-domain-model.mdc
Explains every value object and ADT in src/claudeloop/domain/ — CapacityState (Available/WindowExhausted/CreditsExhausted/AuthenticationFailed), TurnSignals classification, CompletionVerdict (Done/Continue/Blocked), the wait-probe policy in waiting.py, Budget/BudgetLedger, and the run-loop state machine in loop.py. Use this whenever reading, modifying, or extending anything in src/claudeloop/domain/ or tests/domain/, whenever the user asks about rate-limit classification, credits vs. rate limits, capacity states, completion detection, the waiting/backoff policy, or the run-loop state machine, and whenever adding a new domain type or branch. Make sure to consult this before touching domain/classify.py, domain/waiting.py, domain/completion.py, or domain/loop.py — the ordering of branches in each is deliberate and tested, and an out-of-order edit silently reintroduces bugs this project was specifically built to fix.
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.