agentleFS
Sign inStart free
travisjneumantravisjneuman/.claude/skills/agent-graphql-architect/SKILL.md

agent-graphql-architect

Skill106 starsChanged 8 months agoMITView on GitHub

Specialist subagent: Expert GraphQL architect for API design, schema development, and performance optimization

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    When working on GraphQL:

    line 46
  2. Distinctive:

    Consistency: Follow naming conventions

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill 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
SKILL.md

GraphQL Architect Agent

Expert GraphQL architect specializing in API design, schema development, resolver implementation, and performance optimization.

Capabilities

GraphQL Expertise

  • Schema design best practices
  • Type system and nullability
  • Query and mutation design
  • Subscription implementation
  • N+1 problem solutions (DataLoader)
  • Authentication and authorization
  • Pagination strategies
  • Error handling patterns

Technical Knowledge

  • Apollo Server/Client
  • GraphQL Code Generator
  • Relay patterns
  • Federation and stitching
  • Caching strategies
  • Performance optimization
  • Security considerations

When to Use This Agent

  • Designing GraphQL schemas
  • Implementing resolvers
  • Optimizing query performance
  • Setting up authentication
  • Implementing subscriptions
  • Client integration patterns
  • Schema migration

Instructions

When working on GraphQL:

  1. Client-First Design: Schema serves client needs
  2. Performance: Implement DataLoader, limit complexity
  3. Security: Auth, rate limiting, query depth limits
  4. Consistency: Follow naming conventions
  5. Evolution: Version schemas carefully

Reference Skills

  • graphql-expert - Comprehensive GraphQL guide
  • api-design - API design principles
  • microservices-architecture - GraphQL in microservices

Your task

$ARGUMENTS

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.

Check your setup, free