YAML config parser with validation
You're building a YAML config parser in Rust for a CLI tool: load a `config.yaml`, validate it against a schema, apply defaults, and surface clear errors with the offending field path and line. You'll delegate it to an AI agent. Write the prompt/spec — constraints, edge cases, acceptance criteria — for a first-try-correct result. What does a vague prompt ("parse the YAML config") get wrong in Rust specifically?
validate_config(known_keys: list[str], required_keys: list[str], lines: list[str]) → list[str][["name","timeout","country","retries"],["name","timeout"],["name = svc","timeout = 30"]]out[][["name","timeout","country","retries"],["name","timeout"],["name = svc","tieout = 30"]]out["line 2: unknown key 'tieout'","missing required key 'timeout'"][["name","timeout","country","retries"],["name","timeout"],["name = svc","timeout = 30","country = NO"]]out[]Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.