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.

State the outcome and the hard constraints as a short block at the top, then the details as a numbered list. On reasoning models you do not need to tell it to think or to be thorough; you need to tell it what 'done' looks like, because it will plan against that. Anything true about you every time (your city, your business, your job) belongs in Custom Instructions, not retyped into each prompt.

Worth knowingCustom Instructions apply to every new chat, so background you put there will quietly leak into unrelated work. Keep it to durable facts, and override it in the prompt when a task needs something different.
  • Put your city, trade and audience in Custom Instructions once.
  • Name the deliverable and length in the first line.
  • Skip 'think step by step' on reasoning models; state success criteria instead.
  • Move long drafts into Canvas before you start editing.
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 makes a busy reader actually start exercising this week.

Audience: salaried professionals aged 30-45 in Indian cities - long commutes, desk jobs, very little free time.

Cover exactly these three benefits, in this order:
1. Mental clarity and sharper focus at work
2. Lower stress and better sleep
3. Long-term protection against lifestyle diseases that are common in India, especially type 2 diabetes and hypertension

Constraints:
- Tone: authoritative but warm. No hype, no scare tactics, no emoji.
- Use markdown: one H1, an H2 per benefit, short paragraphs.
- Close with three starting points someone can do today with zero equipment (stairs instead of lift, 20-minute walk after dinner, 15-minute home workout).

Done means: a reader who has 'start exercising' permanently on their to-do list finishes this post knowing which single thing to do tonight.
Open Perplexity 904 characters
Example 2: From Idle Curiosity to a Strategic Plan

Instead of

How can I use social media for my business?

Perplexity version

Build me a 30-day Instagram content plan.

The business: a new online store in Kondapur, Hyderabad selling handmade leather goods - wallets, belts, laptop sleeves. Price band is premium but not luxury.
The customer: style-conscious men, 25-45, mostly in Hyderabad, Bengaluru and Pune.
The objective: brand awareness first, website traffic second. I have no ad budget for month one.

Output as a markdown table with one row per week and these columns: Week | Theme | 5 Post Ideas (say the format - Reel, carousel, static, Story) | Hashtag Set | What I Should Measure.

Suggested themes to work from: Week 1 brand story, Week 2 craftsmanship, Week 3 the customer, Week 4 offers and social proof.

After the table, add a short section called 'Shooting list' telling me every photo and video I need to capture, so I can film one weekend's worth of content in a single day.

Then ask me up to three questions whose answers would make this plan sharper.
Open Perplexity 947 characters
Example 3: From a Simple Request to a Solved Problem

Instead of

Help me with my resume.

Perplexity version

I am moving from software development into project management and my resume still reads like a developer's.

About me: 5 years building backend services in Python and Java, currently in Hyderabad. I have led small teams informally - running stand-ups, splitting work, talking to clients - but none of that is on paper. Target roles: Project Manager / Delivery Manager at mid-size Indian IT services and product firms.

My current resume text:
[paste resume here]

Rewrite it so that:
1. Leadership, stakeholder communication and planning are the things a recruiter sees first.
2. Deep technical jargon is reduced to proof of credibility, not the main story.
3. Every work-experience bullet states an outcome with a number where I have one. Where I have not given you a number, leave a clear [metric?] marker rather than inventing one.
4. There is a new Professional Summary of no more than four sentences, positioning me as a developer who already does PM work.

Put the rewritten resume in Canvas so I can edit it with you line by line. Below it, list every place you flagged [metric?] so I can go find the real figures.
Open Perplexity 1,121 characters