Back to Rules
Backend
apex Cursor Rules
sahajamoth April 15, 2026
0 copies 0 downloads
This project uses APEX for code coverage analysis and security detection.
Rule Content
# APEX Coverage & Security Analysis This project uses APEX for code coverage analysis and security detection. ## When to use APEX - After writing or modifying code, run `apex_run` to check coverage gaps - Before committing, run `apex_detect` to check for security issues - When investigating a vulnerability, use `apex_reach` to find which entry points can reach it - In CI, use `apex_ratchet` to enforce minimum coverage ## Available MCP Tools - `apex_run` — coverage gap analysis (pass target path + language) - `apex_detect` — security findings with CWE IDs - `apex_reach` — reverse path from file:line to entry points - `apex_ratchet` — CI coverage gate (PASS/FAIL) - `apex_doctor` — check prerequisites - `apex_deploy_score` — deployment readiness 0-100 ## Supported Languages python, rust, javascript, typescript, java, kotlin, go, c, cpp, ruby, swift, csharp
Comments
More Rules
View allWeb Development
Next.js 15 + TypeScript Cursor Rules
Comprehensive .cursorrules file for Next.js 15 App Router projects with TypeScript, enforcing server components by default, proper use of "use client" directive, and App Router conventions.
C
CommunityBackend Development
Python FastAPI Best Practices Rules
Cursor rules for Python FastAPI projects enforcing async patterns, Pydantic v2 models, dependency injection, and proper error handling.
C
CommunityFrontend Development
React + TypeScript Component Rules
Rules for consistent React component development with TypeScript interfaces, proper hook patterns, and component composition.
C
CommunityAI/ML
Cursor Agent Mode Configuration
Rules optimizing Cursor Agent mode behavior including multi-file editing context, session management, and autonomous task completion patterns.
C
Cursor TeamFrontend Development
Tailwind CSS + shadcn/ui Rules
Cursor rules for projects using Tailwind CSS with shadcn/ui component library, enforcing consistent utility class usage and component patterns.
C
CommunityBackend Development
Go Backend Service Rules
Rules for Go backend services enforcing idiomatic Go patterns, proper error handling, and clean architecture conventions.
C
Community