go-graphql
Analyze Go GraphQL projects using gqlgen. Use when onboarding to Go GraphQL APIs, understanding schema design, analyzing resolver implementations, reviewing directive usage, examining dataloaders, identifying N+1 query patterns, and generating GraphQL API documentation.
What this skill does
## Purpose
Provide comprehensive analysis of Go GraphQL projects built with gqlgen to help developers quickly understand schema design, resolver patterns, and GraphQL-specific implementations. This skill leverages the graphql-architect agent for deep GraphQL analysis.
## When to Use
Use this skill when you need to:
- **Onboard to a gqlgen project** - Understand the full GraphQL API structure
- **Analyze schema design** - Review types, queries, mutations, subscriptions
- **Review resolver implementations** - Understand how queries are resolved
- **Examine directive usage** - Find custom directives and their handlers
- **Identify dataloaders** - Analyze batching and caching patterns
- **Detect N+1 problems** - Find potential performance issues
- **Document the GraphQL API** - Generate schema documentation
- **Understand federation** - Analyze Apollo Federation setup
## gqlgen Detection
### Identifying gqlgen Projects
Check for gqlgen markers:
```bash
# Check go.mod for gqlgen
grep "github.com/99designs/gqlgen" go.mod
# Find gqlgen config
find . -name "gqlgen.yml" -o -name "gqlgen.yaml" -o -name ".gqlgen.yml"
# Find generated files
find . -name "generated.go" -path "*/graph/*"
```
### gqlgen Project Structure
```
project/
├── graph/
│ ├── generated/ # Auto-generated code (DO NOT EDIT)
│ │ └── generated.go
│ ├── model/ # Generated and custom models
│ │ └── models_gen.go
│ ├── resolver.go # Root resolver
│ ├── schema.resolvers.go # Schema resolver implementations
│ └── schema.graphqls # GraphQL schema definition
├── gqlgen.yml # gqlgen configuration
└── server.go # Server entry point
```
## Analysis Checklist
### 1. Schema Analysis
```bash
# Find all schema files
find . -name "*.graphqls" -o -name "*.graphql"
# Count types, queries, mutations
grep -c "^type " *.graphqls
grep -c "^input " *.graphqls
grep -c "^enum " *.graphqls
grep -c "^interface " *.graphqls
# Find Query type
grep -A 50 "^type Query" *.graphqls
# Find Mutation type
grep -A 50 "^type Mutation" *.graphqls
# Find Subscription type
grep -A 20 "^type Subscription" *.graphqls
```
### 2. Resolver Analysis
```bash
# Find resolver files
find . -name "*resolver*.go"
# Find resolver struct
grep -rn "type Resolver struct" --include="*.go"
# Find query resolvers
grep -rn "func.*QueryResolver" --include="*.go"
# Find mutation resolvers
grep -rn "func.*MutationResolver" --include="*.go"
# Find field resolvers
grep -rn "func.*Resolver\)" --include="*.go" | grep -v "Query\|Mutation"
```
### 3. Directive Analysis
```bash
# Find directive definitions in schema
grep -rn "^directive @" --include="*.graphqls"
# Find directive implementations
grep -rn "DirectiveRoot" --include="*.go"
# Common directives
grep -rn "@auth\|@hasRole\|@deprecated\|@cacheControl" --include="*.graphqls"
```
### 4. Dataloader Analysis
```bash
# Find dataloader implementations
grep -rn "dataloader\|DataLoader\|Loader" --include="*.go"
# Find batch functions
grep -rn "func.*Batch\|func.*Load" --include="*.go"
# Check for dataloaden usage
grep "github.com/vektah/dataloaden" go.mod
```
### 5. Model Analysis
```bash
# Find model definitions
find . -name "*model*.go" -o -name "*models*.go"
# Find custom scalars
grep -rn "MarshalGQL\|UnmarshalGQL" --include="*.go"
# Find model bindings in gqlgen.yml
grep -A 20 "models:" gqlgen.yml
```
### 6. Subscription Analysis
```bash
# Find subscription resolvers
grep -rn "func.*SubscriptionResolver" --include="*.go"
# Find channel usage in subscriptions
grep -rn "chan.*<-\|<-chan" --include="*resolver*.go"
```
### 7. Federation Analysis (if applicable)
```bash
# Check for federation
grep -rn "@key\|@external\|@requires\|@provides" --include="*.graphqls"
# Find entity resolvers
grep -rn "func.*EntityResolver\|func.*Entity\(" --include="*.go"
# Check federation config
grep "federation:" gqlgen.yml
```
## gqlgen Configuration Analysis
Key sections in `gqlgen.yml`:
```yaml
# Schema location
schema:
- graph/*.graphqls
# Generated code output
exec:
filename: graph/generated/generated.go
package: generated
# Model generation
model:
filename: graph/model/models_gen.go
package: model
# Resolver configuration
resolver:
layout: follow-schema # or single-file
dir: graph
package: graph
# Model bindings (map GraphQL to Go types)
models:
ID:
model:
- github.com/99designs/gqlgen/graphql.ID
DateTime:
model:
- github.com/99designs/gqlgen/graphql.Time
# Federation v2
federation:
filename: graph/federation.go
package: graph
version: 2
```
## Common Patterns
### Resolver Pattern
See `reference/resolver-patterns.md` for detailed patterns.
```go
// Query resolver
func (r *queryResolver) Users(ctx context.Context) ([]*model.User, error) {
return r.UserService.List(ctx)
}
// Field resolver (for computed fields)
func (r *userResolver) FullName(ctx context.Context, obj *model.User) (string, error) {
return obj.FirstName + " " + obj.LastName, nil
}
```
### Dataloader Pattern
See `reference/dataloader-patterns.md` for detailed patterns.
```go
// Batch function
func (r *Resolver) UserLoader(ctx context.Context, keys []string) ([]*model.User, []error) {
users, err := r.UserService.GetByIDs(ctx, keys)
// Map results to match key order...
}
```
### Directive Pattern
See `reference/directive-patterns.md` for detailed patterns.
```go
// Auth directive
func Auth(ctx context.Context, obj interface{}, next graphql.Resolver) (interface{}, error) {
user := auth.ForContext(ctx)
if user == nil {
return nil, errors.New("unauthorized")
}
return next(ctx)
}
```
## Output Format
Generate a GraphQL API onboarding report with:
### 1. Schema Overview
- Total types, queries, mutations, subscriptions
- Custom scalars and enums
- Interface and union types
### 2. Schema Diagram (Mermaid)
Generate `docs/graphql-schema.md` with schema visualization:
```markdown
# GraphQL Schema
## Type Relationships
\`\`\`mermaid
<!-- See reference/schema-diagram.mmd -->
\`\`\`
## Operations
| Type | Operation | Return Type | Description |
|------|-----------|-------------|-------------|
| Query | users | [User!]! | List all users |
| Query | user(id: ID!) | User | Get user by ID |
| Mutation | createUser | User! | Create new user |
```
### 3. Resolver Map
- Query resolvers and their implementations
- Mutation resolvers
- Field resolvers (computed fields)
- Subscription resolvers
### 4. Directive Reference
- Custom directives and their purposes
- Directive handlers and implementations
### 5. Dataloader Analysis
- Identified dataloaders
- Batch functions
- Potential N+1 issues
### 6. Key Files
Recommended reading order:
1. `gqlgen.yml` - Configuration
2. `graph/schema.graphqls` - Schema definition
3. `graph/resolver.go` - Root resolver
4. `graph/schema.resolvers.go` - Resolver implementations
5. `graph/model/` - Data models
6. Directive handlers (if any)
7. Dataloader implementations (if any)
## Performance Checklist
- [ ] Dataloaders used for relationship loading
- [ ] No N+1 queries in field resolvers
- [ ] Query complexity/depth limits configured
- [ ] Proper error handling in resolvers
- [ ] Context cancellation handled
- [ ] Subscriptions properly cleaned up
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.