Lesson 1 of 25

The Principle of the Definite Chief Aim

A prompt gets you what you actually asked for, so the useful skill is naming the exact thing you want: who it is for, how long it should be, what it must cover, and what you will do with it. Vague asks get average answers because the model has to guess, and it guesses towards the middle of everything it has ever read.

Reach for it whenAny time your first answer came back bland and generic, and you are about to retype the same request in slightly different words.

Separate the parts of your ask with XML-style tags - <goal>, <audience>, <constraints>, <material> - so nothing gets read as part of something else. When you are pasting in long material such as a resume or a draft, put that material at the top and your instruction at the very bottom; Claude follows the last instruction most reliably. Ask it to state its understanding of the aim before writing, and you will catch a misread aim in one line instead of 800 words.

Worth knowingTags are only labels - they do nothing unless what is inside them is specific. A <constraints> block that says 'make it good' is no better than no tag at all.
  • Tag each part: <goal>, <audience>, <constraints>, <material>.
  • Paste long material first, put your instruction last.
  • Ask it to restate the aim in one line before writing.
  • Keep a recurring brief in a Project so chats share it.
  • Ask for the deliverable as an Artifact when you will keep editing it.
Example 1: The Vague Wish vs. The Definite Aim

Instead of

Write something about the benefits of exercise.

Perplexity version

<goal>
An 800-word persuasive blog post that gets a reader to start exercising this week.
</goal>

<audience>
Salaried professionals aged 30-45 in Indian cities. Desk jobs, long commutes, almost no free time. They already know exercise is good for them - being told again will not move them.
</audience>

<must_cover>
1. Mental clarity and sharper focus at work
2. Lower stress and better sleep
3. Long-term protection against lifestyle diseases common in India, especially type 2 diabetes and hypertension
</must_cover>

<constraints>
- Tone: authoritative but warm. No hype, no fear, no emoji.
- Structure: one title, three sections, short paragraphs.
- End with three zero-equipment starting points: stairs instead of lift, a 20-minute walk after dinner, a 15-minute home workout.
- Write for a general reader. If you would normally cite a statistic, describe the direction of the evidence instead of inventing a precise figure.
</constraints>

<task>
First, write one line stating what you understand the aim to be. Then write the post as an Artifact so I can edit it with you.
</task>
Open Perplexity 1,089 characters
Example 2: From Idle Curiosity to a Strategic Plan

Instead of

How can I use social media for my business?

Perplexity version

<business>
A new online store in Kondapur, Hyderabad selling handmade leather goods - wallets, belts, laptop sleeves. Premium but not luxury pricing. No ad budget in month one.
</business>

<customer>
Style-conscious men aged 25-45, mostly in Hyderabad, Bengaluru and Pune.
</customer>

<objective>
Brand awareness first, traffic to the store second.
</objective>

<format>
A markdown table, one row per week, with these columns: Week | Theme | 5 Post Ideas (name the format) | Hashtag Set | What To Measure.
Then a section called Shooting List covering every photo and video I need, grouped so I can shoot a month of content in one day.
</format>

<if_unsure>
If something about the business would change your plan - stock levels, whether I can film the workshop, whether I ship outside Hyderabad - do not guess silently. Make the most reasonable assumption, mark it clearly as an assumption in the row it affects, and list all such assumptions at the end.
</if_unsure>

<task>
Build the 30-day Instagram plan described above. Output it as an Artifact.
</task>
Open Perplexity 1,061 characters
Example 3: From a Simple Request to a Solved Problem

Instead of

Help me with my resume.

Perplexity version

<resume>
[paste your full current resume text here - all of it, formatting included]
</resume>

<background>
I am a software developer in Hyderabad with 5 years of backend work in Python and Java. I have led small teams informally - running stand-ups, dividing work, handling client calls - but none of it appears on the resume. I am targeting Project Manager and Delivery Manager roles at mid-size Indian IT services and product companies.
</background>

<task>
Rewrite the resume above for those project management roles.

1. Lead with leadership, stakeholder communication and planning. Demote deep technical detail to credibility, not the main story.
2. Rewrite each work-experience bullet around an outcome. Where I have given you no number, write [metric?] rather than inventing one - I would rather fill a gap than ship a false figure.
3. Add a Professional Summary of at most four sentences framing me as a developer who already does the job.
4. After the rewritten resume, list every [metric?] you left and the specific question I should ask myself to fill it.

Before rewriting, tell me in two or three lines which parts of my current resume are actively working against a PM application.
</task>
Open Perplexity 1,206 characters