Skip to content
Agentmart
Submit a tool

api-design

API contract design and review workflow.

Skill by JunMystery

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/junmystery-api-design-8ddc1c

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

API contract design and review workflow. Use when designing or changing endpoints, request and response schemas, status codes, pagination, filtering, sorting, versioning, rate limits, webhooks, or API error models.

Use cases: documents, design, backend, productivity

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/api-design

What's inside

Skill name
api-design
Description
API contract design and review workflow. Use when designing or changing endpoints, request and response schemas, status codes, pagination, filtering, sorting, versioning, rate limits, webhooks, or API error models.
License
MIT
Instructions
23 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# API Design

Use this skill when a task changes an API surface or external contract.

## What to Apply

- Define resources, methods, request bodies, response shapes, and errors before implementation.
- Use consistent naming, versioning, pagination, filtering, and status code conventions.
- Document validation, authentication, authorization, rate limits, and idempotency.
- Preserve backwards compatibility unless the user explicitly accepts a breaking change.
- Keep contracts boring, predictable, and testable.

## Reference Files

- [ai-agent-standards/prompts/sample-use-cases/create-api-with-rate-limiting.md](../../ai-agent-standards/prompts/sample-use-cases/create-api-with-rate-limiting.md)
- [ai-agent-standards/engineering-practices/DOCUMENTATION_STANDARDS.md](../../ai-agent-standards/engineering-practices/DOCUMENTATION_STANDARDS.md)
- [ai-agent-standards/risk-management/security-constraints.md](../../ai-agent-standards/risk-management/security-constraints.md)

## Output Expectation

Return the proposed contract, compatibility notes, and the tests needed to prove the API behavior.

From JunMystery/AI-Agent-Standards, MIT.

More from JunMystery/AI-Agent-Standards

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
May 25, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/JunMystery/AI-Agent-Standards
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from JunMystery

Cite this page

api-design skill. Agent Mart. https://agentmart.dev/skills/junmystery-api-design-8ddc1c (last updated 2026-10-24)