1 link tagged with all of: system-design + prompt-engineering
Click any tag below to further narrow down your results
Links
Most LLM failures come from poorly written system prompts, not model selection. This guide covers the specific structures (XML tags for Claude, markdown for GPT), token budgeting strategies, and five patterns that consistently work—like making roles absurdly specific, showing exact output schemas instead of describing them, and explicitly telling models when to admit they don't know something. Testing matters too: run your prompts through happy paths, edge cases, and adversarial inputs multiple times before deploying.
- A 400-token system prompt outperformed a bloated 3,000-token version because the model got confused parsing everything at once
- Showing exact JSON schemas instead of describing them jumped format compliance from 70% to 95%+
- Claude performs 15-20% better with XML tags while GPT prefers markdown with JSON schemas and Gemini prefers markdown with numbered rules
- One ambiguous instruction (like "include all relevant context" next to a JSON format requirement) can cause a week of debugging