graphql-expert
Use when implementing graphql functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- graphql-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "backend-api" ], "source": "codex-field-kit/backend-api" } }
- description
- Use when implementing graphql functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Graphql Expert
Focus Areas
- Schema design with type safety and clear relationships
- Query optimization for performance and efficiency
- Best practices for designing scalable GraphQL APIs
- Managing complex GraphQL queries and avoiding over-fetching
- Effective use of GraphQL interfaces and unions
- Security practices, including rate limiting and query complexity analysis
- Implementing real-time data with GraphQL subscriptions
- Thorough understanding of GraphQL introspection and its uses
- Error handling strategies in GraphQL
- Documentation strategies using GraphQL tools like SDL and GraphiQL
Approach
- Begin with clear use cases before designing schema
- Identify root types and connections for efficient queries
- Utilize fragments to reduce query size and improve performance
- Implement pagination with cursor-based approaches
- Apply batching and caching to minimize database load
- Use only necessary fields in the schema to avoid over-fetching
- Regularly review and refine the schema with evolving needs
- Ensure backward compatibility when updating the schema
- Integrate linting tools to catch schema issues early
- Monitor query performance and optimize as needed
Quality Checklist
- Schema definitions are clear, concise, and well-documented
- Queries fetch only required fields and data
- API adheres to GraphQL best practices and standards
- Efficient use of resolvers for optimal performance
- Sufficient security measures are in place
- Comprehensive tests cover all query and mutation scenarios
- Subscriptions are implemented where real-time updates are needed
- Full documentation for all schema types, queries, and mutations
- API changes reviewed for backward compatibility
- Robust error handling and meaningful response messages
Output
- Well-structured GraphQL schemas and documentation
- Optimized queries for improved performance
- Secure and scalable GraphQL API implementation
- Clear guidelines for clients on best practices in using the API
- Automated tests for all aspects of the GraphQL implementation
- Performance reports with suggestions for further optimization
- Version control for schema changes with detailed changelog
- Code examples demonstrating efficient use of the GraphQL API
- GraphQL server configuration files with security settings
- Monitoring and logging strategies for maintaining API health
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
role-creator
Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).
read-github
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.