api-design
v0.8.0APIs in both directions: design your own (resource naming, status-code discipline, pagination/filtering/sorting, versioning, RFC 9457 errors, idempotency, Laravel API Resources, plus a graphql-grpc skill for non-REST surfaces; /api-design:review and spec-first /api-design:scaffold) and consume others' honestly — verify current official API/SDK docs before writing integration code (UserPromptSubmit reminder + /api-design:check, the api-docs-first skill) and keep your own docs true after a change with the docs-upkeep drift scan: README claims, changelog gaps, stale examples, dead links (/api-design:drift).
By Ivan-WG1 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 4 skill or MCP entries
- Source updated
- Sep 15, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install api-design for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install api-design-2@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/galaykos/cc-marketplaceClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/api-design/.
Plugin files
├── .claude-plugin/plugin.json├── skills/api-design/SKILL.md├── skills/api-docs-first/SKILL.md├── skills/docs-upkeep/SKILL.md└── skills/graphql-grpc/SKILL.md
Included Skills4
Use when designing or reviewing your own REST APIs — resource naming, honest status codes, RFC 9457 problem+json, cursor vs page pagination, whitelisted filtering, versioning and breaking changes, Idempotency-Key, Laravel apiResource/FormRequest mapping. Consuming third-party API docs lives in the sibling `api-docs-first` skill.
Use before writing any code that calls an external API, SDK, or third-party library — verify current official docs first; no accessible docs, stop and ask for a URL. Never code an integration from memory. Designing your own REST APIs is api-design.
Use when a change alters behavior, interfaces, setup steps, or commands — to update the documentation that just became a lie, in the same change, before it merges.
Use when designing or reviewing a GraphQL or gRPC API — schema design, N+1/dataloader, resolver authorization, depth/complexity limits; protobuf design, streaming, deadlines, versioning. For REST use api-design.
Plugin manifests1
{
"name": "api-design",
"version": "0.8.0",
"description": "APIs in both directions: design your own (resource naming, status-code discipline, pagination/filtering/sorting, versioning, RFC 9457 errors, idempotency, Laravel API Resources, plus a graphql-grpc skill for non-REST surfaces; /api-design:review and spec-first /api-design:scaffold) and consume others' honestly — verify current official API/SDK docs before writing integration code (UserPromptSubmit reminder + /api-design:check, the api-docs-first skill) and keep your own docs true after a change with the docs-upkeep drift scan: README claims, changelog gaps, stale examples, dead links (/api-design:drift).",
"author": {
"name": "Ivan-WG",
"email": "[email protected]"
},
"keywords": [
"api",
"backend",
"review"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[api-design on Agent Plugins Marketplace](https://pluginsmp.com/plugins/api-design-2)