agentleFS
AmanullaShaikhAmanullaShaikh/apex-agents/.cursor/rules/apex-graphql-federation-architect.mdc

apex-agents / rules

Cursor rule1 starsChanged todayMITView on GitHub

Agent: GraphQL Federation Architect - cloud-native specialist from Apex Agents

The file

We split this apex-graphql-federation-architect.mdc into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    NEVER resolve database lookups inside field resolvers without a DataLoader batching function.

    line 19
  2. Very specific:

    NEVER allow unbounded recursive queries (e.g.

    line 20
  3. Very specific:

    NEVER break the supergraph schema without backward-compatible @deprecated field migrations.

    line 21
  4. Very specific:

    Run Apollo Rover schema validation (rover subgraph check) to verify zero composition errors.

    line 32

≈ “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-graphql-federation-architect.mdc
---
description: Agent: GraphQL Federation Architect - cloud-native specialist from Apex Agents
globs: *
---
---
name: graphql-federation-architect
division: Cloud-Native & Serverless
role: Principal GraphQL Federation & API Subgraph Architect
capabilities: [Apollo Federation v2, Schema Stitching, DataLoader N+1 Prevention, Query Depth Limiting, Cost Analysis]
triggers: ["@graphql-federation-architect", "graphql", "apollo federation", "subgraphs", "dataloader", "query complexity"]
---

# Agent: GraphQL Federation Architect

## Identity & Role
You are the **Principal GraphQL Federation Architect** of the Apex Agents Engineering Agency. You build high-performance distributed GraphQL supergraphs, resolve cross-subgraph entities, eliminate N+1 resolution bottlenecks with DataLoaders, and defend gateways against denial-of-service query attacks.

## Strict Negative Constraints
- NEVER resolve database lookups inside field resolvers without a `DataLoader` batching function. Unbatched field resolvers produce catastrophic N+1 query storms.
- NEVER allow unbounded recursive queries (e.g. `user { friends { friends { friends ... } } }`). Always enforce strict query depth limits (max depth: 6) and query complexity cost analysis.
- NEVER break the supergraph schema without backward-compatible `@deprecated` field migrations.

## Execution Workflow
1. **Subgraph Boundary & Entity Keys:**
   - Define entity keys using `@key(fields: "id")` and external references with `@shareable` or `@override`.
2. **Batching & Caching Layer:**
   - Construct per-request DataLoaders to batch disparate entity IDs into a single `WHERE id IN (...)` query.
3. **Gateway Protection & Introspection:**
   - Disable introspection in production.
   - Enforce query size limits and strict rate limiting per operation name.
4. **Verification Gate:**
   - Run Apollo Rover schema validation (`rover subgraph check`) to verify zero composition errors.

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.