readwise-vector-db / taskmaster
leonardsellem/readwise-vector-db/.cursor/rules/taskmaster/dev_workflow.mdc
Guide for using Taskmaster to manage task-driven development workflows
The rules real projects give Cursor's agent, from .cursor/rules.
leonardsellem/readwise-vector-db/.cursor/rules/taskmaster/dev_workflow.mdc
Guide for using Taskmaster to manage task-driven development workflows
leonardsellem/readwise-vector-db/.cursor/rules/taskmaster/taskmaster.mdc
Comprehensive reference for Taskmaster MCP tools and CLI commands.
galyarderlabs/galyarder-framework/.cursor/rules/email-marketing-bible.mdc
>
galyarderlabs/galyarder-framework/.cursor/rules/playwright-pro.mdc
Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites. Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55 templates, 3 agents, smart reporting.
galyarderlabs/galyarder-framework/.cursor/rules/using-galyarder-framework.mdc
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Lzh-xbccz/hermes-finance/.cursor/rules/hermes-finance.mdc
Hermes Finance market-analysis workflow and MCP entry points
sruja-ai/sruja/.cursor/rules/sruja-context-host.mdc
Wire Phase 3/4 context tools (drift injector, session prune, memory search) when using Sruja MCP
AI-by-design/primitiv/.cursor/rules/project.mdc
Primitiv project rules — apply to all files
dazeb/coolify-mcp-enhanced/.cursor/rules/802-coolify-mcp-workflow.mdc
FOLLOW Coolify MCP workflow WHEN implementing new Coolify API endpoints TO ensure consistent and tested MCP
edhoferdian/EEF/.cursor/rules/api-design-edho-ferdian.mdc
Design and evolve API boundaries and contracts — REST resource naming, status-code semantics, pagination strategy, versioning policy, and the discipline of treating one contract artifact (OpenAPI/schema) as authoritative so client and server never drift. A design-time activity, distinct from system-design-edho-ferdian (broader architectural trade-offs) and code-review-edho-ferdian (reviewing an already-written endpoint). Trigger phrases: \"desain API untuk fitur ini\", \"bagaimana struktur endpoint yang baik\", \"API contract berubah, bagaimana handle-nya\", \"REST vs apa\", or when starting a new API surface.
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.
edhoferdian/EEF/.cursor/rules/communications-triage-edho-ferdian.mdc
Channel-agnostic framework for triaging incoming messages (email, chat, Slack, LINE, Messenger, or any other channel) into four priority tiers, drafting replies that stay within a strict human-approval gate, and tracking whether a sent reply's promises actually get followed through on. Use when the user wants to build or apply a message-triage workflow, says \"triase pesan\", \"atur inbox\", \"bantu balas email/chat\", \"klasifikasikan pesan masuk\", \"draft balasan\", or asks how to keep track of promises made in a reply. Note: no channel (Gmail, Slack, etc.) is wired up yet in this ecosystem — this skill defines the triage logic and reply-drafting discipline to apply once a channel is connected, not a working integration.
edhoferdian/EEF/.cursor/rules/gan-harness-edho-ferdian.mdc
Rapid, adversarial-loop prototyping and design iteration: a Plan → Generate → Evaluate cycle where a generator builds a live app and an evaluator drives it in a real browser, scores it against a weighted design rubric, and feeds fixes back until a quality threshold is crossed (see the Plan phase section below for exactly how scope is sourced, never invented from a one-line prompt). Use when the user wants fast UI/prototype iteration with automated design critique, says \"gan-harness\", \"loop generate-evaluate\", \"iterate sampai bagus\", or wants a live app scored and improved automatically. Not a substitute for dev-kickoff-edho-ferdian's IMPLEMENT stage on production feature work — this is the faster/looser prototyping variant.
edhoferdian/EEF/.cursor/rules/research-ops-edho-ferdian.mdc
Evidence-first research workflow — classify what kind of research the question actually needs, take the lightest evidence path that answers it, synthesize multiple sources into a cited report, and label every claim by evidence type (sourced fact / user-supplied / inference / recommendation) so a reader can tell what is proven from what is guessed. Use whenever the user says \"riset\", \"cari tahu\", \"cek fakta\", \"bandingkan X vs Y\", \"apa yang terbaru soal\", \"research this\", \"deep dive\", \"investigate\", or asks a question whose answer depends on current public information rather than on this repo's own code. For competitor benchmarking and positioning research, use `marketing-edho-ferdian/references/market-and-competitor-research.md` instead — it consumes this skill's evidence method rather than repeating it.
edhoferdian/EEF/.cursor/rules/skill-authoring-edho-ferdian.mdc
Discipline for creating and governing this ecosystem's own skills: search before building (local → marketplace → GitHub → web, with a security vet on anything external), write to a quality bar, measure whether a skill is actually obeyed rather than assuming it, promote recurring cross-skill principles up into rules, and package a finished skill into `dist/*.skill` for manual upload. Use when the user says \"bikin skill baru\", \"ada skill buat X gak\", \"fork skill ini\", \"skill gue kepake gak sih\", \"package skill ini\", \"mau publish skill ini\", \"buatkan .skill-nya\", or before adding anything to this repo's `skills/` or `dist/`.
louisbrulenaudet/monorepo-template/.cursor/rules/backend/ports.mdc
Local dev port allocation - role ranges, registry, inspector_port, strictPort, multi-config wrangler.
louisbrulenaudet/monorepo-template/.cursor/rules/ops/previews.mdc
Cloudflare Worker Previews - previews block under env.production, same --env on every command, preview-only wildcard CORS, Vite CLOUDFLARE_ENV build, Access before arming, PR workflow and agent loop
louisbrulenaudet/monorepo-template/.cursor/rules/tests/vitest.mdc
Vitest - two runtimes, @repo/vitest-config, no watch for agents
sandraschi/advanced-memory-mcp/.cursor/rules/advanced-memory-mcp-standards.mdc
Critical rules for advanced-memory-mcp to prevent Unicode crashes and Linux syntax errors in PowerShell environments
MohamedAbdallah-14/prompt-to-asset/.cursor/rules/prompt-enhancer.mdc
Asset generation — route, rewrite, generate, validate. Never send transparency requests to Imagen/Gemini.
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.