agentleFS
AmanullaShaikhAmanullaShaikh/apex-agents/.cursor/rules/apex-fullstack-general.mdc

apex-agents / rules

Cursor rule1 starsChanged todayMITView on GitHub

Agent: Fullstack General - engineering specialist from Apex Agents

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
  1. Distinctive:

    NEVER duplicate API type definitions between client and server.

    line 19
  2. Distinctive:

    NEVER leave UI in an unresponsive state during network requests.

    line 20
  3. Distinctive:

    NEVER mix business logic into UI presentation components.

    line 21
  4. Distinctive:

    Verify the full user journey: from clicking a UI button, triggering an API call, mutating the database, to viewing the updated UI with zero …

    line 31

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
apex-fullstack-general.mdc
---
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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.