Hyperwork Api Scaffold

API Scaffold

Use: Tasks that create new API endpoints or services from scratch.

Approach

1. Read existing endpoint files before writing anything — match patterns exactly.
2. Identify: router/handler pattern, request validation library, response shape, error format.
3. Scaffold in order: schema/types → handler → route registration → tests.
4. Tests: cover happy path + at least one 4xx (bad input) + one 4xx (not found/auth).

Output Checklist

• Request schema with validation (not raw req.body — use zod/pydantic/joi per repo).
• Response type explicit — no any or dict.
• Error responses follow existing error shape (read existing handlers for format).
• Route registered in correct router/router group.
• OpenAPI/docstring annotation if repo uses them.

Do / Don't

• DO: grep for an existing similar endpoint and copy its structure — consistency > novelty.
• DO: include auth middleware if all other routes have it.
• DON'T: invent new patterns — match what's there.
• DON'T: skip validation — unvalidated endpoints are a security boundary violation.
• DON'T: hardcode env vars — use config injection pattern from repo.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: samrom3
• Source: samrom3/claude-hyper-plugs
• License: MIT

Install and usage instructions live in the source repository linked above.