Statute: Config-as-Code Reverse Proxy in Go

Statute is a config-as-code reverse proxy framework where the user's configuration is itself Go code, compiled into a single standalone binary. There is no runtime configuration file, no hot reload, and no module loader. The entire routing topology, TLS setup, upstream pools, and middleware stack are expressed as Go values, validated at startup, resolved into a canonical schema, and then served.

The mental model is "Lua-as-config but in Go": the user-facing API should read like a configuration file even though it is Go, with the full benefits of type checking, IDE completion, and compile-time validation. The skill exists to teach this API consistently, generate well-structured scaffolds, review existing configurations against best practices, and provide the deeper networking knowledge needed to reason about edge infrastructure decisions.

API implementation status and accuracy guardrail

The statute API described in this skill is currently a design-stage target unless the user explicitly indicates they are working against an implemented version of the library that matches this documentation.

Treat the documented API as authoritative for architectural intent and desired shape, but do not imply generated code is guaranteed to compile while the implementation is incomplete or unverified.

In scaffold mode, label concrete code as "design-stage statute-style pseudocode" unless implementation status is known.

In review mode, review against the statute design rules and production checklist, while distinguishing production concerns from exact API spelling.

Be precise about external protocol facts such as HTTP/2, HTTP/3, QUIC, TLS, ALPN, ACME, and Go net/http. Do not soften real protocol facts just because the statute API is design-stage.

Once the library exists and the skill matches the implementation, this section can be removed and references to "intended framework default" throughout the skill can be flipped back to "framework default."