P — PURPOSE
I need to {WHAT_YOU_ARE_TRYING_TO_ACHIEVE}, so that
{THE_DECISION_OR_ACTION_IT_LEADS_TO}.

R — ROLE
You are {WHO_CLAUDE_SHOULD_BE} with experience in
{THE_RELEVANT_DOMAIN} in Malaysia.

I — INSTRUCTION + INTERVIEW
{THE_EXACT_JOB — one sentence, one verb}.
Before you produce anything, ask me up to three questions about
anything you need and I have not told you. Wait for my answers.

S — STRUCTURE
Give it to me as {FORMAT: e.g. a one-page brief with 4 headings /
a table with these columns / 6 slides with speaker notes}.

M+ — MEASURE
It is good enough when {THE_TEST — e.g. I could hand it to my
manager without editing / every figure traces to the file I gave you /
it fits on one page}.

  and underneath M, the enhancers you need — not all six:
  Context: {WHAT_YOU_MUST_KNOW_THAT_ISN'T_OBVIOUS}
  Audience: {WHO_READS_IT}
  Tone: {HOUSE_VOICE}
  Constraints: {LENGTH / LANGUAGE / WHAT_TO_LEAVE_OUT}
  Grounding: work only from {THE_FILE_OR_PAGE_I_GAVE_YOU}
  Quality check: before showing me, check {THE_ONE_THING_THAT_IS_USUALLY_WRONG}

P — PURPOSE
{PROSPECT_OR_PERSON} has not replied to {WHAT_I_SENT} sent on
{DATE}. I need a follow-up sequence that gets a decision without
making me sound desperate.

R — ROLE
You are a Malaysian B2B salesperson who follows up firmly and
politely, and who never wastes a customer's time.

I — INSTRUCTION + INTERVIEW
Draft three follow-up messages: day 3, day 10 and day 21 after the
original. Each message must ADD something new — an answer, a
relevant case, a deadline or a decision. None may say "just
following up".

S — STRUCTURE
Three messages. Subject line + body. Under 90 words each. Label
them Day 3, Day 10, Day 21.

M+ — MEASURE
Good when each message could stand alone as a reason to write, and
the third one makes it easy for them to say no.

+ Context: {WHAT_THEY_ASKED_ABOUT / WHAT_STALLED_IT}
+ Tone: warm, direct, no chasing language.
+ Constraints: English. Day 3 by {CHANNEL: email/WhatsApp}, Day 10 by
  email, Day 21 by {CHANNEL}.
+ Quality check: before showing me, confirm none of the three
  contains the phrase "following up" or "checking in".

P — PURPOSE
I have to present {THE_PROPOSAL} to {WHO} on {DATE}. I need a deck
outline that survives a real meeting, not a document read aloud.

R — ROLE
You are a presentation editor who cuts decks down, not one who pads
them out.

I — INSTRUCTION + INTERVIEW
Turn the attached proposal into exactly SIX slides, in this order:
1 their situation in their own words · 2 the cost of leaving it alone ·
3 what I propose, in three moves · 4 why us — ONE proof point ·
5 investment and what is included · 6 the next step with a date.
Invent nothing that is not in the proposal.

S — STRUCTURE
For each slide: a headline of 8 words or fewer, at most 3 bullets of
at most 10 words, and SPEAKER NOTES of 40–60 words saying what I say
out loud — which must not repeat the bullets.

M+ — MEASURE
Good when someone reading only the speaker notes would understand
the whole argument, and slide 1 could not be about any other company.

+ Grounding: use only the attached proposal. If something is missing,
  write "[MISSING: ...]" rather than filling the gap.
+ Audience: {DECISION_MAKER_ROLE}.
+ Constraints: exactly 6 slides. No company-profile slide.
+ Quality check: confirm no bullet exceeds 10 words before showing me.

P — PURPOSE
The same facts have to reach three different readers this week, and
right now I write it three times from scratch.

R — ROLE
You are a business communications editor who changes framing without
changing facts.

I — INSTRUCTION + INTERVIEW
From the document above, produce THREE versions:
(1) STAFF — plain language, what changes for you, when it starts,
    who to ask. No policy or clause numbers.
(2) MANAGER — how to answer the four questions their team will ask,
    and what to escalate.
(3) OWNER / BOARD — cost impact, compliance position, and the risk
    if we do nothing. Ends with the decision being asked for.

S — STRUCTURE
Version 1: max 150 words. Version 2: max 250 words plus a Q&A of 4.
Version 3: exactly one page, ending in a single decision line.

M+ — MEASURE
Good when the three versions share every fact and share almost no
sentences.

+ Grounding: no fact may appear in one version that is absent from
  the source.
+ Tone: version 1 warm, version 2 practical, version 3 neutral.
+ Constraints: English. {ADD_BM_VERSION_IF_NEEDED}.
+ Quality check: list any figure that appears in one version but not
  the others, and tell me whether that is deliberate.

P — PURPOSE
Before I analyse anything I need to agree what a row in this file
means, because right now the same customer appears three times and
I do not trust any total.

R — ROLE
You are a data analyst who cleans before counting and who tells me
what they changed.

I — INSTRUCTION + INTERVIEW
Read the attached file and, before any analysis:
 1. list the duplicate records you can see and how you identified them
 2. list every value used for {THE_MESSY_COLUMN — e.g. Source} and
    propose ONE standard name for each group
 3. tell me which dates are not real dates
 4. tell me what a blank in {THE_BLANK_COLUMN} probably means, and
    what you would need to confirm it
Then produce a written summary of what the file actually contains.

S — STRUCTURE
Four short sections matching the four points, then a summary of no
more than 200 words. Show counts, not percentages, at this stage.

M+ — MEASURE
Good when I can state the total number of real, unique records with
a straight face.

+ Grounding: work only from the file. Do not fill gaps from general
  knowledge.
+ Constraints: change nothing yet — propose, do not apply.
+ Quality check: tell me the one assumption you made that, if wrong,
  would change the totals most.

P — PURPOSE
{WHO_DECIDES} has ten minutes and will not read a table. I need the
one page that tells them what to do about these numbers.

R — ROLE
You are a finance-literate business writer who writes for owners,
not for analysts.

I — INSTRUCTION + INTERVIEW
Write a management narrative from the analysis above, in this order:
the number that changed and by how much · one sentence on the cause,
not the correlation · what it means for cash, capacity or risk · the
decision I am asking for or the decision I already took.

S — STRUCTURE
One page. Four short paragraphs. A single bold decision line at the
end. No tables, no bullet lists.

M+ — MEASURE
Good when the reader could act on it without opening the spreadsheet,
and every figure in it appears in the source data.

+ Grounding: every number must come from the data I gave you. If you
  cannot source a figure, leave it out and say so.
+ Audience: {OWNER / GM / BOARD}.
+ Tone: neutral. No good-news framing, no alarm.
+ Constraints: one page. Plain language — no "attrition", no "synergies".
+ Quality check: list every number you used and where it came from.

P — PURPOSE
Nobody reads the full report. I need only the things that are
outside normal, so somebody actually acts on them.

R — ROLE
You are an exception reporter. You do not summarise everything —
you surface only what breaches a rule I set.

I — INSTRUCTION + INTERVIEW
Using the cleaned data above, list every record where:
 - {RULE_1 — e.g. no contact for more than 14 days}
 - {RULE_2 — e.g. weekly hours above 45}
 - {RULE_3 — e.g. status blank for more than 7 days}
For each one, give me the record, which rule it breached, and the
single next action.

S — STRUCTURE
A table: Record · Rule breached · Days/amount over · Next action ·
Owner. Sorted worst first. If nothing breaches a rule, say so
explicitly — do not pad the list.

M+ — MEASURE
Good when the list is short enough that someone will act on all of
it today.

+ Grounding: use only the cleaned data above.
+ Constraints: no commentary, no summary paragraph. The table only.
+ Quality check: confirm the count of exceptions and tell me what
  percentage of all records that is.

P — PURPOSE
I will run this same report every month. I do not want to rewrite
the prompt each time, and I do not want a colleague to get a
different answer from the same data.

R — ROLE
You are a process documenter. You turn one-off instructions into
repeatable ones.

I — INSTRUCTION + INTERVIEW
Take the prompt that produced the output above and turn it into a
reusable template. Pull every specific value out into a clearly
named slot in CAPITALS. Add a short header stating: what this
template is for, which file it runs on, what date range, and who
owns the output.

S — STRUCTURE
A template block I can copy, with the slots listed underneath and
one line each explaining what to put in them.

M+ — MEASURE
Good when a colleague who was not in this room could run it next
month and get an output the same shape as mine.

+ Constraints: nothing specific to this month may remain in the
  template body.
+ Quality check: read your own template back and list anything still
  hard-coded that should be a slot.

P — PURPOSE
I need my tracker to tell me {WHAT_YOU_WANT_TO_SEE} without me
reading every row.

R — ROLE
You are a spreadsheet builder who explains formulas to people who
will have to maintain them.

I — INSTRUCTION + INTERVIEW
Write a formula that {DESCRIBE_THE_OUTCOME_IN_PLAIN_ENGLISH — e.g.
"flags any staff member over 45 hours in a week" / "shows days since
last contact"}.
My data is in {SHEET_NAME}. Headers are in row {N}. The columns are:
{COLUMN_LETTER} = {WHAT_IT_HOLDS}   (list every column you need)
Give me the formula AND an explanation of what each part does, in
plain English.

S — STRUCTURE
1. The formula, ready to paste
2. Which cell to paste it into
3. A plain-English explanation, one line per part
4. One example: "if row 7 contains X, this returns Y"

M+ — MEASURE
Good when I could explain this formula to the person who inherits
this sheet, without opening Claude.

+ Constraints: {GOOGLE_SHEETS or EXCEL} — say which, they differ.
+ Quality check: tell me what this formula does if the cell is blank,
  and what it does if the date is stored as text.

P — PURPOSE
I have been giving Claude the same instruction all day. I want it
written down as a Skill so it runs the same way every time, and so
it fits how business is actually done here.

R — ROLE
You are an SOP writer. A Skill is a digitised SOP — a procedure
followed the same way twice.

I — INSTRUCTION + INTERVIEW
Turn the instruction below into a Skill definition. Include: a name,
when to use it, when NOT to use it, the file or data it runs on, the
steps, and the output shape.
Then tell me which parts of it assume a non-Malaysian business, and
propose fixes.

    [PASTE YOUR BEST PROMPT OF THE DAY HERE]

S — STRUCTURE
Part A: the Skill definition.
Part B: a table — Assumption found · Why it does not fit here ·
My fix.

M+ — MEASURE
Good when a colleague could run it without asking me a question,
and when I can name at least ONE thing I deliberately changed for
Malaysian practice and say why.

+ Context: we are a {INDUSTRY} business in {STATE}, {N} staff.
+ Constraints: plain language. No jargon a new staff member would
  not know.
+ Quality check: list anything in the Skill that would break if the
  source file's column names changed.

P — PURPOSE
Right now I am the only person who can run this. I want my team to
install it and get the same result without asking me how it works.

R — ROLE
You are packaging this for a colleague who was not in the room and
who will not read documentation.

I — INSTRUCTION + INTERVIEW
Take the Skill above and prepare it for packaging as a Plugin.
Give me:
 1. a one-line description a colleague would understand
 2. what they must have ready before running it
 3. the three most likely mistakes and what to do about each
 4. what this Plugin must NEVER do without a human approving first
 5. who in the team should be allowed to run it

S — STRUCTURE
Five short numbered sections. Section 4 as a bulleted list of hard
rules written in the negative ("must not ...").

M+ — MEASURE
Good when a colleague installs it, runs it once, and does not
message me.

+ Constraints: plain language. Assume no AI experience.
+ Quality check: reread section 4 and tell me whether anything in
  sections 1-3 contradicts it.