Skip to content

A FIELD GUIDE FOR WORKING WITH CLAUDE

Good ideas deserve
better prompts.

Move from a blank chat to a clear next step. A practical collection of 120 prompt patterns for the writing, coding, and decisions you make every day.

Card, Apple Pay, Google Pay.
Explore the samples

One payment Lifetime updates Yours to keep

THE PROMPT WORKSPACE
01 / START WITH THE TASKFREE TEMPLATE

Make this sound more human.

A clearer editing brief

Edit the draft below for [audience] who needs to [take a specific next step]. Keep the meaning and factual claims within the supplied source material. Voice reference: [paste a short sample of your own writing that you have permission to use] Prefer concrete nouns, direct verbs, and sentences I would say aloud.

Read the complete prompt
Adapt it. Run it. Check it.

An editable starting point. Results depend on your task.

120prompt patterns
12task categories
10workflow playbooks
$19 onceevery section included

THOUGHTFUL TOOLS. EVERYDAY WORK.

Find your way to
a more useful answer.

A reference you can actually use.
Choose a task, adapt a pattern, and check the result against your own work.

01 / THE REFERENCE

Less searching.
More starting.

Prompt patterns organized around what you need to do, with worked examples and notes on when to leave a pattern out.

/skeptic Question an assumption/ghost Give your writing direction/eli5 Explain with more clarity
Open two actual entries
02 / FIND YOUR TASK

Made for your
kind of work.

Write & edit Build & debug Think & decide

Start with a useful question.
Then give it the context it deserves.

03 / GO A STEP FURTHER

One good prompt.
A repeatable workflow.

Playbooks and combo templates help you connect individual prompts into a sequence you can revisit.

Try three free workflows

A SIMPLE PRACTICE

Make it yours.
Then make it useful.

  1. 01

    Choose the job

    Find a pattern for the task in front of you.

  2. 02

    Add your context

    Replace the placeholders with your goals and constraints.

  3. 03

    Check the result

    Review the output. Keep what helps. Question what does not.

Try two before you buy · No email required

Two entries, straight out of the sheet.

Every one of the 120 patterns looks like this: what it does, the exact prompt, the recorded before and after, and when to skip it. Copy either prompt, swap in your own task, and see the difference in Claude right now.

/skeptic

Tells Claude to challenge the premise of your question before answering it. Most prompt prefixes change how Claude answers. /skeptic changes which question Claude attempts to answer in the first place. That distinction is what makes it the only code I would defend as a real logic intervention rather than a structural tweak.

Prompt from the reference

/skeptic Should I add a referral program to my SaaS where buyers earn 30% commission for every new buyer they refer?

Read the recorded before / after

Original prompt

Should I add a referral program to my SaaS where buyers earn 30% commission for every new buyer they refer?

Before

Generic Claude: A 400-word writeup of how to structure a referral program — commission tiers, attribution windows, payout cycles, fraud prevention. Useful if you should build a referral program. Disastrous if you shouldn't.

After

"Before I answer the structural question, I want to challenge the premise. How many existing customers do you have? If the answer is under 50, a referral program is almost certainly premature. The signal-to-noise on referrals is too low at small scale, and you'll spend more time building the program than it pays back in qualified referrals. The right move at <50 customers is to personally ask each existing customer for one specific intro, not to build a system. If you're over 50 customers, here's how I'd structure it..."

The first version answers the question. The second version catches the wrong question before answering, then answers the right one if it survives the challenge. In the test, this exact prompt was run by a founder with 4 customers. The referral program would have been a weekend wasted.

When to skip it

Factual questions ("what year was X founded") — adds friction with no upside

/ghost

Strips the structural patterns that make AI writing recognizable as AI writing. Specifically: em-dashes used for rhetorical pauses, transitional phrases that mark essay structure, balanced sentence pairs (one short sentence followed by one long sentence repeated as a pattern), and meta-commentary like "I hope this helps" or "let me know if you need clarification." The output reads like a tired human typed it at 11pm — slightly less polished, much more believable.

Prompt from the reference

/ghost Write a cold email to a SaaS founder about my product.

Read the recorded before / after

Original prompt

Write a cold email to a SaaS founder about my product.

Before

Generic Claude: "Dear [Founder], I hope this email finds you well. I wanted to reach out to introduce you to our innovative platform — a comprehensive solution that streamlines your sales workflow. Furthermore, our product has been carefully designed to integrate seamlessly with your existing tools. I would love to set up a quick 15-minute call to discuss how we can help you achieve your goals. Looking forward to your response! Best regards, [Name]" — every sentence is an AI tell. The recipient deletes it before finishing the first paragraph.

After

"Hey [Founder], saw your post about response rate plateaus last week. Built a thing that might help — it loads ten distinct sales philosophies (Collison, Benioff, etc.) and writes outreach in their voices instead of generic AI tone. Free version at [link], $599 for the full pack. Reply with 'send it' if you want details. — [Name]" — no em-dashes, no transitional phrases, no "I hope this finds you well," no "looking forward to your response." Reads like a real person wrote it.

The structural difference is enormous and the audience that matters can spot it instantly. Modern technical buyers have spent two years training themselves to recognize and delete AI-generated emails. /ghost is the single most important defense against that filter.

When to skip it

Technical documentation that needs to sound authoritative — /ghost makes it sound casual and slightly broken on purpose

A few words from buyers unfiltered.

Bought it mostly out of curiosity. The placebo verdicts section alone was worth it. I was using three prompts that apparently do nothing.
Verified purchaseClaude user
Used two of the combo-stacking prompts on a client deliverable this week and it saved real time. This is the first prompt resource I have paid for that felt tested rather than guessed.
Verified purchaseClaude user
The anti-pattern library changed how I write prompts more than the codes themselves did. Small purchase, disproportionate value.
Verified purchaseClaude user
Solid for the price. Wish there was a searchable index instead of scrolling the PDF, but the before/after examples are genuinely useful.
Verified purchaseClaude user
Good honest tone throughout, appreciated that it tells you what does not work instead of just selling hype. Delivery was instant which I did not expect for $15.
Verified purchaseClaude user
Decent reference but I expected more depth on the failure-mode warnings. Half of them are one line. Still cheaper than the hours I would have spent testing myself.
Verified purchaseClaude user
It is fine. Not life-changing, but I do not regret the $15. Would not recommend at a higher price point though, the depth does not quite match a $49 pack.
Verified purchaseClaude user
Some codes felt like stuff I could have found free on Reddit. The token-delta data is the actual differentiator, more of that and less repackaged basics would have made this better.
Verified purchaseClaude user
Felt like I should have gotten a bigger sample before judging the rest of it. Could be clearer upfront about what you get.
Verified purchaseClaude user

THE COMPLETE CLAUDE CHEAT SHEET

Your second monitor’s
new best friend.

A compact reference for the moments when you know what you want to do, but need a better way to ask.

Markdown Web referencePrint-to-PDF
Start with the free guide
$19one-time payment
No subscription.
  • 120 prompt patterns, organized by task
  • Worked examples and when-to-skip notes
  • 10 workflow playbooks + 20 combo templates
  • 20 bonus prompts and an anti-pattern library
  • Markdown + web reference + print-to-PDF
  • Lifetime updates and 30 days of builder email access
Card, Apple Pay, Google Pay.

Personal license. Refund policy · Already purchased?

A FEW THINGS TO KNOW

Good questions.
Clear answers.

Still wondering about something?
Let’s talk

Before you buy

Is this for Claude chat or Claude Code?
The Cheat Sheet is a reference of plain-language prompt patterns for Claude. Its shorthand names are not official slash commands. Installable Claude Code skills are a separate product in the library.
What exactly do I get?
All 120 prompt patterns, worked examples, usage notes, deep dives, 10 playbooks, 20 combo templates, 20 bonus prompts and the anti-pattern library. It is one personal license with lifetime updates. Read the two full samples on this page before deciding.
How were the examples tested?
The included methodology describes one practitioner's work with Opus 4.6 and Sonnet 4.5 during March and April 2026. It is not a blinded study or a public benchmark. Results can change by task and model; use the samples to make your own comparison.
Does this include a Claude subscription?
No. Use your own Claude account. This purchase is a reference resource, with no included API credits or guaranteed outcomes.
How do I get access after paying?
Use an email you can access at checkout. If a card purchase through Dodo has not arrived, use the receipt and access form or email team@clskills.in. Existing buyers can recover their access. Please do not buy twice.
Can I share it with a team?
The standard purchase is a personal license. Email team@clskills.in for team licensing. Please read the refund policy before purchasing.

Better inputs. Thoughtful checks. Your work, a little clearer.

Try something free