javascript / rules
clerk/javascript/.cursor/rules/clerk-ui-theming.mdc
Styling and theming architecture for @clerk/ui package
No other project uses it yet
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.
clerk/javascript/.cursor/rules/clerk-ui-theming.mdc
Styling and theming architecture for @clerk/ui package
No other project uses it yet
clerk/javascript/.cursor/rules/development.mdc
best practices and conventions API Design Principles - Design APIs to be intuitive and self-documenting - Provide sensible defaults to minimize configuration - Support both imperative and declarative usage patterns - Maintain backward
No other project uses it yet
clerk/javascript/.cursor/rules/global.mdc
Development Workflow - Make changes in relevant package under packages/ - Follow established testing and documentation requirements - Use Changesets for version management and releases - If you are provided a commit SHA, always
No other project uses it yet
clerk/javascript/.cursor/rules/monorepo.mdc
Structure - `packages/` - All publishable packages - `integration/` - End-to-end tests and integration templates - `docs/` - Documentation and contribution guides - `scripts/` - Build and automation scripts - `tools/` - Internal development tools Development Workflow
No other project uses it yet
clerk/javascript/.cursor/rules/nextjs.mdc
next.js
No other project uses it yet
clerk/javascript/.cursor/rules/typescript.mdc
definitions ├── utils/ # Pure utility functions ├── hooks/ # Custom React hooks (if applicable) └── __tests__/ # Test files ``` Documentation Standards ```typescript /** * Calculates the total price including tax * @param basePrice - The base price before
No other project uses it yet
NVIDIA/Personal-AI-Router/.cursor/rules/architecture.mdc
Core PAIR boundaries for naming, communication, backend ownership, and reactive state
NVIDIA/Personal-AI-Router/.cursor/rules/communication-layers.mdc
Current renderer, Electron, broker, and node communication boundaries
NVIDIA/Personal-AI-Router/.cursor/rules/no-legacy-fallbacks.mdc
No legacy compatibility paths or dead fallback branches — greenfield codebase
NVIDIA/Personal-AI-Router/.cursor/rules/readme-ownership.mdc
Keep the root README focused on public app usage
NVIDIA/Personal-AI-Router/.cursor/rules/security.mdc
Security ownership boundary — the backend owns all cluster trust; PAIR implements none
NVIDIA/Personal-AI-Router/.cursor/rules/service-contracts.mdc
Verify desktop ↔ services JSON-RPC contracts and binary inventory parity
NVIDIA/Personal-AI-Router/.cursor/rules/system-architecture.mdc
Current PAIR runtime architecture, communication paths, modular services, and security boundaries
redwoodjs/sdk/.cursor/rules/sdk-dev.mdc
Rules on how to make changes to the rwsdk package (in sdk/ subdirectory)
Instawork/hyperview/.cursor/rules/alphabetical-sorting.md
Existing Patterns**: When breaking established patterns in legacy code would cause more harm ### Documentation Required When exceptions are made, document the reason: ```typescript // Order maintained for API compatibility
Brandawg93/PeaNUT/.cursor/rules/07-api-standards.mdc
API Development Standards
No other project uses it yet
AgentDock/AgentDock/.cursor/rules/agents.mdc
assets/` folder for icons/avatars. ``` agents/ └── [agent-name]/ ├── template.json # Core configuration (required) ├── README.md # Documentation (recommended) └── assets/ # Optional assets (e.g., avatar.png) ``` ## Template Configuration (`template.json`) - The `template.json` file defines the agent's identity
AgentDock/AgentDock/.cursor/rules/contributions.mdc
might already exist in the project root or within `agentdock-core/src/test/`. 5. **Update Documentation**: Ensure relevant documentation in `/docs` is updated (see `[docs.mdc](mdc:.cursor/rules/docs.mdc)` for guidelines). 6. **Commit
AgentDock/AgentDock/.cursor/rules/docs.mdc
description: globs: alwaysApply: false --- # Documentation Rules (`/docs`) This file provides guidelines for working with the documentation in the `/docs` directory. ## Documentation Structure The `/docs` directory is organized as follows: - `[docs/README.md
AgentDock/AgentDock/.cursor/rules/nodes.mdc
formatting ## Directory Structure The actual `/src/nodes` directory contains: - `[README.md](mdc:src/nodes/README.md)`: Overview and architecture documentation - `[custom-tool-contributions.md](mdc:src/nodes/custom-tool-contributions.md)`: Detailed guide for contributors - `[registry.ts](mdc:src/nodes/registry.ts)`: Node registration system - `[init.ts
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.