From db52bc5c185f56a271c22229723e28a933932143 Mon Sep 17 00:00:00 2001 From: Jack Felke Date: Fri, 13 Mar 2026 08:22:34 -0700 Subject: [PATCH] docs: add 'verify it's working' section after Quick Start MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Shows users how to confirm preflight is loaded and what to expect with a vague vs well-scoped prompt — bridges the gap between install and actual usage. --- README.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/README.md b/README.md index 6d03f5d..becf02c 100644 --- a/README.md +++ b/README.md @@ -115,6 +115,32 @@ Add to your project's `.mcp.json`: Restart Claude Code. The tools activate automatically. +### Verify it's working + +After setup, confirm preflight is loaded: + +```bash +claude mcp list +# Should show: preflight +``` + +Then open Claude Code in your project and try a deliberately vague prompt: + +``` +> fix the bug +``` + +Instead of guessing, Claude will fire `preflight_check` → `clarify_intent` and ask which bug you mean, listing recent errors or open issues it finds. That's how you know it's working. + +Try a well-scoped prompt for comparison: + +``` +> In src/auth/jwt.ts, the refreshToken function doesn't handle expired refresh tokens — + add a check that throws AuthExpiredError when the refresh token's exp claim is in the past +``` + +This one passes triage as actionable and goes straight through. No interruption, no overhead — preflight only activates when it helps. + ### Option C: npm (global) ```bash