JevMade Sign in
← Back to guides

JevMade field notes / Written guide

Build and debug an opt-in Claude Code prompt router

Krzysztof Słomka designs a Jev classifier that suggests which Claude Code helper should handle a prompt. He explains the silent hook failure, missing conversation context and per-project privacy switch.

Original by Krzysztof SłomkaAgent workflows

Listen to this guide

JevMade’s plain-English explanation

0:00 /

Our summary

A short lookup and a difficult investigation need different amounts of help. Krzysztof Słomka uses Jev to sort Claude Code prompts into four task sizes. The hook adds an instruction asking the lead model to delegate; it does not switch models or enforce that delegation itself.

Short messages and uncertain classifications stay with the lead model. Missing credentials, timeouts and unusable answers also leave the original prompt untouched. When Słomka checks the installed hook, he discovers it has never routed a real prompt: it read prompt_text instead of the actual prompt field.

The article measures six synthetic endpoint calls, not a working production router. Its confidence cutoff is uncalibrated, and helpers may lack the conversation behind a follow-up. Routed text goes to OpenRouter and TypeSafe. A person enables each project explicitly; the author keeps confidential client work outside this route.

Key takeaways

  1. Verify that the hook receives the field it actually reads. An empty log can mean it exits before calling the classifier, even when prompts still work normally.
  2. Keep context-dependent follow-ups with the lead model. A task-size label does not give a helper the conversation or files it needs.
  3. Make external prompt sharing an explicit project choice. The classifier suggests a tier; it must not decide whether confidential text may leave the machine.

The UserPromptSubmit design adds additionalContext asking for tiny, everyday, large or hardest helpers; it does not directly change models or enforce routing. Prompts shorter than 80 characters and confidence below 0.60 stay inline. The installed hook produced no real routing decisions because it read prompt_text instead of prompt. Six synthetic calls illustrate endpoint timing, not routing accuracy, answer quality, sustained latency or savings. The threshold is uncalibrated and some follow-up handling relies on lead-model instructions. Routed text is sent to OpenRouter and TypeSafe.

Krzysztof Słomka · Original published

Read the original guide Opens the author’s site in a new tab.

Keep this for later

Sign in to bookmark experiments, guides and videos, and keep notes only you can see.

Continue to sign in

We’ll bring you back to this listing.