Include six components: your role context, the specific query, the post structure template, voice instructions, your expertise inputs (methodology, real examples, your position), and internal link targets. The most important is your expertise inputs. They’re what makes the content distinctly yours instead of generic. Paste a literal structural template and Claude will follow it precisely.
Build a reusable system prompt that contains your role context, voice instructions, and structural template. Then use a shorter per-post prompt that includes only the query, your expertise inputs, and the internal link targets for that specific node.
Separating the stable elements (system prompt) from the variable elements (per-post prompt) makes production faster and more consistent. Claude remembers the context; you only supply what changes each time.
Read node-1 in this cluster for how prompt quality fits into the broader content production system. And how it drives the quality of your review process downstream.
The first component of a strong prompt is role context. A clear statement of who you are, what you know, what methodology you use, and what you fundamentally believe about your field. Claude uses this context to calibrate the voice, depth, and framing of everything it generates.
A strong role context statement for an content prompt looks like this:
You are writing as Cindy Anne Molchany, founder of Perfect Little Business
and creator of the Authority Directory Method. You help entrepreneurs
build AI-discoverable websites that generate qualified leads without social
media dependency. Your methodology teaches structured, query-based content
architecture. Pillar-cluster-node. Combined with schema markup and
off-page authority building. You believe experts get recommended by AI when
their digital presence is structured clearly enough for machines to read and
cite it. You do not believe in hustle, urgency, or manufactured scarcity.
This role context gives Claude a frame of reference for every decision it makes: what to include, what to emphasize, what to avoid, and what perspective to bring to questions where multiple framings are possible. Without it, Claude defaults to the most common framing of a topic. Which is rarely the most expert one.
Voice is the most difficult quality to maintain at scale because it is the most subtle. A structural template can be followed precisely. Voice drifts without active guidance.
Effective voice instructions in a prompt include:
The example is disproportionately effective. Show Claude a paragraph that sounds like you, and tell it: "Match this tone throughout." Claude models voice from examples more accurately than from descriptions alone. Include both.
The structural template is the post format you want Claude to produce. Include it literally in the prompt. Not a description of it, but the actual template with section names, content requirements, and sequence.
For an authority directory node post, the structural template looks like this:
STRUCTURE. Follow this exactly:
TL;DR (3 paragraphs, direct answer, no bold)
. Paragraph 1: The core direct answer
. Paragraph 2: The mechanism or system
. Paragraph 3: What makes this approach distinctive
H2 #1. [Related question on this topic] (150–200 words)
H2 #2. [Another related question] (150–200 words)
H2 #3. [Another related question] (150–200 words)
H2 #4. [Another related question] (150–200 words)
H2 #5. [Another related question] (150–200 words)
VCYL Perspective (3–5 paragraphs, first person, Cindy's POV)
FAQ (5 questions with conversational answers, no bold in answers)
When the template is this explicit, Claude produces the right structure on the first draft consistently. When it's a vague instruction like "write a well-structured blog post," Claude interprets structure according to its training data. Which may be quite different from what you want.
This is the most important component. Expertise inputs are the specific knowledge, examples, and positions that come from your professional experience and methodology. They cannot be generated by Claude from context alone. They must come from you.
For each post, your expertise inputs should include:
For the post you're reading, the expertise input might be: "I built a directory business in 2014 that grew through SEO and content. I sold it when SEO declined. Years later, watching AI recommend my name directly to a prospective client who signed within 20 minutes, I understood why structured content matters for the current era. My methodology, the Authority Directory Method, came from that moment." That level of specificity is what Claude needs to write content that sounds like it came from you.
The final component is practical: the specific links this post should include, the post's URL, and the canonical metadata. Including this in the prompt means Claude drafts the links into appropriate places in the body copy. Rather than leaving you to insert them manually during review.
For each post, specify:
This component makes internal linking a built-in step rather than an afterthought. When links are specified in the prompt, they appear in the draft. When they're not specified, they get forgotten. And the internal link network that drives topical authority never fully develops.
I want to share the honest experience of learning to prompt well. Because it is not intuitive at first. Early prompts feel like you're over-explaining. You have the urge to just say "write me a blog post about X" and see what happens. What happens is a post that is competent, complete, and completely generic. It answers the question the way any informed writer would answer it. It does not answer it the way you would answer it.
The shift happens when you start loading your prompts with your actual positions. Not "here's what the research says about X" but "here's what I tell my clients about X, which is different from what most people say, and here's why." That shift. from providing a topic to providing a perspective. Is where your voice enters the content. And it only happens through the prompt.
There is something deeply satisfying about a well-loaded prompt. When you submit it, you have already done the thinking. You know what you believe about the question, what example best illustrates your point, and where your methodology diverges from the conventional approach. Claude is organizing and articulating that thinking. Not inventing it. The work of knowing what you think is the real work. Prompting is how you transfer that knowledge into a publishable post.
The Vibe Coding approach. Partnering with AI as a thinking and building partner. Works best when you bring genuine intellectual content to the partnership. You are not replacing your expertise with AI. You are using AI to amplify and articulate expertise you already hold. The clearer you are about what you know and believe, the better AI serves as your creative partner.
A fully loaded prompt for a blog post is typically 300–600 words. This feels long compared to a casual prompt, but the investment is proportional to the output quality. A detailed prompt generates a draft that needs 20% editing. A bare prompt generates a draft that needs 60% rewriting. And that rewriting takes longer than writing a better prompt from the start.
Either works, but a system prompt is more efficient for production at scale. Set your role context, voice instructions, and structural template in the system prompt once. Then use the user prompt for each post's specific inputs. The query, your expertise points for that topic, and the internal link targets. This separation keeps the setup clean and the per-post prompting fast.
Your specific expertise inputs. Your methodology, your real examples, your position on the question. Everything else in the prompt creates the container. Your expertise inputs are what fills the container with something only you can provide. Without them, Claude will produce competent but generic content that could have been written by anyone in your field.
Describe your voice in concrete terms: the energy level, the perspective (peer-to-peer vs. mentor), how you handle complexity (explain the why before the how), and what you never do (hype, urgency language, over-explaining). If you have existing writing that exemplifies your voice, paste a short excerpt and tell Claude this is the model. Voice instructions plus an example are more effective than voice instructions alone.
Include the actual template. Not just a description. Paste the exact section headers, element names, and structural requirements you want Claude to follow. The more literal your structural specification, the more consistently Claude will produce the format you need. Vague structural descriptions produce vague structural adherence.
Take the free AI Visibility Scan to discover your current positioning. Or explore the complete build system.