Api Design Knowledge logo

Api Design Knowledge

Community
dykyi-roman
api-design-knowledge

API Design knowledge base. Provides REST constraints, Richardson Maturity Model, HTTP semantics, content negotiation, and GraphQL/gRPC comparison for API audits and generation.

Overview

Publisherdykyi-roman
Repositoryawesome-claude-code
Skill nameapi-design-knowledge
Stars
98
Forks
25
Bundled files
3
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by dykyi-roman on GitHub. Read the source before you install it.

Installation

Install the Api Design Knowledge AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/dykyi-roman/awesome-claude-code.git /tmp/awesome-claude-code
mkdir -p .claude/skills
cp -r /tmp/awesome-claude-code/skills/api-design-knowledge .claude/skills/api-design-knowledge
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Api Design Knowledge in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Api Design Knowledge on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Api Design Knowledge is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

API Design Knowledge Base

Quick reference for API design patterns, REST best practices, and PHP implementation guidelines.

Core Principles

REST Constraints

ConstraintDescriptionImplication
Client-ServerSeparation of concernsIndependent evolution
StatelessNo server-side session stateEach request contains all info
CacheableResponses declare cacheabilityReduces server load
Uniform InterfaceStandard resource operationsPredictable API surface
Layered SystemClient can't tell if connected directlyProxy, gateway, CDN support
Code on Demand (optional)Server can send executable codeRarely used in APIs

Richardson Maturity Model

LevelNameDescriptionExample
0Swamp of POXSingle endpoint, RPC-stylePOST /api with action in body
1ResourcesMultiple endpoints per resourceGET /orders/123
2HTTP VerbsProper use of HTTP methods + status codesDELETE /orders/123204
3HATEOASHypermedia controls in responsesLinks to related actions

HTTP Methods Semantics

MethodSafeIdempotentRequest BodyTypical Use
GETYesYesNoRetrieve resource
HEADYesYesNoCheck resource existence
POSTNoNoYesCreate resource, trigger action
PUTNoYesYesReplace resource entirely
PATCHNoNoYesPartial update
DELETENoYesNoRemove resource
OPTIONSYesYesNoCORS preflight, capabilities

Status Code Guide

RangeCategoryCommon Codes
2xxSuccess200 OK, 201 Created, 202 Accepted, 204 No Content
3xxRedirection301 Moved Permanently, 304 Not Modified
4xxClient Error400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, 409 Conflict, 422 Unprocessable Entity, 429 Too Many Requests
5xxServer Error500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable, 504 Gateway Timeout

Content Negotiation

HeaderPurposeExample
AcceptClient requests formatAccept: application/json
Content-TypeBody format declarationContent-Type: application/json
Accept-LanguageLocalizationAccept-Language: en-US
Accept-EncodingCompressionAccept-Encoding: gzip, br

API Style Comparison

AspectRESTGraphQLgRPC
ProtocolHTTP/1.1+HTTP/1.1+HTTP/2
Data formatJSONJSONProtobuf
SchemaOpenAPI (optional)SDL (required).proto (required)
CachingHTTP caching nativeComplex (POST only)Manual
Over-fetchingCommonSolved (client picks fields)Solved (defined messages)
Under-fetchingCommon (multiple calls)Solved (nested queries)Separate RPCs
Learning curveLowMediumHigh
Best forPublic APIs, CRUDClient-driven UIs, BFFInternal services, streaming

Quick Checklists

API Design Checklist

  • Resources use nouns, not verbs (/orders not /getOrders)
  • Consistent naming convention (kebab-case or camelCase)
  • Proper HTTP methods for operations
  • Meaningful status codes (not always 200)
  • Pagination for list endpoints
  • Filtering and sorting support
  • Versioning strategy defined
  • Error responses follow RFC 7807
  • Rate limiting with proper headers
  • CORS configured for browser clients

Security Checklist

  • Authentication on all endpoints (except public)
  • Authorization checks per resource
  • Input validation at API boundary
  • Rate limiting per client/IP
  • HTTPS only (no HTTP)
  • No sensitive data in URLs
  • Proper CORS policy
  • Security headers set

Detection Patterns

bash
# REST endpoint definitions
Grep: "#\[Route|@Route|->get\(|->post\(|->put\(|->delete\(" --glob "**/*.php"
Glob: **/Controller/**/*.php
Glob: **/Action/**/*.php

# Status code usage
Grep: "->setStatusCode\(|Response\(.*[0-9]{3}|JsonResponse\(" --glob "**/*.php"

# Content negotiation
Grep: "Accept|Content-Type|application/json" --glob "**/*.php"

# API versioning
Grep: "/v[0-9]/|api-version|Accept.*vnd\." --glob "**/*.php"

# Error handling
Grep: "ProblemDetails|RFC7807|application/problem" --glob "**/*.php"
Grep: "JsonResponse.*4[0-9]{2}|JsonResponse.*5[0-9]{2}" --glob "**/*.php"

# Pagination
Grep: "page|per_page|limit|offset|cursor" --glob "**/Controller/**/*.php"

Advanced API Patterns

Cursor-Based Pagination (High-Load)

AspectOffset-BasedCursor-Based
URL?page=5&per_page=20?cursor=abc123&limit=20
Performance at scaleDegrades (OFFSET N)Constant (WHERE id > X)
ConsistencyMisses/duplicates on insertStable, no gaps
Random page accessYesNo (sequential only)
Use caseAdmin panelsFeeds, large datasets

API Rate Limiting Algorithms

AlgorithmPrecisionBurstPHP Implementation
Token BucketMediumAllows burstRedis Lua script
Sliding WindowHighSmoothRedis sorted set
Fixed WindowLowEdge burstRedis INCR + EXPIRE
Leaky BucketHighNo burstRedis list

Rate Limit Headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, Retry-After (on 429).

gRPC for PHP

FactorChoose RESTChoose gRPC
Client typeBrowser, third-partyInternal services
PayloadSmall-medium JSONLarge binary data
StreamingNot neededReal-time updates
PHP ecosystemMatureLimited (ext-grpc)

GraphQL N+1 Prevention

TechniqueHowComplexity
DataLoaderBatch + cache per requestMedium
Query depth limitMax 5-7 nesting levelsLow
Complexity scoringCost per field, reject expensiveMedium
Persisted queriesWhitelist allowed queriesLow

References

For detailed information, load these reference files:

  • references/rest-patterns.md — Richardson Maturity details, HATEOAS, pagination, filtering, versioning strategies
  • references/error-handling.md — RFC 7807 Problem Details, error response patterns, GraphQL errors, PHP implementation
  • references/advanced-api.md — Cursor-based pagination, API rate limiting (token bucket, sliding window), gRPC PHP integration, GraphQL N+1 solutions

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Api Design Knowledge AI skill do?

API Design knowledge base. Provides REST constraints, Richardson Maturity Model, HTTP semantics, content negotiation, and GraphQL/gRPC comparison for API audits and generation.

Why use Api Design Knowledge on TypingMind?

Because you install it once and use it with any model. Api Design Knowledge is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Api Design Knowledge in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/dykyi-roman/awesome-claude-code/tree/master/skills/api-design-knowledge. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Api Design Knowledge?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Api Design Knowledge?

As many as you like. As long as a model supports skills, you can use Api Design Knowledge with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Api Design Knowledge AI skill free?

Yes. It is published on GitHub by dykyi-roman under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇