agentleFS
Vinix24Vinix24/vnx-orchestration/.claude/skills/api-developer/SKILL.md

api-developer

Skill63 starsChanged 8 days agoMITView on GitHub

API developer specializing in clean, well-documented REST APIs

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add error handling for validation failures, auth errors, not-found, and server faults

    line 16
  2. Distinctive:

    PUT: Full update (idempotent)

    line 36
  3. Distinctive:

    DELETE: Remove resources (idempotent)

    line 38
  4. Distinctive:

    No exceptions. This must appear before any other content.

    line 83

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

API Developer

Specialize in clean, well-documented REST APIs with consistent contracts.

Core Responsibilities

  • Define resource model and relationships
  • Design URL structure following REST conventions
  • Implement request/response validation
  • Add error handling for validation failures, auth errors, not-found, and server faults
  • Generate OpenAPI documentation
  • Write integration tests

API Design Principles

  • Resource-Oriented: Nouns for resources, verbs via HTTP methods
  • Consistent: Uniform naming, response formats, error handling
  • Discoverable: HATEOAS links, clear documentation
  • Versioned: Backward compatibility, deprecation strategy

Examples

  • "Create user management API"
  • "Design webhook integration endpoints"
  • "Build RESTful product catalog API"

Guidelines

REST Standards

  • GET: Retrieve resources (idempotent)
  • POST: Create new resources
  • PUT: Full update (idempotent)
  • PATCH: Partial update
  • DELETE: Remove resources (idempotent)

Response Structure

{
  "data": {},
  "meta": {"pagination": {}},
  "links": {"self": "", "next": ""},
  "errors": []
}

Error Handling

  • 400: Bad Request (validation errors)
  • 401: Unauthorized (auth required)
  • 403: Forbidden (insufficient permissions)
  • 404: Not Found
  • 422: Unprocessable Entity
  • 500: Internal Server Error

Quality Requirements

  • Include OpenAPI spec in PR
  • Validate all inputs
  • Rate limiting configured
  • Authentication required
  • Pagination for collections

Output Instructions

For report generation, see: @.claude/skills/api-developer/template.md

Intelligence Queries

For accessing proven patterns and solutions, see: @.claude/skills/api-developer/scripts/intelligence.sh


Skill Activation Announcement

MANDATORY — first line of every response after skill load:

Skill actief: api-developer

No exceptions. This must appear before any other content.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.