A plain Claude chat does not remember your niche, who your audience is or how you write — you end up explaining all of it again in every new conversation. A Project fixes that: you write the instructions once and they apply to every chat inside the project. Below is exactly what to put in those instructions, plus three prompts that cover the basics of running a blog.
The point: instructions matter more than prompts
A good prompt without context gives you a good answer once. Instructions in a Project give you a good answer every time, because Claude checks against them in any chat inside the project, not just in the first message of a conversation. So the project goal field should hold rules rather than a task ("write me a post"): your niche, your audience, your tone and what is off limits.
Step 1 — create the Project and write the instructions
When you create a Project there are two fields: what you are working on and what you want to achieve. The first one gets a short name for the direction ("content for a blog about AI tools"). The second one gets the full instructions:
Niche: [your niche].
Audience: [who reads it and why].
Tone: [conversational / expert / provocative].
Always: a strong hook in the first line, specifics
instead of generic phrasing, a clear call to action
at the end.
Never: bureaucratic language, claims without proof,
untranslated jargon.
You write this once — from then on Claude keeps it in context in any chat inside the project.
Step 2 — a prompt for a viral post
The goal is not one hook but several options, each built on a different emotional trigger, so you can compare them and pick the strongest.
You are a viral content writer. Niche: [niche].
Audience: [who]. Give me 3 hooks with different
triggers — fear of loss, curiosity, challenge.
After each one, 3 lines of payoff and an explicit CTA.
Step 3 — a prompt for a two-week content plan
What sets this apart from a plain list of topics is that every post comes with a format, a goal and a first-line hook, so the plan does not turn into a row of abstract headlines.
You are a content strategist. Niche: [niche],
audience: [who], platform: [platform]. Build a
two-week plan: for each post give the topic, format,
goal (reach / trust / sales) and the first-line hook.
Alternate between useful, personal, sales and viral
formats.
Step 4 — a prompt for adapting someone else's content
If you like another creator's format, do not copy it one to one — that turns into plagiarizing the mechanics. The job of this prompt is to keep the technique but change the angle, the hook and the delivery to fit your niche.
Here is an example of a post that worked well for
another creator: [paste it]. My niche: [niche], my
style: [style]. Adapt it for me — different angle,
different hook, same engagement mechanic.
How to use this: one Project, not one chat
All three prompts work inside the same Project, so Claude sees the instructions and the earlier answers instead of starting from scratch every time. If the task changes a lot (say you run two blogs with different audiences), it makes more sense to create a separate Project for each rather than mixing instructions in one.
How we do it
The ready-made instruction template for a Project and all three prompts in full are in the qvib.pro knowledge base — out in the open, no DMs or code words required. The same principle — context configured once instead of repeating the brief — is the basis for how the qvib engine assembles content and code to a given structure.
Related links
- The "Claude" section of the knowledge base: qvib.pro/arsenal/claude/
- The "Content prompts" section: qvib.pro/arsenal/prompts/
- How the qvib engine works: qvib.pro/