Go HTTP Server Applications
SkillMediaDesign, build, test, and review production Go HTTP servers covering inbound adapters, modern ServeMux routing, middleware, strict bounded request decoding, response commitment, transparent ResponseWriter wrapping, server timeouts, health semantics, graceful shutdown, shared-state safety, and httptest verification. Use when implementing an HTTP service, API handler, middleware stack, server lifecycle, health endpoint, or inbound JSON boundary in Go.
Use Go HTTP Server Applications in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Go HTTP Server Applications and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Go HTTP Server Applications skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
What this skill tells your AI
The instructions your AI receives, as published by hashgraph-online/awesome-codex-plugins in plugins/LVTD-LLC/skills/skills/go-http-server-applications/SKILL.md and read by ahel’s review.
Keep handlers thin, bound untrusted input, configure the server explicitly, and make startup and shutdown part of the tested application contract.
Core Workflow
- Separate domain behavior from the inbound HTTP adapter.
- Define routes, methods, media types, limits, and error mappings.
- Build an explicit mux and ordered middleware stack.
- Decode requests strictly and within endpoint-specific byte/time budgets.
- Encode complete responses before committing headers where practical.
- Configure listener, server timeouts, header limits, and health semantics.
- Serve under a lifecycle that observes errors and drains with a deadline.
- Test handlers, routing, middleware, shared state, and real loopback behavior.
Read Next
| Task | Load |
|---|---|
| Build a server | guidelines.md, workflows/build-http-server.md |
| Test handlers or lifecycle | workflows/test-http-server.md |
| Review routing, middleware, JSON, or shutdown | references/http-server/rules.md |
| Understand server and writer contracts | references/http-server/knowledge.md |
| Review patterns | references/http-server/examples.md |
Guardrails
- Do not use
http.DefaultServeMuxfor application composition. - Do not expose a public server with zero-value timeout policy by accident.
- Do not read request bodies without an endpoint-specific bound.
- Do not assume a wrapped
ResponseWriterpreserves optional capabilities. - Do not call readiness an unconditional liveness response.
- Do not let the process exit before graceful shutdown finishes.
Source Notes
Guidance is transformed and paraphrased from Inanc Gumus, Go by Example: Programmer's Guide to Idiomatic and Testable Programs (Manning, 2025), Chapters 8-9. Examples are original.
Terminal-response control-flow and timeout guidance also incorporates transformed material from Teiva Harsanyi, 100 Go Mistakes and How to Avoid Them (Manning, 2022), Chapter 10.
Book: https://www.manning.com/books/go-by-example
Verify current routing and lifecycle behavior against https://pkg.go.dev/net/http and https://pkg.go.dev/net/http/httptest for the pinned Go version.
Signals
- GitHub stars
- 1k
- Forks
- 316
- Last commit
- Oct 2026
Advanced
- Item type
- skill
- Key
go-http-server-applications- Source
- github.com/hashgraph-online/awesome-codex-plugins
github.com/hashgraph-online/awesome-codex-plugins