← ClaudeAtlas

gaugelisted

Engineer a codebase's feedback surface so an agent gets clear feedback at every step — fast, local, attributed, deterministic, and hard to fake green — instead of flailing against late, opaque, or false-green signals. Set up the strict type layer, boundary validation, errors-as-values, structured failures, observability, and the gates that make the signal trustworthy. Use when the user wants a project to give the agent a "static-language / Rust-like hand-feel", asks to set up strict typing (pyright/mypy/tsc), add boundary validation (pydantic/zod), make failures legible, stop an agent guessing, or harden the feedback the codebase produces. Triggers on "clear feedback for the agent", "Rust-like hand-feel in Python/TS", "set up strict typing", "make failures legible", "the agent keeps flailing".
IamK77/Skill · ★ 1 · AI & Automation · score 77
Install: claude install-skill IamK77/Skill
<!-- Copyright 2026 IamK77 — Licensed under the Apache License, Version 2.0. See ./LICENSE and ./NOTICE · https://www.apache.org/licenses/LICENSE-2.0 --> # gauge !`checklist init ${CLAUDE_SKILL_DIR} --force` An agent works in a loop: act → observe a signal → correct. Its effectiveness is bounded by the **quality of the signal at each step** — it has no intuition about the system, no memory between sessions, and no "feel" that something is subtly wrong. It knows only what the code, the checker, the test, and the logs *tell* it. So the highest-leverage thing you can do for an agent is make the codebase's feedback **clear**. The goal is not to copy a static language's syntax — it is to reproduce the *property* a good static language delivers: clear feedback. Decompose "clear" into the dimensions you actually engineer for: - **Fast** — it returns inside the agent's working loop (on save, on one command), not minutes later and not only in production. - **Local** — it points at the exact site (file, line, sub-expression), not "something failed downstream". - **Attributed** — it says *why* (expected X, got Y; this constraint failed), not just "error". - **Deterministic** — same input, same signal; a flaky signal is no signal, because the agent can't attribute it. - **Trustworthy** — green means good, and *absence* of a signal means "fine", not "this path was never checked". - **Un-fakeable** — a signal the agent can flip green by hand (delete the assertion, `as any`, widen the