1328 hand-tested AI prompts across image, video, and music — each with full context, variables, and a sample output. Content is authored in Traditional Chinese; the UI here is English.
Has the AI produce a first draft, then switch into a strict editor role to pick apart its own flaws, and finally rewrite based on that critique — effectively running three rounds of polish inside a single prompt.
Write out the grading rubric in your head and give it to the AI first — it will use that yardstick to self-align, self-evaluate, and fix whatever falls short, getting you much closer to the quality you actually want.
Explicitly naming "the most common failure mode AI makes on this type of task" in the prompt and telling it to proactively avoid that mode — 2026 field tests show roughly a 28-30% reduction in errors.
Demonstrate both the 'desired output' and the 'output that shouldn't appear' at the same time, so the AI calibrates between the two poles; for tasks about tone and precision, a single negative example often outperforms three positive ones.
Forces the AI to think through 5 fixed steps before answering — restate → list assumptions → reason step by step → self-check → conclude. Field tests show roughly a 30% reduction in confidently wrong answers on complex reasoning tasks.
After 18 months of testing 60 Claude workflows, the retention pattern: annoying but not painful, output has a destination, input under 30 seconds. The 5 templates that survived 6+ months (Friday review / meeting follow-up / client weekly report / Monday briefing / pipeline update).
Five quantifiable techniques from an AI engineer's hundreds of hours testing across GPT-4, Claude, and Gemini: CoT scaffolding, persona + goal + anti-goal, XML being 28% more accurate than markdown, negative examples outperforming positive ones, and prompt chaining beating the mega-prompt.
The pain of writing a CV isn't the layout — it's listing duties instead of achievements, then having AI pile on and turn you into a "dynamic team player." This ruleset forbids AI from drafting anything until it has your evidence and positioning, and walks you through one question at a time.
A first-draft Product Requirements Document: a 3-sentence problem statement → 5 user stories → an API contract → success metrics. A spec engineers can start building from immediately.
Give Claude the target job description plus 5 real work incidents of yours, and it produces 5 STAR-format interview answers you can rehearse the night before the interview.
Give Claude a summary of your emails, meeting notes, and Slack messages from the past 90 days, and it produces a 'quarterly self-review'—achievements, failures, lessons learned, and next quarter's goals. Done 30 minutes before your performance review.
Give Claude the guest's bio, the show's theme, and the angle you want to dig into, and it produces a complete 60-minute interview outline—15 main questions, backup follow-ups, and an opening/closing design.
PRO13You have one generic resume and want to apply to 10 companies at once. Claude reorders and re-emphasizes it for each job description without changing any facts.
PRO14Not a casual 'take a quick look at this code' request. One command yields a full review of the PR across four dimensions: scope/impact, security, performance, and readability.
PRO15Give it a topic, length, and platform, and it instantly produces a storyboard plus prompts ready to feed straight into Sora or Runway.