api-design-principles

Category: Content & Multimedia | Uploader: AratKruglik | Downloads: 0 | Version: v1.0（Latest）

Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing... Українською: проектуй API, спроектувати ендпоінт, API дизайн, REST, GraphQL, версіонування API, контракт API, документація API, масштабованість, ресурси, маршрути, HTTP методи, відповідь сервера, структура запиту.

Changelog: Source: GitHub https://github.com/AratKruglik/claude-laravel

Directory Structure

Current level: tree/main/.claude/skills/api-design-principles/

📁 assets/
- 📄 api-design-checklist.md 3.8 KB
- 📄 rest-api-template.py 5.2 KB
📁 references/
- 📄 graphql-schema-design.md 8.8 KB
- 📄 rest-best-practices.md 7.4 KB
📁 resources/
- 📄 implementation-playbook.md 12.7 KB
📄 SKILL.md 1.8 KB

SKILL.md

---
name: api-design-principles
description: "Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing... Українською: проектуй API, спроектувати ендпоінт, API дизайн, REST, GraphQL, версіонування API, контракт API, документація API, масштабованість, ресурси, маршрути, HTTP методи, відповідь сервера, структура запиту."
risk: unknown
source: community
---

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

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

api-design-principles

Directory Structure

SKILL.md

Report

Notice