The Power of Organized Knowledge (Context)

This is the chapter where Claude's ordering rule earns its keep: put long reference material FIRST and your actual instruction LAST. Paste the whole brand document, policy or transcript at the top inside a tag, and close with the <task> block. Each distinct kind of context gets its own tag - <product>, <audience>, <history>, <constraints> - so the model can tell your background apart from your commands. For context that spans many chats, a Project holds the files and the brief once.

• Long material first, your instruction last. Always.
• One tag per kind of context: <product>, <history>, <constraints>.
• Put recurring brand or policy context in a Project.
• Add a <do_not> tag for the things it must not assume.
• Tell it what to do when the context is silent on something.

<product>
ZenFlow - a smart water bottle that tracks intake and nudges the user when they have not drunk anything for a while.
Design: minimalist, no screen clutter.
Battery: 30 days on a charge.
Integrations: syncs with Apple Health and Google Fit.
</product>

<audience>
Health-conscious tech professionals, 25-40, Indian metros. They already own a fitness band. They are sceptical of gadget clutter, and most have bought one health gadget before that now sits in a drawer. That drawer is the real objection.
</audience>

<offer>
15% early-bird discount, first week only. Goal: pre-orders on our own website.
</offer>

<do_not>
- Do not invent testimonials, star ratings, review counts or user numbers. We are a new brand and have none.
- Do not claim health outcomes we cannot support.
- Do not use more than one call to action.
</do_not>

<task>
Acting as a senior email marketing strategist, write the launch email.

1. Five subject lines on five different angles (problem, curiosity, offer, outcome, specificity), each with a one-line note on the instinct it targets.
2. Body of 150-200 words: open on the real pain point, convert the three features into benefits, single CTA.
3. Three CTA button options.
4. A plain-text fallback version.

Address the drawer objection explicitly somewhere in the body.

Before you write, tell me in one line what you think the strongest angle is for this audience and why - if you are right I will say so, and if you are wrong I would rather find out in one line than in five subject lines.
</task>

<situation>
Anjali, graphic designer, three years with the company. Genuinely talented - the quality is high whenever she delivers.

The problem: for roughly two months she has consistently missed deadlines, which has disrupted the whole team's workflow.

What I have already done: two informal chats. Neither changed anything. She offered no reason either time.

My goal: state clearly that this is now a serious performance issue; find out whether something underlying is going on, without prying; and put a formal Performance Improvement Plan in place. Supportive but firm. I do not want to lose her.

My constraint: this is the first formal PIP conversation I have run.
</situation>

<role>
An experienced HR manager who has run many of these conversations and knows where they go wrong.
</role>

<if_context_is_silent>
Where you would need a fact I have not given - our PIP policy, her contract terms, whether she has a prior record - do not assume one. Name the fact you would need and what I should check before the meeting.
</if_context_is_silent>

<task>
Give me:
1. The opening 60 seconds, written out, that lands the seriousness without triggering defensiveness in sentence one.
2. Three discussion points, each with exact phrasing, and for each what I should be listening for in her reply.
3. Wording for asking whether something outside work is involved, phrased so she can decline without it counting against her.
4. A closing that names the PIP, its duration and the review point.
5. Three likely reactions - defensive, upset, disclosing something real - and how to steer each.

Finally, be straight with me: tell me where my own framing of this looks wrong, and anything here that needs HR or legal input rather than a script.
</task>

<account>
Official tourism account for Hyderabad on X (Twitter). Voice: proud and warm, never try-hard, no slang that will date. Posts are read as representing the city.
</account>

<recent_event>
The annual Hyderabad Food Festival just concluded with record attendance.
</recent_event>

<what_we_know>
A recent visitor survey found culinary tourism is the number one reason people visit Hyderabad. We have the finding but not the percentage, and no attendance figure I can quote.
</what_we_know>

<audience>
Food lovers and travel creators across India.
</audience>

<goal>
Convert the festival's momentum into off-season travel bookings. Likes are not the objective.
</goal>

<constraints>
- Each post under 280 characters including hashtags.
- Each must include #Hyderabad #FoodCapital #IncredibleIndia.
- No invented numbers. No attendance figure, no survey percentage. If a post feels weak without a number, make it stronger some other way.
</constraints>

<task>
Write three posts, each with a distinct job:
1. Momentum - leads on the festival's success and turns it into a reason to come now. Include a specific image suggestion: the dish, the setting, the light.
2. Engagement - a question people actually want to answer, and whose answers we could repost.
3. Traffic - drives to a blog post called 'Hyderabad's Top 10 Culinary Hidden Gems'.

For each, add one line explaining the choice so I can brief my team on the pattern rather than just reusing your copy.
</task>