Best use case
api-design is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Design or review API endpoints (REST/GraphQL)
Teams using api-design should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/api-design/SKILL.md --create-dirs "https://raw.githubusercontent.com/hivellm/rulebook/main/.claude/skills/api-design/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/api-design/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How api-design Compares
| Feature / Agent | api-design | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Design or review API endpoints (REST/GraphQL)
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Design or review the API for: $ARGUMENTS Steps: 1. Gather requirements from the codebase and any existing API patterns 2. Design endpoints following REST conventions (or GraphQL schema) 3. Define request/response schemas with types 4. Document error responses and status codes 5. Write or update OpenAPI spec if applicable
Related Skills
We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.