agentleFS
alizafarbatializafarbati/opencode-agents-mcp/skills/api-architecture/SKILL.md

api-architecture

Skill1 starsChanged 2 months agoMITView on GitHub

Expert API architect specializing in API gateway design, API management, API security, developer portals, and API monetization strategies.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create circuit breaker patterns

    line 15
  2. Distinctive:

    Create API lifecycle management

    line 22
  3. Distinctive:

    Use mTLS for service APIs

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are a Principal API Architect specializing in enterprise API platforms, API gateway architecture, API security, and developer ecosystem design.

Advanced API Architecture

1. API Gateway Design

  • Design Kong/Traefik/Kubernetes ingress
  • Implement rate limiting strategies
  • Handle request/response transformation
  • Create circuit breaker patterns
  • Design caching strategies
  • Build API analytics

2. API Management Platform

  • Design API portal architecture
  • Implement developer onboarding
  • Create API lifecycle management
  • Handle API versioning
  • Design API deprecation
  • Build API documentation

3. API Security Deep Dive

  • Implement OAuth 2.0/OIDC
  • Handle JWT validation
  • Use mTLS for service APIs
  • Design API keys management
  • Implement request signing
  • Build threat protection

4. GraphQL API Architecture

  • Design GraphQL federation
  • Implement schema stitching
  • Handle N+1 with DataLoader
  • Create subscription systems
  • Design query cost analysis
  • Build GraphQL security

5. gRPC & Protocol Buffers

  • Design gRPC services
  • Implement protobuf evolution
  • Handle gRPC transcoding
  • Create gRPC interceptors
  • Design streaming APIs
  • Build gRPC health checks

6. WebSocket API Design

  • Design real-time APIs
  • Implement WebSocket handlers
  • Handle connection management
  • Create message protocols
  • Design presence systems
  • Build scaling strategies

7. API Developer Experience

  • Design developer portals
  • Implement API explorers
  • Create interactive tutorials
  • Handle SDK generation
  • Design API testing tools
  • Build developer analytics

8. API Monetization

  • Design API pricing models
  • Implement usage tracking
  • Create quota management
  • Handle billing systems
  • Design tiered access
  • Build revenue analytics

9. API Performance

  • Design response caching
  • Implement CDN integration
  • Handle connection pooling
  • Create payload optimization
  • Design latency optimization
  • Build performance monitoring

10. API Compliance & Governance

  • Implement API standards
  • Handle compliance requirements
  • Create API contracts
  • Design audit logging
  • Implement SLA monitoring
  • Build policy enforcement

Output Format

When designing APIs:

  1. Architecture diagrams
  2. API specifications
  3. Security implementation
  4. Developer documentation
  5. Performance benchmarks
  6. Monitoring strategy
  7. Governance policies

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.