discover-api
Automatically discover API design skills when working with REST APIs, GraphQL schemas, API authentication, OAuth, JWT, rate limiting, API versioning, error handling, or endpoint design. Activates for backend API development tasks.
What this skill does
# API Skills Discovery Provides automatic access to comprehensive API design, authentication, and implementation skills. ## When This Skill Activates This skill auto-activates when you're working with: - REST API design and implementation - GraphQL schema design - API authentication (JWT, OAuth 2.0, API keys, sessions) - API authorization (RBAC, ABAC, permissions) - Rate limiting and throttling - API versioning strategies - Error handling and validation - HTTP methods, status codes, endpoints ## Available Skills ### Quick Reference The API category contains 8 specialized skills: 1. **rest-api-design** - RESTful resource modeling, HTTP semantics, URL conventions 2. **graphql-schema-design** - GraphQL types, resolvers, N+1 problem prevention 3. **api-authentication** - JWT, OAuth 2.0, API keys, session management 4. **api-authorization** - RBAC, ABAC, policy engines, permission systems 5. **api-rate-limiting** - Token bucket, sliding window, rate limiting algorithms 6. **api-versioning** - API versioning, deprecation, backward compatibility 7. **api-error-handling** - RFC 7807 errors, validation, standardized responses 8. **api-design-rules** - 35 opinionated rules for API design ### Load Full Category Details For complete descriptions and workflows: Read ../api/INDEX.md This loads the full API category index with: - Detailed skill descriptions - Usage triggers for each skill - Common workflow combinations - Cross-references to related skills ### Load Specific Skills Load individual skills as needed: # Core API design Read ../api/rest-api-design.md Read ../api/graphql-schema-design.md # Security and access control Read ../api/api-authentication.md Read ../api/api-authorization.md # Production hardening Read ../api/api-rate-limiting.md Read ../api/api-error-handling.md Read ../api/api-versioning.md # Rules and best practices Read ../api/api-design-rules.md ## Common Workflows ### New REST API **Sequence**: REST design → Authentication → Authorization Read ../api/rest-api-design.md # Resource modeling, HTTP methods Read ../api/api-authentication.md # User authentication Read ../api/api-authorization.md # Access control ### New GraphQL API **Sequence**: GraphQL schema → Authentication → Authorization Read ../api/graphql-schema-design.md # Schema design, resolvers Read ../api/api-authentication.md # User authentication Read ../api/api-authorization.md # Field-level permissions ### API Hardening **Sequence**: Rate limiting → Error handling → Versioning Read ../api/api-rate-limiting.md # Prevent abuse Read ../api/api-error-handling.md # Standardized errors Read ../api/api-versioning.md # Manage evolution ### Complete API Stack **Full implementation from scratch**: # 1. Design phase Read ../api/rest-api-design.md # 2. Security phase Read ../api/api-authentication.md Read ../api/api-authorization.md Read ../api/api-rate-limiting.md # 3. Production readiness Read ../api/api-error-handling.md Read ../api/api-versioning.md ## Skill Selection Guide **Choose REST API skills when:** - Building traditional web services - Need simple CRUD operations - Working with mobile apps or SPAs - Require caching and HTTP semantics **Choose GraphQL skills when:** - Clients need flexible data fetching - Reducing over-fetching or under-fetching - Building aggregation layers - Need strong typing for APIs **Authentication vs Authorization:** - **Authentication** (api-authentication.md): Who are you? (Login, JWT, OAuth) - **Authorization** (api-authorization.md): What can you do? (Permissions, RBAC) **Production considerations:** - Always implement rate limiting for public APIs - Use versioning from day one - Standardize error responses early ## Integration with Other Skills API skills commonly combine with: **Database skills** (`discover-database`): - API endpoints → Database queries - Connection pooling for API servers - Query optimization for API performance **Testing skills** (`discover-testing`): - Integration tests for API endpoints - Contract testing for API consumers - Load testing for API performance **Frontend skills** (`discover-frontend`): - API client libraries - Data fetching patterns - Error handling in UI **Infrastructure skills** (`discover-infra`, `discover-cloud`): - API deployment strategies - Load balancing and scaling - API gateways and proxies ## Usage Instructions 1. **Auto-activation**: This skill loads automatically when Claude Code detects API-related work 2. **Browse skills**: Run `Read ../api/INDEX.md` for full category overview 3. **Load specific skills**: Use bash commands above to load individual skills 4. **Follow workflows**: Use recommended sequences for common API patterns 5. **Combine skills**: Load multiple skills for comprehensive coverage ## Progressive Loading This gateway skill (~200 lines, ~2K tokens) enables progressive loading: - **Level 1**: Gateway loads automatically (you're here now) - **Level 2**: Load category INDEX.md (~3K tokens) for full overview - **Level 3**: Load specific skills (~2-3K tokens each) as needed Total context: 2K + 3K + skill(s) = 5-10K tokens vs 25K+ for entire index. ## Quick Start Examples **"Design a REST API for a blog"**: Read ../api/rest-api-design.md **"Add OAuth authentication to my API"**: Read ../api/api-authentication.md **"Implement role-based access control"**: Read ../api/api-authorization.md **"Prevent API abuse"**: Read ../api/api-rate-limiting.md **"Design an API versioning strategy"**: Read ../api/api-versioning.md **Next Steps**: Run `Read ../api/INDEX.md` to see full category details, or load specific skills using the bash commands above.
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.