Cookbook Router — your Claude build brief, routed to the right recipes

Describe what you are trying to build with the Claude API and get a routing plan across the twenty-one Claude Cookbook recipes: the shape first (one call, a workflow, an agent, a batch job or a cheap-lane-plus-escalation hybrid), then an ordered stack of recipes with a role of core, supporting or optional — each one required to quote a phrase from your own brief to justify itself. Just as useful is the rule-out list: the recipes that pattern-match to your words and are the wrong call, with the reason. It comes back with an eval plan that has a pass threshold per check, cost notes naming which lane in your stack dominates spend, a build sequence, and the questions your brief left open — answer two of them and the second route is a different plan, not a reworded one. A free client-side prescan reads your brief for signals of all twenty-one recipes and shows the sentence that triggered each, names what the brief does not say (volume, latency budget, accuracy bar, data location, output shape, cost ceiling), and does the prompt-cache break-even arithmetic in your browser before you spend anything. Derived from the @anthropics/claude-cookbooks skill — the recipe catalogue this routes across.

Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.