markdown-site / rules
waynesutton/markdown-site/.cursor/rules/convex-doctor.mdc
Convex doctor code quality standards maintained at 100/100 score
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.
waynesutton/markdown-site/.cursor/rules/convex-doctor.mdc
Convex doctor code quality standards maintained at 100/100 score
waynesutton/markdown-site/.cursor/rules/convex-write-conflicts.mdc
Guidelines for preventing write conflicts when using React, useEffect, and Convex
waynesutton/markdown-site/.cursor/rules/sec-check.mdc
Security Guidelines for markdown-blog This document covers security patterns specific to the markdown-blog application, a Convex-powered blog with no authentication. ## App-Specific Security Context ### Architecture - **Frontend**: Vite
adaline/gateway/.cursor/rules/gateway.mdc
return this.pool.pop()!; } return this.createResource(); } release(resource: T): void { if (this.pool.length < this.maxSize) { this.pool.push(resource); } } } ``` ## Security Considerations ### 1. Input Sanitization ```typescript // Always sanitize user inputs function sanitizeInput(input: string): string { return input
adaline/gateway/.cursor/rules/main.mdc
files, PascalCase for classes 5. **Group Related Files**: Keep related functionality together ### 6. Performance & Security #### Rules - **ALWAYS** implement proper caching strategies - **ALWAYS** use queues for rate limiting and concurrency control
adaline/gateway/.cursor/rules/provider.mdc
failing endpoints - **ALWAYS** provide fallback mechanisms when possible - **ALWAYS** monitor provider health and performance ## Security Considerations ### 1. API Key Management - **ALWAYS** validate API keys before use - **ALWAYS** never
adaline/gateway/.cursor/rules/providers.mdc
failing endpoints - **ALWAYS** provide fallback mechanisms when possible - **ALWAYS** monitor provider health and performance ## Security Considerations ### 1. API Key Management - **ALWAYS** validate API keys before use - **ALWAYS** never
evenfire-ai/evenfire/.cursor/rules/minikube-t2-harness.mdc
Keep the Minikube T2 harness, its contract tests, docs, rule, and skill in sync when editing harness code
vltpkg/vltpkg/.cursor/rules/install-build-phases.mdc
Phased install/build model and install command options
vltpkg/vltpkg/.cursor/rules/registries-and-auth.mdc
Multi-registry support and authentication system
skaldlabs/skald/.cursor/rules/style.mdc
Codebase styles and patterns
openshift/hypershift/.cursor/rules/create-jira-items.mdc
This rule is helpful when a user asks to create features, epics, stories, tasks, or bug tickets. This rule is also helpful when a user asks to create content for either a features, epics, stories, tasks, or bug tickets.
tetherto/pearpass-app-desktop/.cursor/rules/use-ui-kit.mdc
Rules for building and editing UI in this repo. The repo uses @tetherto/pearpass-lib-ui-kit as the single source for UI primitives — do not roll custom buttons, inputs, modals, typography, or icons. Covers component catalog, props (modern vs deprecated), theming conventions, a cookbook of common patterns, and anti-patterns to avoid. Mirror of .claude/skills/use-ui-kit/SKILL.md — keep in sync.
vibeeval/vibecosystem/.cursor/rules/agent-development.mdc
Rules for creating and editing vibecosystem agent definitions
vibeeval/vibecosystem/.cursor/rules/general.mdc
vibecosystem core coding standards and quality rules
solana-foundation/solana-com/.cursor/rules/nextjs-standards.mdc
Error { cause?: unknown }`). - Wrap async operations in `try/catch`; surface via an error boundary. ### Performance & security - Enable **Content-Security-Policy**, **X-Frame-Options**, **Strict-Transport-Security** headers. - Strip unreachable code with
MHaggis/Security-Detections-MCP/.cursor/rules/contentctl-path.mdc
contentctl tool location and usage (Splunk-specific). For other SIEM validation tools, see validation-tools.mdc.
MHaggis/Security-Detections-MCP/.cursor/rules/detection-validation.mdc
Extensions` - file: `windows_embargo_ransomware_file_extensions.yml` ## Quick Validation Run the appropriate validator before committing: **Splunk**: ```bash cd $SECURITY_CONTENT_PATH source venv/bin/activate && contentctl validate ``` **Sigma**: ```bash sigma convert -t splunk -p sysmon rule.yml
MHaggis/Security-Detections-MCP/.cursor/rules/validation-tools.mdc
Detection validation tools - location, usage, and multi-SIEM support
leancoderkavy/premiere-pro-mcp/.cursor/rules/output-style.mdc
Always-on caveman wording and ADHD-shaped replies for every folder in this workspace.
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.