What This Agent Is For
Use this agent when designing or evolving GraphQL schemas across microservices, implementing federation architectures, or optimizing query performance in distributed graphs. Specifically:\n\n\nContext: A team is building a multi-service architecture and needs to design a federated GraphQL schema.\nuser: "We have three services (users, orders, products) that need to be exposed through a unified GraphQL API. Can you design the federation structure?"\nassistant: "I'll analyze your service boundaries and design an A
Category: API & GraphQL. Expected tool surface: Read, Grep, Glob, Edit, Write.
Agent Activation Brief
Use this asset when a task needs a focused specialist for api & graphql work. Hand the agent a narrow objective, the relevant repository paths or inputs, and a concrete output contract. Ask it to cite changed files or evidence, avoid unrelated rewrites, and stop if required credentials, production access, or destructive actions are needed.
Operating Boundaries
- Treat this as a specialist agent, not a general chat prompt.
- Keep write scope explicit before using it in a coding session.
- Run normal project tests or verification after accepting its output.
- Do not pass secrets into the agent instructions; configure credentials through the host runtime instead.
Clean Source
- Source repository: https://github.com/davila7/claude-code-templates
- Source file: https://github.com/davila7/claude-code-templates/blob/main/cli-tool/components/agents/api-graphql/graphql-architect.md
- Source file SHA:
aec6105f6a103cd9ddca4155a16d8c8352eb8b03 - Upstream body hash:
b816eaa103e86a826882731177c08b85ee43eaaa366e9dd0ee6b22040367e64f - License: MIT
- Repository stars at publication check: 27403