Prompt chaining when models reason for themselves: when do you still need it?
When to split work into a chain of API calls, the draft–review–refine self-correction pattern, chain design principles and the cost and latency risks.
Tips
Prompts, shortcuts and saving tokens. · 10 articles
All
Claude Code
Claude API
LLM & NLP
AI Agents & Skills
Tips
AI Automation
Tools
System Design
Reading
Prefill is no longer supported: migrating prompts for newer Claude models
From Claude 4.6, last-turn prefill returns a 400. Migration by purpose: JSON, classification, preambles, continuations, context reminders.
LLM-as-a-judge: using models to grade models, the right way
MT-Bench found LLM judges agree with humans over 80% of the time. Three grading modes, four biases and a sample judge prompt.
4 habits of coding agents and the prompts that fix them
Over-engineering, coding to the tests, leftover temp files, guessing at unread code: four coding-agent habits and Anthropic's sample fixes.
6 core Claude prompting principles from Anthropic: clarity, reasons, examples, XML
Treat Claude like a brilliant new hire: be explicit, explain why, give 3–5 examples, separate parts with XML tags, set a role, say what to do.
Prompting with long documents: data first, question last, quotes before answers
Three official techniques for long inputs: documents above the query, XML-wrapped documents with sources, and quote extraction before the task.
Installing MCP servers and skills for fun? Understand prompt injection first
Agents read web pages, emails, GitHub issues… and any of that text can carry hidden instructions. Simple defensive rules for Claude Code users.
Caveman: make Claude talk like a caveman to cut output tokens
A community skill that strips greetings, articles and filler from Claude’s replies while leaving code unchanged. It saves output tokens, but isn’t for every situation.
Type 5 keys, send 1 request: how a 300ms debounce works
A search box that calls the API on every keystroke floods the server with half-typed queries. Debounce waits until you’re done.
setTimeout(fn, 0) runs 50ms later? The event loop explains why
“0ms” doesn’t promise to run now — only to queue early. Microtasks always go before macrotasks.
No matching articles
Try another keyword or clear the topic filter.
Never miss a new article
Follow binhAI via RSS (Feedly, Inoreader, Slack…) to get new articles as soon as they’re published.