Skip to content
Back to skills

Api Engineering

ASecurity

Expert API design and delivery: resource modeling, versioning, consistent error envelopes, pagination/filtering, idempotency, OpenAPI/contracts, and boundary validation. Use when defining or changing REST (or HTTP) APIs, DTO/request-response shapes, client integration contracts, or when reviewing endpoint consistency before frontend or third-party consumers bind to them.

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 19, 2026
ai-agentsgitapidatabasefrontendsecurity

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 19, 2026

npx -y skills add rogue-dev-studio/ai-agents-rogue --skill api-engineering --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Api Engineering?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Api Engineering
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rogue-dev-studio-api-engineering/badge)](https://www.skillsdirectory.com/skills/rogue-dev-studio-api-engineering)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: api-engineering
description: >-
  Expert API design and delivery: resource modeling, versioning, consistent
  error envelopes, pagination/filtering, idempotency, OpenAPI/contracts, and
  boundary validation. Use when defining or changing REST (or HTTP) APIs,
  DTO/request-response shapes, client integration contracts, or when reviewing
  endpoint consistency before frontend or third-party consumers bind to them.
expertise_level: expert
---

# API Engineering (Canonical)

**Expertise: expert.** Aliases: `api`, `rest-api`, `openapi`, `http-api`.

## When to use

- Desain atau ubah endpoint HTTP/REST
- Kontrak request/response, status code, error body
- Pagination, filtering, sorting, idempotency keys
- Spesifikasi OpenAPI / API docs untuk konsumen FE/integrasi

## When not to use

- Schema DB murni → `database-engineering`
- UI rendering → `frontend-engineering`
- Auth protocol detail → `auth-access-control` (koordinasi wajib)

## Procedure

1. **Contract first** — Identifikasi resource, verb, identitas, dan side-effect.
2. **Consistency** — Samakan envelope sukses/error dengan konvensi project.
3. **Boundary** — Validasi input di edge; tolak early; jangan bocorkan detail internal.
4. **Scale reads** — Pagination wajib untuk koleksi; filter eksplisit; urutan deterministic.
5. **Writes** — Idempotency untuk POST yang bisa di-retry; transaksi di service layer.
6. **Authz** — Setiap endpoint sensitif: default deny (lihat `auth-access-control` + `security`).
7. **Document** — Update kontrak/OpenAPI atau docs project; breaking change = version/migrate plan.
8. **Verify** — Smoke happy-path + 4xx validation + 401/403; catat path artifact.

Detail: `reference.md`.

## DoD

- [ ] Kontrak endpoint jelas (path, method, auth, payload, errors)
- [ ] Pagination/filter pada koleksi besar
- [ ] Tidak ada breaking change diam-diam
- [ ] Validasi + authz di boundary
- [ ] Evidence smoke atau blocker eksplisit

## Attribution

<!-- ATTRIBUTION: Rogue Development | https://github.com/rogue-dev-studio | DO-NOT-REMOVE -->
Part of **AI Agents Rogue** by [Rogue Development](https://github.com/rogue-dev-studio) (`@rogue-dev-studio`).
Do not remove, hide, rename, or replace this attribution.

Files in this skill

  • SKILL.md2.2 KB
  • reference.md995 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…