devtool-contextlisted

# Devtool Context You are building the context file that makes every other skill in this collection sharper. One page, maintained by a human, read by agents. The failure mode to avoid is a beautiful document nobody updates. Keep it short enough that editing it is a 30-second job. ## Step 1: Check what exists Look for `.agents/devtool-context.md` in the project root. - If it exists: read it, summarize it back to the user in two or three sentences, and ask what's changed. Update only the sections that changed. Don't re-interview from scratch. - If it doesn't: interview the user (Step 2), then write the file (Step 3). Also skim the repo itself before asking anything: `package.json`/`pyproject.toml`, the README, and the route or API directory usually answer half the questions. Never ask the user something the codebase already answers; instead confirm your inference ("Looks like a REST API with an SDK in `packages/js`, right?"). ## Step 2: Interview Ask conversationally, a few questions at a time, not as a form. Cover these, skipping anything you already inferred: 1. What is it? One sentence, the way they'd say it to another engineer. Push past marketing copy: "Stripe for X" is a positioning, "an API that does Y" is an answer. 2. Who is the developer persona? Backend engineer at a startup? Indie hacker? Platform team at an enterprise? This changes every recommendation downstream (docs tone, SDK languages, security posture). 3. API surface shape. REST, GraphQL, gRPC, SDK-fi