suitereact-mcp / rules
reddit/suitereact-mcp/.cursor/rules/global.mdc
SuiteReact MCP project structure, commands, and conventions
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.
reddit/suitereact-mcp/.cursor/rules/global.mdc
SuiteReact MCP project structure, commands, and conventions
reddit/suitereact-mcp/.cursor/rules/netsuite-integration.mdc
NetSuite SDF, Suitelet, and RESTlet conventions
Space-Dinosaurs/DinoStack/.cursor/rules/conventions.mdc
Writing style, project structure conventions, session context and memory handling, and git workflow including protected branches and worktree-per-feature.
bsmi021/mcp-server-webscan/.cursor/rules/main-rule.mdc
description: globs: alwaysApply: true --- # MCP Server Development Guidelines ## project name: mcp-server-webscan ## memory_bank ProjectID: de83ede7-85de-4746-86c7-c2dafefc3fb7 ## Description: A Model Context Protocol (MCP) server
DXHeroes/mcp-devtools/.cursor/rules/core-libraries-usage.mdc
Core Libraries Usage Guidelines
DXHeroes/mcp-devtools/.cursor/rules/mcp-tool-implementation.mdc
MCP Tool Implementation Guidelines
futureweb/intervals-mcp-server/.cursor/rules/api-patterns.mdc
MCP Tool Implementation Pattern 1. **Parameter Validation**: Check required parameters and provide defaults 2. **Credentials**: Tools never take an API key; `make_intervals_request()` uses `API_KEY` from the server
ALAPI-SDK/mcp-alapi-cn/.cursor/rules/mcp.mdc
Each client may support different MCP features, allowing for varying levels of integration with MCP servers. ## Feature support matrix | Client | [Resources] | [Prompts] | [Tools] | [Sampling] | Roots | Notes | | | | | | | | | | ------------------------------------ | ----------- | --------- | ------- | ---------- | ----- | ------------------------------------------------------------------ | - | -------------------- | - | - | - | - | - | ----------------------------- | | [Claude Desktop App][Claude
simtlix/simfinity.js/.cursor/rules/simfinity-architecture.mdc
Simfinity.js project architecture overview -- always loaded for context
simtlix/simfinity.js/.cursor/rules/simfinity-auth-module.mdc
Documents the authorization subsystem -- Envelop plugin, permission maps, rule helpers, and policy expressions
simtlix/simfinity.js/.cursor/rules/simfinity-barber-examples.mdc
Maintain the independent Barber applications, shared frontend, Docker stacks and dedicated CI
simtlix/simfinity.js/.cursor/rules/simfinity-core-functions.mdc
Documents the critical internal functions and pipelines in the Simfinity core engine
simtlix/simfinity.js/.cursor/rules/simfinity-testing.mdc
Testing conventions, patterns, and requirements for when tests must be updated
brianonbased-dev/HoloScript/.cursor/rules/holodoor-security.mdc
HoloDoor security guardrails (replaces Corridor)
katalon-labs/true-skills/.cursor/rules/create-test-cases.mdc
Create, update, organize, and link Katalon True Platform/TestOps manual test cases from a synced requirement key such as CEL-6, a read requirement, or free-text product behavior. Use when you need to analyze requirements, design manual test cases using ISTQB techniques as a reference, check existing Katalon coverage, avoid duplicate test cases, import only missing cases, update or link existing cases, or create/reuse a test suite for newly designed cases. For full requirement-to-execution workflows, combine with or defer to true-platform-testing. Written for the manual tester who has a written requirement in hand and no cases for it yet.
katalon-labs/true-skills/.cursor/rules/exploratory-charter.mdc
Write, run, and debrief exploratory testing charters against Katalon True Platform/TestOps when there is no script to follow. Use when you need to turn a vague area into a charter (mission, areas, oracles, timebox), run a timeboxed unscripted session, log what you find as session notes, judge which findings are real defects, and promote what was learned into atomic manual cases plus the folder or suite that holds them. This is unscripted discovery and the debrief after it; when a written requirement is already in hand and the job is designing cases from it, use create-test-cases instead. Written for the manual tester who has an hour, a feature, and no cases to run against it.
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.
katalon-labs/true-skills/.cursor/rules/upload-report.mdc
Run automation and upload or verify Katalon Platform reports for Katalon Studio/KRE, JUnit XML, and Playwright reports. Use when you need to combine Katalon MCP project/result discovery with Katalon CLI execution, Katalon Report Uploader, or @katalon/playwright-reporter; configure report folders, report types, Platform/TestOps IDs, verify uploaded runs, handle failed auto-upload, or summarize execution results after automation completes. Written for the automation tester whose framework has already run and whose report is sitting on disk. If the Playwright run has not happened yet, start at playwright-execute.
lacymorrow/juno/.cursor/rules/enterprise-ai-agent-architecture.mdc
integrate_enterprise_tools(&mut self) -> Result<(), MCPError> { // Salesforce, ServiceNow, JIRA, Confluence, etc. self.register_enterprise_mcp_servers().await?; // Enable intelligent tool batching for 33% performance improvement self.enable_intelligent_batching().await
compnew2006/browser-controller/.cursor/rules/project.mdc
Core project context for browser-controller
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.