Prompt Engineering
The practice of crafting effective instructions to get better, more consistent results from AI tools, from single messages to project-wide rule sets.
Prompt engineering is the skill of writing instructions that consistently get better results from AI tools. This ranges from small techniques (giving the AI a role, providing examples of what you want, specifying constraints and format) to project-level practices like writing persistent rule files that shape how the AI behaves across every interaction. The core principle is simple: the more precisely you describe what you want, the closer the output gets to what you actually need.
The Simple Version
When you ask an AI to “write me a blog post,” you get something generic. When you say “write a 1,000-word blog post for non-technical readers about how PLAN.md prevents AI drift, using a conversational tone, no em dashes, with analogies to business consulting,” you get something much closer to what you actually want.
That second version is prompt engineering. It’s the skill of giving AI instructions that are specific enough to produce useful output. The more precise your input, the better the output.
Why It Matters
Prompt engineering is the most accessible AI skill. You don’t need to code. You don’t need to understand machine learning. You just need to be clear about what you want and learn what kinds of specificity actually help.
At the message level, it’s about structure, role-setting, and constraints. “You are a technical writer for a non-technical audience” is better than “write something.” “Explain in two paragraphs with an analogy” is better than “explain this.”
At the project level, prompt engineering becomes something bigger. Instead of crafting one perfect message, you’re defining rules and conventions that shape every interaction. That’s where it overlaps with context engineering.
How It’s Used on This Site
Every instruction in CLAUDE.md is prompt engineering. “Write for someone who is smart but has never opened a terminal.” “No em dashes.” “Link all technical terms to glossary pages.” “Include a soft CTA, one per post, that reads like a hand reaching out, not a sale being made.” These aren’t one-time prompts. They’re persistent instructions that shape every piece of content Claude Code produces for this site.
Related Terms
Browse the Full Dictionary