api-patterns

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

65 stars

Best use case

api-patterns is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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

Teams using api-patterns should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/api-patterns/SKILL.md --create-dirs "https://raw.githubusercontent.com/One-Man-Company/Skills-ContextManager/main/MySkillsHUB/skills/api-patterns/skill.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/api-patterns/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How api-patterns Compares

Feature / Agentapi-patternsStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

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

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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>` |

Related Skills

testing-patterns

65
from One-Man-Company/Skills-ContextManager

Testing patterns and principles. Unit, integration, mocking strategies.

tailwind-patterns

65
from One-Man-Company/Skills-ContextManager

Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.

python-patterns

65
from One-Man-Company/Skills-ContextManager

Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.

webapp-testing

65
from One-Man-Company/Skills-ContextManager

Web application testing principles. E2E, Playwright, deep audit strategies.

web-design-guidelines

65
from One-Man-Company/Skills-ContextManager

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

vulnerability-scanner

65
from One-Man-Company/Skills-ContextManager

Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.

ui-ux-pro-max

65
from One-Man-Company/Skills-ContextManager

UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks.

tdd-workflow

65
from One-Man-Company/Skills-ContextManager

Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.

systematic-debugging

65
from One-Man-Company/Skills-ContextManager

4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.

skill-creator

65
from One-Man-Company/Skills-ContextManager

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

server-management

65
from One-Man-Company/Skills-ContextManager

Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.

seo-fundamentals

65
from One-Man-Company/Skills-ContextManager

SEO fundamentals, E-E-A-T, Core Web Vitals, and Google algorithm principles.