agentleFS
weirdgmeweirdgme/Claude-code-infrastructure-showcase/.claude/skills/api-engineering/SKILL.md

api-engineering

Skill4 starsChanged 12 months agoMITView on GitHub

Guide to API design patterns, GraphQL, gRPC, API gateways, rate limiting, and versioning strategies. Note: This is a foundational version. Community contributions welcome to expand coverage! Enable teams to design, build, and maintain robust, scalable APIs. Automatically activates when working on: - REST API design and best practices - GraphQL schema design - gRPC service definition - API gateway configuration (Kong, Ambassador) - API versioning strategies - Rate limiting and throttling - API security (OAuth2, JWT) ✅ Follow RESTful principles…

Files
SKILL.md

API Engineering

Guide to API design patterns, GraphQL, gRPC, API gateways, rate limiting, and versioning strategies.

Note: This is a foundational version. Community contributions welcome to expand coverage!

Purpose

Enable teams to design, build, and maintain robust, scalable APIs.

When to Use This Skill

Automatically activates when working on:

  • REST API design and best practices
  • GraphQL schema design
  • gRPC service definition
  • API gateway configuration (Kong, Ambassador)
  • API versioning strategies
  • Rate limiting and throttling
  • API security (OAuth2, JWT)

Quick Start Checklist

  • Define clear API contract (OpenAPI/GraphQL schema)
  • Implement authentication/authorization
  • Add rate limiting
  • Version your API
  • Document endpoints
  • Implement error handling
  • Add request validation

Resource Files

  • rest-api-design.md - RESTful principles, resource modeling, HTTP methods
  • graphql-patterns.md - Schema design, resolvers, N+1 problem, DataLoader
  • api-versioning.md - URI versioning, header versioning, strategies
  • rate-limiting.md - Token bucket, sliding window, distributed rate limiting

Best Practices

✅ Follow RESTful principles ✅ Use proper HTTP status codes ✅ Version your API from day one ✅ Implement rate limiting ✅ Validate input thoroughly ✅ Document with OpenAPI/GraphQL introspection ✅ Use API gateways for centralized concerns

Integration Points

  • backend-dev-guidelines: API implementation
  • documentation-as-code: API documentation
  • devsecops: API security
  • cloud-engineering: API Gateway services

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 🎯 SKILL ACTIVATED: api-engineering ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Total Resources: 4 foundational guides (community can expand!) Status: Basic coverage - contributions welcome

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.