ai-rules-builder / rules
przeprogramowani/ai-rules-builder/.cursor/rules/vitest-unit-testing.mdc
Unit testing with Vitest and React Testing Library
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.
przeprogramowani/ai-rules-builder/.cursor/rules/vitest-unit-testing.mdc
Unit testing with Vitest and React Testing Library
marianfoo/mcp-sap-docs/.cursor/rules/60-adding-github-sources.mdc
json { "id": "ui5-typescript", "type": "documentation", "lang": "en", "boost": 0.1, "tags": ["ui5", "typescript", "types", "frontend"], "description": "UI5 TypeScript", "libraryId": "/ui5-typescript", "sourcePath": "ui5-typescript", "baseUrl": "https://github.com/UI5/typescript/blob/gh-pages", "pathPattern": "/{file}", "anchorStyle
WrBug/PolyHermes/.cursor/rules/frontend.mdc
alwaysApply: true path: frontend/** --- # 前端开发规范 ## 核心原则 - **禁止**在代码中添加 TODO/FIXME/XXX 注释 - **禁止**使用 `any` 类型 - **禁止**硬编码中文或英文文本 - **必须**支持移动端和桌面端 ## 技术栈 - **框架**: React + TypeScript - **UI 库**: Ant Design(移动端使用 Ant Design Mobile
databrickslabs/ontos/.cursor/rules/03-system-components-and-requirements.mdc
name: System Components and Requirements priority: 90 scope: globs: ["**/*"] --- ### System Components & Requirements - **Frontend:** Each feature has a dedicated React View (`src/frontend/src/views`). - **Backend:** Each feature has a dedicated FastAPI router (`src/backend/src/routes
databrickslabs/ontos/.cursor/rules/05-code-style-and-structure.mdc
manager getters in route files). Managers are initialized as singletons in `app.state` during startup. **Frontend (TypeScript/React)** - **TypeScript**: Use strictly with explicit types. `type` and `interface` are both fine — pick whichever
databrickslabs/ontos/.cursor/rules/08-testing-and-deployment.mdc
scope: globs: ["**/*"] --- ### Testing and Deployment **Local development** - Backend (FastAPI/Uvicorn) runs on **port 8000**. Frontend (Vite) runs on **port 3000**. - Both servers run in dev mode with auto-reload. **NEVER restart
databrickslabs/ontos/.cursor/rules/09-package-management.mdc
scope: globs: ["src/**", "package.json", "package-lock.json"] languages: ["typescript"] --- ### Package Management - This project uses **npm** for frontend package management. Use `npm install`, `npm ci`, `npm install `, `npm uninstall
databrickslabs/ontos/.cursor/rules/10-entity-panel-matrix.mdc
access control | | `agreements` / `agreement_wizard_sessions` | Approval workflows | | `business_owners` | Owner assignments | --- ## 2. Reusable Frontend Panels | Panel Component | File | Key Props | |---|---|---| | `EntityCostsPanel` | `components/costs/entity-costs-panel.tsx` | `entityType`, `entityId` | | `EntityQualityPanel` | `components/quality/entity-quality-panel.tsx` | `entityType`, `entityId`, `productAggregation
OWASP/OpenCRE/.cursor/rules/complete-ticket.mdc
Requires complete tickets before coding - asks clarifying questions if requirements are missing
OWASP/OpenCRE/.cursor/rules/requirements-gate.mdc
Stop and ask clarifying questions before coding when requirements are incomplete
OWASP/OpenCRE/.cursor/rules/verifiable-goals.mdc
Non-negotiable lint, mypy, test, and CI checks with evidence in handoff
atbe/atbe-1000x-developer-next-expo-starter-project/.cursor/rules/general-rules.mdc
service layout All API services are defined in the `packages/api` package. ### tRPC All frontend to backend communication must be facilitated using the `tRPC` routers. When exposing a method
PGshen/thinking-map/.cursor/rules/project-rule.mdc
Overview This is a thinking map application with a Go backend (server/) and Next.js frontend (web/). The project uses modern development practices with TypeScript, shadcn/ui, Zustand, and ReactFlow
syofyanzuhad/uptime-kita/.cursor/rules/laravel-boost.mdc
base folders without approval. - Do not change the application's dependencies without approval. ## Frontend Bundling - If the user doesn't see a frontend change reflected in the UI, it could
mcp-shark/mcp-shark/.cursor/rules/CODING_RULES.md
contains all coding rules and standards for the chase-functions project (both backend and frontend). These rules must be followed in all code implementations. ## General Rules (Apply to Both Backend
Dicklesworthstone/ultimate_mcp_client/.cursor/rules/02-mcp-client-architecture.mdc
REST API - WebSockets for bidirectional real-time chat - Alpine.js, Tailwind CSS, and DaisyUI for frontend - Multiple themes with light/dark mode support ## Resilience Features ### STDIO Safety Mechanisms - StdioProtectionWrapper: Wraps sys.stdout
Dicklesworthstone/ultimate_mcp_client/.cursor/rules/07-web-interface.mdc
bidirectional real-time communication - Uvicorn as the ASGI server - API endpoints for programmatic access ### Frontend - Alpine.js for lightweight reactivity - Tailwind CSS and DaisyUI for styling - Marked.js for Markdown rendering - Highlight.js
ryandaaa/siakad/.cursor/rules/laravel-boost.mdc
base folders without approval. - Do not change the application's dependencies without approval. ## Frontend Bundling - If the user doesn't see a frontend change reflected in the UI, it could
madebyaris/advance-minimax-m3-cursor-rules/.cursor/rules/cursor-tools-mastery.mdc
Cursor 3.7 runtime guide: choose the right tool, canvases, Design Mode, /worktree, /best-of-n, Await, and parallel execution where safe.
pr-pm/prpm/.cursor/rules/creating-agents-md.mdc
Creating agents.md files with plain markdown format (NO frontmatter) - use when creating agents.md packages for PRPM or generating project context files
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.