---
name: api-design-principles
description: "Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers and stand the test of time."
risk: safe
source: community
date_added: "2026-02-27"
title: api-design-principles
canonical_url: https://skilld.dev/gh/davila7/claude-code-templates/api-design-principles
last_updated: 2026-09-29T01:26:20.000Z
---

> **Skill from skilld.dev.** Follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [assets/api-design-checklist.md](https://skilld.dev/api/skills-raw/davila7/claude-code-templates/api-design-principles/assets/api-design-checklist.md), [assets/rest-api-template.py](https://skilld.dev/api/skills-raw/davila7/claude-code-templates/api-design-principles/assets/rest-api-template.py), [references/graphql-schema-design.md](https://skilld.dev/api/skills-raw/davila7/claude-code-templates/api-design-principles/references/graphql-schema-design.md), [references/rest-best-practices.md](https://skilld.dev/api/skills-raw/davila7/claude-code-templates/api-design-principles/references/rest-best-practices.md), [resources/implementation-playbook.md](https://skilld.dev/api/skills-raw/davila7/claude-code-templates/api-design-principles/resources/implementation-playbook.md).
>
> If the user asked to install this Skill, run `npx skilld install davila7/claude-code-templates/api-design-principles`. Install writes the Skill files into the project, so every session loads them.

# API Design Principles

Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers and stand the test of time.

## Use this skill when

- Designing new REST or GraphQL APIs
- Refactoring existing APIs for better usability
- Establishing API design standards for your team
- Reviewing API specifications before implementation
- Migrating between API paradigms (REST to GraphQL, etc.)
- Creating developer-friendly API documentation
- Optimizing APIs for specific use cases (mobile, third-party integrations)

## Do not use this skill when

- You only need implementation guidance for a specific framework
- You are doing infrastructure-only work without API contracts
- You cannot change or version public interfaces

## Instructions

1. Define consumers, use cases, and constraints.
2. Choose API style and model resources or types.
3. Specify errors, versioning, pagination, and auth strategy.
4. Validate with examples and review for consistency.

Refer to `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.

## Resources

- `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.