IsaacSim / rules
isaac-sim/IsaacSim/.cursor/rules/modules_changelog.mdc
Changelog rules for independently shipped libraries under source/libraries
Steady2 mentions in 2 weeks
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.
isaac-sim/IsaacSim/.cursor/rules/modules_changelog.mdc
Changelog rules for independently shipped libraries under source/libraries
Steady2 mentions in 2 weeks
No other project uses it yet
isaac-sim/IsaacSim/.cursor/rules/pip_packaging.mdc
Creating standalone pip packages from Kit extensions using in-place pyproject.toml
isaac-sim/IsaacSim/.cursor/rules/python_codestyle.mdc
This rule file should be used for Python code development
Steady2 mentions in 2 weeks
No other project uses it yet
isaac-sim/IsaacSim/.cursor/rules/python_docstrings.mdc
Python API docstrings in Python source and native binding definitions
Steady2 mentions in 2 weeks
No other project uses it yet
lilishop/lilishop/.cursor/rules/03-development-guidelines.mdc
Store sensitive configuration in environment variables 4. Never commit sensitive credentials to version control ## Testing 1. Write unit tests for critical business logic 2. Ensure API endpoints are properly documented
No other project uses it yet
johnlindquist/kit/.cursor/rules/derived-cursor-rules.mdc
AI rules derived by SpecStory from the project AI interaction history
No other project uses it yet
johnlindquist/kit/.cursor/rules/kit-development.mdc
description: globs: alwaysApply: true --- # Kit Development Guide This guide provides instructions for building, testing, and working with the Kit codebase. ## Testing Tests are written using `ava` and follow the `*.test.ts
No other project uses it yet
johnlindquist/kit/.cursor/rules/_testing.mdc
description: globs: alwaysApply: true --- ## Follow patterns ".test.ts" and "ava" for writing tests. ## Run all the tests `pnpm ava` ## Run a single test, e.g., src/core/env-safety.test.ts `pnpm ava src/core/env-safety.test.ts` ## Build. Ask first
No other project uses it yet
groupultra/telegram-search/.cursor/rules/architecture.mdc
lint # ESLint 检查 pnpm run lint:fix # 自动修复 pnpm run typecheck # 类型检查 pnpm run test run # 运行测试 ``` ## 配置文件 ### 环境配置 - **浏览器模式**: `.env` 文件 - `VITE_TELEGRAM_API_ID` - `VITE_TELEGRAM_API_HASH
No other project uses it yet
groupultra/telegram-search/.cursor/rules/contributing.mdc
refactor per PR. - Mechanical renames and large formatting should be isolated from behavioral changes. - Tests: - Add or update tests alongside behavior changes, especially for core and DB logic
groupultra/telegram-search/.cursor/rules/db.mdc
Make migrations forward-only and additive when possible. - Avoid destructive operations without a clear, tested migration path. - If a generated migration needs manual tweaks: - Keep custom SQL focused and well
groupultra/telegram-search/.cursor/rules/testing.mdc
globs: **/*.spec.ts, **/*.test.ts, vitest.config.ts, packages/**/vitest.config.ts --- ## Testing (Vitest) - **Goal**: Fast, reliable tests that validate behavior at the event and DB boundary, not implementation details. ### General Guidelines - Use **Vitest** consistently; avoid
chartbrew/chartbrew/.cursor/rules/10-spec-workflow.mdc
Spec-first workflow the agent can attach when relevant
No other project uses it yet
chartbrew/chartbrew/.cursor/rules/11-spec-template.mdc
Insert a Feature Spec file template
No other project uses it yet
chartbrew/chartbrew/.cursor/rules/20-implement-from-spec.mdc
Implement changes directly from the latest Feature Spec with minimal diffs
chartbrew/chartbrew/.cursor/rules/22-specless-fast-path.mdc
Implement tiny changes without a full spec
chartbrew/chartbrew/.cursor/rules/30-review-guardrails.mdc
Review guardrails for specs, correct PRs
TransformerLensOrg/TransformerLens/.cursor/rules/transformerlens.mdc
TransformerLens project conventions for Cursor agents.
No other project uses it yet
t3-oss/t3-env/.cursor/rules/general.mdc
your changes confirm to the project lint configuration by running `bun run lint`. - Write tests for changes and validate they pass using `bun run test`. ## Code Review Checklist - Ensure proper
Steady4 mentions in 2 weeks
No other project uses it yet
OpnForm/OpnForm/.cursor/rules/back-end.mdc
Laravel Back-end
No other project uses it yet
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.