scaffold-hono-service
Skill0 starsChanged 27 days agoMITView on GitHub
Stand up a new law-compliant Hono backend service from the proven w3cj reference baseline with deps bumped to current-safe pins. Use when asked to "stand up a backend", "scaffold a new API service", "start a new Hono service", or "create a backend from scratch". Encodes turbo's S-10 scenario + O-02/O-08/O-09 opinions — never a blank index.ts, never the unbumped starter.
- Installs packages
2 other projects use a version of this.
Adopted by
Most recently taken up by
- VelimirMueller/ai-development-skillstheir own version, first seen Oct 25, 2026
- VelimirMueller/claude-skillstheir own version, first seen Oct 11, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- VelimirMueller/ai-development-skills★ 7same name
- VelimirMueller/claude-skills★ 7same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- agent-runtimeSkill
- frontend-designSkill
- architectSkill
- deep-thinkSkill
- design-systemsSkill
- ecosystem-referenceSkill
- fractal-delegationSkill
- harness-reviewSkill
- heartbeatSkill
- integrate-resourcesSkill
- llm-council-critiqueSkill
- loop-createSkill
- mcp-setupSkill
- memory-compressionSkill
- memorySkill
- model-routingSkill
- oss-project-scaffoldSkill
- playwright-cliSkill
- repo-scoutSkill
- self-improveSkill
- skill-creatorSkill
- skill-routingSkill
- sprintSkill
- test-visualSkill
- troubleshootSkill
- ux-auditSkill
- audit-serverless-stateSkill
- design-api-contractSkill
- sse-streaming-safelySkill
- zod-boundary-and-patchSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Decide blank vs from-spec: If the user has an OpenAPI spec → this is the wrong skill.
- Distinctive: line 50
If any gate fails, iterate (Ralph loop) — do not report "done" until all four checks are green.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
scaffold-hono-service
Encodes scenario S-10 (scaffold the energy-law-compliant service from scratch) and opinions O-02 (default to Hono), O-08 (OpenAPI-first, generated from Zod), O-09 (Node 24 + native
.tsbut thetsc --noEmitgate is non-negotiable). The anti-pattern this kills: hand-rolling a flatindex.tsthat grows past 400 lines and breaks RPC inference, OR copying the reference repo without bumping its stale deps.
Trigger
Invoke when the user (or a sibling employee / coding agent) asks to:
- "stand up / scaffold a new backend / API service"
- "start a new Hono service"
- "create a backend from scratch" / "I need a service to expose X"
Do NOT invoke for: adding a route to an existing service (that's normal editing), generating a service from a spec the user already has (use gen_from_openapi / turbo api — see design-api-contract), or anything frontend/mobile/db/auth/payments/deploy (those are pixel/pebble/acorn/badge/penny/rocket — out of turbo's boundary).
Steps
- Decide blank vs from-spec. If the user has an OpenAPI spec → this is the wrong skill; route to
turbo api --spec <file>(the acceptance path) instead. If they want a fresh blank service → continue. - Run the scaffold (do not hand-roll):
This stands up theturbo scaffold --name <service-name> --out <dir> --jsonw3cj/hono-open-api-starterbaseline with deps bumped to current-safe pins (hono@^4.12.25,zod@^4.4,@hono/zod-openapi@^1.4) — the starter ships 0.x/Zod-3, and the bump-and-migrate is exactly where breakage hides (the v1@hono/zod-openapiis a Zod-3→4 peer shift that drags in the PATCH-.default()trap, P-04). The scaffold wires:/health,/openapi.json+ Scalar UI,hcWithTypeexport, Pino JSON logs,eslint-plugin-neverthrow, and the{name}.routes.ts/.handlers.ts/.index.ts/.test.tsroute-group layout that reconciles "chain.route()" with the <400-line law. - Verify the law on the output (the gate, not "it compiles"):
Both MUST be green.cd <dir> && npm install && npx tsc --noEmit # O-09: no `any`; native strip-types would NOT catch this npm run contract # runtime OpenAPI conformance + RPC `typeof app` compiletsc --noEmitis non-negotiable —node app.tsstrips types without type-checking, so the runtime never enforces the law. - Self-audit the scaffold (the generator must pass its own audit):
Expect zero P-02 (noturbo audit <dir> --jsonnew Map()/ module-scope mutable state) and zero P-04 (no defaulted create-schema reused for PATCH). - Confirm runtime swappability (O-05 hedge): the core stays Web-standard / Node-API-safe so a Bun↔Node swap is a config change. Do NOT migrate to Bun "for speed" — its edge collapses to ~3% once a DB is involved.
Output
A running, law-compliant Hono service directory plus a one-paragraph report:
tsc --noEmit: PASS/FAIL (the law gate)npm run contract: PASS/FAIL (OpenAPI conformance + RPC type)turbo audit: P-02 count, P-04 count (both must be 0)- pinned versions confirmed (
hono ≥4.12.25,zod ^4.4,@hono/zod-openapi ^1.x) - the route-group file layout, with no file >400 lines
- a note: "rate-limit / cache is echo's seam — not wired here."
If any gate fails, iterate (Ralph loop) — do not report "done" until all four checks are green.
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
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.

