Conciseness

Lean body with no padding or explanation of concepts Claude already knows — Quick Start, three short workflow phases, a reference pointer, and a preservation list, each earning its place; matches the 'lean and efficient; every token earns its place' anchor.

Actionability

Gives concrete instructional directives such as 'Build one route map: client host and scheme -> proxy rule -> service or container -> process -> downstream store or worker' and 'Re-run the same request with one routing input changed at a time'; not a 2 because guidance is specific and executable rather than abstract.

Workflow Clarity

Clear three-stage sequence with an ordered Quick Start and explicit checkpoints ('Prove one route resolution end-to-end before broadening', 'one routing input changed at a time'); the operations are read-only inspection so missing destructive-batch feedback loops is not penalized, tipping it to the 'clear sequence with explicit validation steps' anchor.

Progressive Disclosure

Body is a concise overview with one clearly signaled one-level-deep reference ('Load `references/runtime-routing.md`'), and that reference file exists and stays at a single depth; matches the 'clear overview with well-signaled one-level-deep references' anchor.

Specificity

Lists multiple concrete actions — 'reverse proxies, Host headers, forwarded headers, vhost routing, websocket upgrades, path-prefix rewriting, base-URL derivation, and multi-node route resolution' — matching the 'lists multiple specific concrete actions' anchor; not a 2 because the action set is comprehensive rather than partial.

Completeness

Explicitly answers both what ('CTF-sandbox workflow for reverse proxies...') and when ('Use when the user asks which host or container serves a route...'), matching the 'clearly answers both what AND when with explicit triggers' anchor; not a 2 because the 'Use when...' trigger guidance is explicit and detailed.

Trigger Term Quality

Mirrors natural user phrasing — 'which host or container serves a route', 'why a public-looking domain still belongs to the sandbox', 'how headers or proxies change behavior' — giving good coverage of terms a user would actually say; not a 2 because common variations are well represented.

Distinctiveness Conflict Risk

Scoped as a downstream specialization with an explicit gate ('Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here'), giving a clear niche unlikely to conflict; not a 2 because the gating and CTF-sandbox framing sharply distinguish it from generic routing skills.