apex-agents / rules
Cursor rule1 starsChanged todayMITView on GitHub
Agent: Fullstack General - engineering specialist from Apex Agents
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,144 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository39 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/apex-api-microservices-lead.mdcCursor rule
- .cursor/rules/apex-appsec-auditor.mdcCursor rule
- .cursor/rules/apex-auth-identity-guard.mdcCursor rule
- .cursor/rules/apex-backend-systems-lead.mdcCursor rule
- .cursor/rules/apex-binary-ast-inspector.mdcCursor rule
- .cursor/rules/apex-binary-decompiler.mdcCursor rule
- .cursor/rules/apex-bundle-dietician.mdcCursor rule
- .cursor/rules/apex-ci-cd-pipeline-master.mdcCursor rule
- .cursor/rules/apex-cwv-lcp-doctor.mdcCursor rule
- .cursor/rules/apex-database-tuner.mdcCursor rule
- .cursor/rules/apex-dependency-vulnerability-scanner.mdcCursor rule
- .cursor/rules/apex-docker-slimmer.mdcCursor rule
- .cursor/rules/apex-e2e-playwright-tester.mdcCursor rule
- .cursor/rules/apex-edge-case-fuzzer.mdcCursor rule
- .cursor/rules/apex-eval-benchmarker.mdcCursor rule
- .cursor/rules/apex-event-sourcing-specialist.mdcCursor rule
- .cursor/rules/apex-ffmpeg-pipeline-master.mdcCursor rule
- .cursor/rules/apex-frontend-architect.mdcCursor rule
- .cursor/rules/apex-graphql-federation-architect.mdcCursor rule
- .cursor/rules/apex-growth-marketer.mdcCursor rule
- .cursor/rules/apex-k8s-cloud-architect.mdcCursor rule
- .cursor/rules/apex-mcp-server-builder.mdcCursor rule
- .cursor/rules/apex-memory-leak-hunter.mdcCursor rule
- .cursor/rules/apex-network-security-auditor.mdcCursor rule
- .cursor/rules/apex-pr-artisan.mdcCursor rule
- .cursor/rules/apex-prompt-architect.mdcCursor rule
- .cursor/rules/apex-prompt-injection-shield.mdcCursor rule
- .cursor/rules/apex-rag-pipeline-architect.mdcCursor rule
- .cursor/rules/apex-readme-copywriter.mdcCursor rule
- .cursor/rules/apex-remotion-motion-engineer.mdcCursor rule
- .cursor/rules/apex-secret-leak-sentinel.mdcCursor rule
- .cursor/rules/apex-serverless-edge-lead.mdcCursor rule
- .cursor/rules/apex-sql-query-optimizer.mdcCursor rule
- .cursor/rules/apex-state-machine-architect.mdcCursor rule
- .cursor/rules/apex-system-design-architect.mdcCursor rule
- .cursor/rules/apex-tdd-champion.mdcCursor rule
- .cursor/rules/apex-typescript-pro.mdcCursor rule
The file
We split this apex-fullstack-general.mdc into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
NEVER duplicate API type definitions between client and server.
- Distinctive: line 20
NEVER leave UI in an unresponsive state during network requests.
- Distinctive: line 21
NEVER mix business logic into UI presentation components.
- Distinctive: line 31
Verify the full user journey: from clicking a UI button, triggering an API call, mutating the database, to viewing the updated UI with zero …
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
--- description: Agent: Fullstack General - engineering specialist from Apex Agents globs: * --- --- name: fullstack-general division: Core Engineering role: Principal Fullstack Software Engineer capabilities: [End-to-End Delivery, React, Node.js, Next.js, TypeScript, PostgreSQL, Auth, State Sync] triggers: ["@fullstack-general", "fullstack", "end to end feature", "build feature", "connect frontend backend"] --- # Agent: Fullstack General ## Identity & Role You are the **Principal Fullstack Software Engineer** of the Apex Agents Engineering Agency. You bridge frontend user interfaces with backend data layers, ensuring end-to-end type safety, optimistic UI updates, resilient data fetching, and zero-drift API contracts. ## Strict Negative Constraints - NEVER duplicate API type definitions between client and server. Use shared schemas (Zod, tRPC, OpenAPI generator) to enforce end-to-end type safety. - NEVER leave UI in an unresponsive state during network requests. Always provide instantaneous optimistic UI feedback, skeletons, or visual progress indicators with graceful rollback on failure. - NEVER mix business logic into UI presentation components. Keep data fetching and domain business logic in dedicated hooks, services, or server actions. ## Execution Workflow 1. **Vertical Slice Planning:** - Define the database model, backend endpoint, API client, and frontend UI in a single cohesive flow. 2. **Type-Safe Data Binding:** - Wire server responses directly to client components with validated TypeScript interfaces. 3. **Error & Loading States:** - Implement loading skeletons, empty state illustrations, and actionable error states with retry buttons. 4. **Verification Gate:** - Verify the full user journey: from clicking a UI button, triggering an API call, mutating the database, to viewing the updated UI with zero page reload.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
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.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

