Claude Cursor opencode Skill

api-patterns

API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download vodailocz-kilo-kit-mcp-skills_engineering_api-patterns-0448e6c.zip · 9 KB

Install

skills CLI npx skills add https://github.com/VoDaiLocz/kilo-kit-mcp/tree/main/skills/engineering/api-patterns
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vodailocz-kilo-kit-mcp@llmmart
Git git clone https://github.com/VoDaiLocz/kilo-kit-mcp.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vodailocz/kilo-kit-mcp collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

API Patterns

API design principles and decision-making for 2025. Learn to THINK, not copy fixed patterns.

🎯 Selective Reading Rule

Read ONLY files relevant to the request! Check the content map, find what you need.


📑 Content Map

File Description When to Read
api-style.md REST vs GraphQL vs tRPC decision tree Choosing API type
rest.md Resource naming, HTTP methods, status codes Designing REST API
response.md Envelope pattern, error format, pagination Response structure
graphql.md Schema design, when to use, security Considering GraphQL
trpc.md TypeScript monorepo, type safety TS fullstack projects
versioning.md URI/Header/Query versioning API evolution planning
auth.md JWT, OAuth, Passkey, API Keys Auth pattern selection
rate-limiting.md Token bucket, sliding window API protection
documentation.md OpenAPI/Swagger best practices Documentation
security-testing.md OWASP API Top 10, auth/authz testing Security audits

🔗 Related Skills

Need Skill
API implementation @[skills/backend-development]
Data structure @[skills/database-design]
Security details @[skills/security-hardening]

✅ Decision Checklist

Before designing an API:

  • Asked user about API consumers?
  • Chosen API style for THIS context? (REST/GraphQL/tRPC)
  • Defined consistent response format?
  • Planned versioning strategy?
  • Considered authentication needs?
  • Planned rate limiting?
  • Documentation approach defined?

❌ Anti-Patterns

DON'T:

  • Default to REST for everything
  • Use verbs in REST endpoints (/getUsers)
  • Return inconsistent response formats
  • Expose internal errors to clients
  • Skip rate limiting

DO:

  • Choose API style based on context
  • Ask about client requirements
  • Document thoroughly
  • Use appropriate status codes

Script

Script Purpose Command
scripts/api_validator.py API endpoint validation python scripts/api_validator.py <project_path>
Files (kilo-kit-mcp)
  • scripts
    • api_validator.py 7.4 KB
      Loading…
  • api-style.md 1.1 KB
    Loading…
  • auth.md 576 B
    Loading…
  • documentation.md 549 B
    Loading…
  • graphql.md 977 B
    Loading…
  • rate-limiting.md 726 B
    Loading…
  • response.md 921 B
    Loading…
  • rest.md 1.3 KB
    Loading…
  • security-testing.md 2.8 KB
    Loading…
  • SKILL.md 2.4 KB
    ---
    name: api-patterns
    description: API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
    allowed-tools: Read, Write, Edit, Glob, Grep
    ---
    
    # API Patterns
    
    > API design principles and decision-making for 2025.
    > **Learn to THINK, not copy fixed patterns.**
    
    ## 🎯 Selective Reading Rule
    
    **Read ONLY files relevant to the request!** Check the content map, find what you need.
    
    ---
    
    ## 📑 Content Map
    
    | File | Description | When to Read |
    |------|-------------|--------------|
    | `api-style.md` | REST vs GraphQL vs tRPC decision tree | Choosing API type |
    | `rest.md` | Resource naming, HTTP methods, status codes | Designing REST API |
    | `response.md` | Envelope pattern, error format, pagination | Response structure |
    | `graphql.md` | Schema design, when to use, security | Considering GraphQL |
    | `trpc.md` | TypeScript monorepo, type safety | TS fullstack projects |
    | `versioning.md` | URI/Header/Query versioning | API evolution planning |
    | `auth.md` | JWT, OAuth, Passkey, API Keys | Auth pattern selection |
    | `rate-limiting.md` | Token bucket, sliding window | API protection |
    | `documentation.md` | OpenAPI/Swagger best practices | Documentation |
    | `security-testing.md` | OWASP API Top 10, auth/authz testing | Security audits |
    
    ---
    
    ## 🔗 Related Skills
    
    | Need | Skill |
    |------|-------|
    | API implementation | `@[skills/backend-development]` |
    | Data structure | `@[skills/database-design]` |
    | Security details | `@[skills/security-hardening]` |
    
    ---
    
    ## ✅ Decision Checklist
    
    Before designing an API:
    
    - [ ] **Asked user about API consumers?**
    - [ ] **Chosen API style for THIS context?** (REST/GraphQL/tRPC)
    - [ ] **Defined consistent response format?**
    - [ ] **Planned versioning strategy?**
    - [ ] **Considered authentication needs?**
    - [ ] **Planned rate limiting?**
    - [ ] **Documentation approach defined?**
    
    ---
    
    ## ❌ Anti-Patterns
    
    **DON'T:**
    - Default to REST for everything
    - Use verbs in REST endpoints (/getUsers)
    - Return inconsistent response formats
    - Expose internal errors to clients
    - Skip rate limiting
    
    **DO:**
    - Choose API style based on context
    - Ask about client requirements
    - Document thoroughly
    - Use appropriate status codes
    
    ---
    
    ## Script
    
    | Script | Purpose | Command |
    |--------|---------|---------|
    | `scripts/api_validator.py` | API endpoint validation | `python scripts/api_validator.py <project_path>` |
    
    
  • trpc.md 801 B
    Loading…
  • versioning.md 651 B
    Loading…

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.