agent-skills / rules
callstackincubator/agent-skills/.cursor/rules/react-native-best-practices.mdc
React Native performance — route to react-native-best-practices SKILL.md and profiling first
The rules real projects give Cursor's agent, from .cursor/rules.
callstackincubator/agent-skills/.cursor/rules/react-native-best-practices.mdc
React Native performance — route to react-native-best-practices SKILL.md and profiling first
langwatch/better-agents/.cursor/rules/coding-guidelines.mdc
Guiding principles: - Clean Code - SRP - YAGNI - KISS DIRECTIVES: - We want thin files that aim to have a single responsibility and a single export. - We should have a single export per file. - Files should be organized/grouped by feature - Code should be modular - Functions should be small - Classes should be small - functions, classes, methods should have TSDoc with example usage - top-level directories represent core features, and should each have a…
langwatch/better-agents/.cursor/rules/commit-and-push.mdc
Commit (conventional commit) files and push to the remote repository. Important: if not on main, propose to create a new branch and switch to it.
langwatch/better-agents/.cursor/rules/commit.mdc
git add commit ONLY the files you changed just now, write a commit message for it using conventional commits format DO NOT commit again automatically until I tell you so to do it again
langwatch/better-agents/.cursor/rules/correction-response.mdc
Respond to corrections by creating or updating rules
langwatch/better-agents/.cursor/rules/development-workflow.mdc
Development workflow and tooling guidelines
langwatch/better-agents/.cursor/rules/docs-directory.mdc
When writing documentation for the repository
langwatch/better-agents/.cursor/rules/propose-commit.mdc
After writing code
langwatch/better-agents/.cursor/rules/typescript-strict-typing.mdc
Enforce strict TypeScript typing without any types
langwatch/better-agents/.cursor/rules/unit-tests-todos.mdc
When proposing/writing unit test specs
akto-api-security/akto/.cursor/rules/akto-core-rules.mdc
No summary in the file. Open it to read it.
NVIDIA/Personal-AI-Router/.cursor/rules/absolute-imports.mdc
Use the `@/*` path alias instead of relative (`../`) imports across the codebase
NVIDIA/Personal-AI-Router/.cursor/rules/agent-onboarding.mdc
Read PAIR's rules and docs before changing desktop or services code
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/backend-constants.mdc
Prefer backend-reported values over hardcoded constants; keep the remaining backend-coupled constants in one canonical file
NVIDIA/Personal-AI-Router/.cursor/rules/build-and-typecheck.mdc
Build, typecheck, and the local gate to run before pushing; rules around .d.ts / tsbuildinfo files
NVIDIA/Personal-AI-Router/.cursor/rules/commit-sign-off.mdc
Sign off every commit with git commit -s; the DCO trailer must match the commit author
NVIDIA/Personal-AI-Router/.cursor/rules/communication-layers.mdc
Current renderer, Electron, broker, and node communication boundaries
NVIDIA/Personal-AI-Router/.cursor/rules/engines-vs-backends-naming.mdc
Use engine terminology in PAIR code and UI
NVIDIA/Personal-AI-Router/.cursor/rules/file-editing.mdc
Read-before-write rule — always Read a file before Write/StrReplace. No shell scripts to mutate code. No exceptions.
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.