PROMPTS
1346 original and curated AI prompts across image, video, music, and tutorials. Browse by tool, use case, and difficulty; each entry shows its available notes and examples.
Filters2 activeExpandCollapse
Context Engineering: What Separates You in 2026 Isn't the Incantation, It's the Ingredients
Feed the AI structured background, what's already been tried, constraints, and available tools/data structures before giving it the task — in 2026 the real leverage point has shifted from 'prompt tricks' to 'context.'
Prompt Chaining: Split a Big Task into Three Steps for Better Quality
Don't feed an entire complex task into a single prompt — split it into three separate steps ('decompose → produce each part → integrate'), and the output is noticeably more stable and complete.
Self-Critique Revision Loop: Draft, Self-Criticize, Revise — Three Rounds of Polish in One Prompt
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.
Rubric-Driven Output: Tell AI What a Perfect Score Looks Like First
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.
The Anti-Goal Sandwich: One Line to Stop AI's Most Common Mistake
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.
XML Tag Structuring: 28% Fewer Parsing Errors Than Markdown
Wraps instructions, data, rules, and schemas in XML tags when feeding them to an AI — tested to produce roughly 28% fewer errors on structured-extraction tasks than using Markdown headers.
Contrastive Example Calibration: Show It What You Want AND What You Don't — One Negative Example Beats Three Positive Ones
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.
Chain-of-Thought Scaffold: A Fixed 5-Step "Think Before You Answer" Process
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.
5 Claude Repeat-Task Templates That Lasted 6+ Months — and the 3 Retention Rules
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).
5 Prompt Engineering Techniques That Actually Move the Needle (XML Beats Markdown by 28%)
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.
A Red Teamer's View: 3 High-Capability Prompt Patterns That Work Across Models
Three patterns shared by the HackAPrompt 2.0 champion: frame the task as an audit, make the abstraction level explicit, and stage the context like production. They work on Claude, GPT, and Gemini alike.
AI Agent Harness Engineering: Separating the LLM from the Deterministic Orchestration Layer
Mitchell Hashimoto's "Agent = Model + Harness" framework. The reason 88% of enterprise AI agents never reach prod isn't the prompt — it's the missing deterministic orchestration layer. Four CS primitives you can't skip: state machine, idempotency, DAG, DLQ.
reClaim: Turn a Frontier Model Into a Research Agent With Confidence Scores
Scores every claim on three axes (A: sources / B: counterevidence / C: completeness), plus a 4-tier source hierarchy, adversarial self-poking, and 4 output modes.
A Universal Decision Prompt: Use "What Will You Regret in a Year" to Force a Verdict
Stop picking a role for every decision (financial planner / career coach / relationship coach) — one universal prompt, four steps. The regret line is the core — it forces the model from "it depends" to "actually do this."
CV Writer Ruleset: It Interviews You STAR-Style and Bans "Dynamic Team Player"
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.
Voice Memo → Tomorrow's Priorities (With a Confirmation Round)
Before you log off, ramble into your phone mic for 2 minutes, hand it to Claude, and get back a sorted list: first thing tomorrow morning + ranked to-dos + waiting-on + can-defer. Auto-detects daily vs. weekly mode.
The 60-Second Pre-Send Check: Catch the Message You'll Regret Tomorrow Morning
The author wrote this after 30% of their heated replies made them wince the next day — costing a few deals and a friendship. The trick: don't let AI rewrite it, let it show you what the calm version would look like. Once you see it, you usually can't go back to the original.
Flip Your AI Dev Workflow: Generate the Prompt First, Then the Code (4 Phases)
Instead of telling AI to write code directly, have it translate a vague goal into an executable prompt structure first, then use that structure to drive code generation. Phase 1 Intent → Phase 2 Structuring → Phase 3 Tool-Level → Phase 4 Implementation.
Run an Architecture Review on Your Whole Codebase with Claude
Upload the repo and Claude returns an architectural map, the top 5 fixes to prioritize, and the file paths to back them up.
1-Page Decision Memo for the CEO
A one-page decision memo for a CEO, board, or VC. Compresses 30 pages of analysis into a single clear document readable in 5 minutes before a meeting, in the style of Amazon's PRFAQ or McKinsey's SCQA.
One-Page Product PRD Draft
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.
Batch E-Commerce Product Copy for 30 SKUs
Give Claude basic data for 30 SKUs (name, category, selling points, materials) and get back 30 complete sets of 'title + store summary + 3 bullet features + description paragraph' in one pass—a 10x speedup for small brands listing products.
STAR Interview Answer Bank Generator
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.
Manager-Level Quarterly Self-Review Document
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.