Summary
This is for developers who need to build or work with GraphQL APIs and want to avoid the common production disasters. It covers schema design, resolver patterns, DataLoader for preventing N+1 queries, federation for microservices, and client integration with Apollo and urql. The sharp edges table is the real value here: it calls out critical issues like missing DataLoader causing database storms, unlimited query depth enabling DoS attacks, and the nullability propagation gotcha that can surprise you. The underlying philosophy is right: GraphQL is a contract, and your schema is your API documentation, so design it with intention. If you've ever watched a poorly designed GraphQL API melt under load, you'll recognize these lessons.
Install to Claude Code
npx -y skills add davila7/claude-code-templates --skill graphql --agent claude-codeInstalls into .claude/skills of the current project.
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
Files
SKILL.md
Select a file.
Featured
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
