Setup complete

You're ready to prompt well.

PromptWell sits between you and Fable 5.
Messy prompt in. Crisp prompt out. Fewer tokens burned.

How it works

You Messy prompt "fix the auth bug"
→
Haiku 4.5 crisp() ~$0.001
→
Blueprint Crisp prompt score + savings
→
Fable 5 Executes no wasted tokens

The 3 tools

crisp(task, context?) — optimize a prompt before Fable 5 sees it
Call this whenever you're about to hand a vague task to Fable 5. It returns a clean prompt, a disambiguation score, and an estimated token savings. 
// In Claude Code, call it as an MCP tool:
mcp__promptwell__crisp({
  task: "fix the auth bug",
  context: "Next.js app, JWT auth in src/lib/auth.ts"  // optional
})

// Returns:
{
  crisp_prompt: "Goal: Fix JWT token expiry handling...\n\nConstraints:\n- do not change token format\n...",
  blueprint: {
    structural_goal: "Fix JWT token expiry in auth middleware",
    disambiguation_score: 72,
    what_was_vague: ["no file path specified", "unclear which auth system"]
  },
  estimated_token_savings: "~2,880 tokens"
}
0–20Crystal clear — specific paths, measurable outcome 21–50Decent — goal clear, missing some context 51–80Vague — common, fixable patterns 81–100Unusable — Fable 5 will guess major requirements
score(...) — record what Fable 5 accomplished
Call this after Fable 5 finishes. It saves the session to your history so PromptWell can track your improvement over time. 
mcp__promptwell__score({
  original_prompt: "fix the auth bug",
  disambiguation_score: 72,          // from crisp()
  what_was_vague: ["no file path specified"],  // from crisp()
  result_summary: "Fixed JWT expiry, all tests pass",
  tokens_used: 4200                  // optional
})
stats() — see your prompting trends
Shows your average disambiguation score over time, token savings, and the top patterns you repeat so you can fix them. 
mcp__promptwell__stats()

// Example output:
PromptWell Stats
Sessions tracked: 24
Avg disambiguation score: 48/100 (lower = crisper)
7-day avg:  41/100
30-day avg: 56/100
Estimated tokens saved: ~38,400

Top patterns to fix:
  - no file path specified (seen 14x)
  - no success criteria (seen 9x)
  - unclear which system (seen 6x)
Tip: The best time to call crisp() is right before you'd normally type a long, multi-sentence prompt to Fable 5. If you can describe the task in one crisp sentence with a file path and a success criterion, you probably don't need it. If you can't — you do.