Rust crate methods don't exist
You ask an AI to integrate a Rust crate you named, and twice it returns code calling methods that don't exist on that crate's types — it keeps 'fixing' by inventing differently-named methods that also don't exist. You're three prompts deep. Diagnose what's happening and decide your next move instead of prompting a fourth time.
Implement
find_ungrounded_calls(proposed_calls: list[str], api_surface: list[str]) → list[str]Examples
in
[["conn.execute_batch(sql)","conn.query_one(sql)","conn.fetch_all()"],["execute_batch","query_one","close"]]out["fetch_all"]in
[["pool.acquire()","pool.acquire()"],["acquire"]]out[]in
[["client.stream_rows(q)","client.streamRows(q)"],["stream_rows"]]out["streamRows"]What a strong answer looks like
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.
0:00 of about 16 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.