Hyperwork api scaffold
Skill samrom3/claude-hyper-plugs/hyperloop/skills/hyperwork-api-scaffold
API scaffolding — generate route/handler/schema/test skeletons for new endpoints, following existing project patterns.From its SKILL.md
npx -y skills add samrom3/claude-hyper-plugs --skill hyperwork-api-scaffoldAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 256 tokens by cl100k_base, as published. Nobody here has run it
API Scaffold
Use: Tasks that create new API endpoints or services from scratch.
Approach
- Read existing endpoint files before writing anything — match patterns exactly.
- Identify: router/handler pattern, request validation library, response shape, error format.
- Scaffold in order: schema/types → handler → route registration → tests.
- 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
anyordict. - 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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.