160+ Claude Prompt Shortcuts: The Working List for 2026

Most of what people call "Claude prompt shortcuts" are short trigger phrases that put the model into a specific mode. /ELI5 isn't magic. It's a faster way to say "explain this to me like I'm five years old." But once you have thirty or forty of these in muscle memory, every conversation gets shorter, sharper, and less repetitive. Less time spent writing prompts. More time spent reading the answer.

Ruben Hassid put together a clean 100-shortcut infographic that's been doing the rounds on LinkedIn this month. It's a good starter set, especially for everyday consumer use cases — emails, recipes, learning, journaling. The categories cover most of what a person reaches for in a typical week.

What it doesn't cover is the work most readers of this site actually do for a living. Code. SEO. Strategy. Sales copy. Schema markup. The shortcuts most builders reach for ten times a day aren't on any of the lists currently circulating. So this is the expanded set: Ruben's original 100, plus the 60 I've built up over the past year of running Claude as a daily teammate.

If you're new to this, here's the one idea worth taking away before the list. Every shortcut is just a pattern you could write longhand. /META TITLE FOR [topic] is shorthand for "write a meta title for this topic, under 60 characters, optimised for search and click-through." Once you know the pattern, you can invent your own. The shortcuts are scaffolding. You'll grow out of needing the labels.

Quick Reference: All 160+ Shortcuts Grouped by Category

Explain & Understand (15)

1. /ELI5 [topic]: explain like you're five, no jargon.
2. /ELI15 [topic]: explain at a teenager's level.
3. /TLDR [paste]: shortest possible summary of a long piece.
4. /SUMMARIZE [paste]: standard summary, more detail than TLDR.
5. /KEY POINTS [paste]: the most important takeaways as a clean list.
6. /MAIN IDEAS [paste]: the big themes rather than the specific facts.
7. /DEFINE [word]: quick definition with context, not a dictionary line.
8. /EXAMPLE OF [concept]: a real-world example to make an abstract idea click.
9. /ANALOGY FOR [concept]: a familiar comparison for something unfamiliar.
10. /SIMPLIFY [paste]: rewrite complicated text in plain language.
11. /EXPAND ON [topic]: add depth when the first answer felt thin.
12. /CONTEXT FOR [topic]: the backstory so you understand why it matters.
13. /HISTORY OF [topic]: a quick origin story.
14. /TIMELINE OF [topic]: chronological order.
15. /GLOSSARY FOR [topic]: mini-dictionary of all the key terms.

Think & Decide (13)

1. /PROS AND CONS [topic]: balanced list of upsides and downsides.
2. /COMPARE [A] vs [B]: side-by-side breakdown of two options.
3. /SWOT [topic]: strengths, weaknesses, opportunities, threats.
4. /RISKS OF [plan]: what could go wrong.
5. /COUNTERARGUMENT [position]: the opposing view, even if you agree with the original.
6. /DEVIL'S ADVOCATE [position]: more aggressive hole-poking.
7. /STEP-BY-STEP [task]: ordered numbered steps.
8. /CHECKLIST FOR [task]: a tickable list, useful for repeated work.
9. /DECISION MATRIX [options]: a scoring grid weighing options against criteria.
10. /QUESTIONS TO ASK BEFORE [decision]: surfaces blind spots before you commit.
11. /RED FLAGS IN [situation]: warning signs for jobs, contracts, deals.
12. /COMMON MISTAKES WITH [task]: avoid errors others have already made.
13. /FACT CHECK [claim]: what's supported, disputed, or unknown.

Writing (11)

1. /REWRITE [paste]: fresh version of the same content.
2. /SHORTER [paste]: cut length without losing the point.
3. /LONGER [paste]: add detail when a draft feels thin.
4. /CLEARER [paste]: smooth confusing or clunky writing.
5. /FIX GRAMMAR [paste]: corrections without changing your voice.
6. /PROOFREAD [paste]: catch typos, grammar issues, and awkward phrasing.
7. /MORE FORMAL [paste]: bump up the professionalism.
8. /MORE CASUAL [paste]: loosen up stiff writing.
9. /MORE POLITE [paste]: soften a message that lands too blunt.
10. /MORE CONFIDENT [paste]: strip out hedging words like "maybe," "just," "kind of."
11. /CHANGE TONE TO [tone] : [paste]: pick a tone (witty, urgent, warm) and rewrite.

Email & Messages (9)

1. /EMAIL FROM [bullet notes]: turn rough notes into a polished email.
2. /REPLY TO [paste email]: draft a response to a message.
3. /SUBJECT LINE FOR [email]: strong subject lines that actually get opened.
4. /FOLLOW-UP EMAIL ABOUT [topic]: chasing replies and second touches.
5. /POLITE DECLINE [situation]: say no without burning bridges.
6. /APOLOGY FOR [situation]: a genuine, non-cringey apology.
7. /THANK YOU NOTE FOR [reason]: a warm thank-you that doesn't sound robotic.
8. /CONDOLENCE MESSAGE FOR [situation]: gentle words when someone is grieving.
9. /CONGRATULATIONS MESSAGE FOR [reason]: heartfelt congrats for life events.

Work (9)

1. /MEETING AGENDA FOR [topic]: structured agenda with time blocks.
2. /ACTION ITEMS FROM [paste notes]: clear next steps out of messy meeting notes.
3. /EXEC SUMMARY OF [paste]: a one-paragraph version for busy decision-makers.
4. /COVER LETTER FOR [job description]: tailored, not generic.
5. /RESUME BULLET FOR [achievement]: a sharp, results-oriented line.
6. /LINKEDIN BIO FROM [details]: a profile summary from your background.
7. /INTERVIEW QUESTIONS FOR [role]: likely questions to practise with.
8. /ANSWER THIS INTERVIEW QUESTION: [question]: a strong answer using STAR method.
9. /PERFORMANCE REVIEW PHRASES FOR [trait]: wording for self-reviews and feedback.

Role-Play & Perspective (3)

1. /ACT AS [role] : [question]: Claude responds as a doctor, lawyer, coach, teacher.
2. /MULTIPLE PERSPECTIVES ON [topic]: how different groups would view the same issue.
3. /WHAT WOULD [type of expert] SAY ABOUT [topic]: a specialist's lens on something general.

Learning (8)

1. /QUIZ ME ON [topic]: Claude becomes a quiz master.
2. /FLASHCARDS FOR [topic]: term-and-definition pairs for Anki or Quizlet.
3. /STUDY PLAN FOR [topic, timeframe]: a day-by-day or week-by-week roadmap.
4. /CHEAT SHEET FOR [topic]: dense one-pager of the key facts.
5. /BEGINNER GUIDE TO [topic]: friendly intro for someone starting from zero.
6. /FAQ ABOUT [topic]: the most common questions and their answers.
7. /PRACTICE QUESTIONS ON [topic]: open-ended questions to test deeper understanding.
8. /TIPS FOR [skill]: quick wins and shortcuts for getting better.

Creative (11)

1. /STORY ABOUT [prompt]: a short fictional story.
2. /POEM ABOUT [topic]: verse on any topic, any style.
3. /HAIKU ABOUT [topic]: a three-line, 5-7-5 syllable poem.
4. /JOKE ABOUT [topic]: a one-liner or short joke.
5. /CAPTION FOR [photo description]: a witty or thoughtful caption.
6. /TWEET ABOUT [topic]: a short post under 280 characters.
7. /LINKEDIN POST ABOUT [topic]: professional post with hooks and structure.
8. /INSTAGRAM CAPTION FOR [description]: more casual, line breaks, emojis.
9. /HEADLINE FOR [article topic]: punchy titles that get clicks.
10. /NAME IDEAS FOR [thing]: brainstormed names for businesses, products, characters.
11. /SLOGAN FOR [brand]: tagline options for a business or campaign.

Home & Life (9)

1. /RECIPE FOR [dish]: full recipe with ingredients and steps.
2. /SUBSTITUTE FOR [ingredient]: swaps when you're missing something.
3. /SHOPPING LIST FOR [recipe or week]: an organised grocery list.
4. /MEAL PLAN FOR [goal, days]: a multi-day plan tailored to your goals.
5. /WORKOUT FOR [goal]: routine for strength, mobility, weight loss.
6. /PACKING LIST FOR [trip type, days]: essentials for travel.
7. /TRAVEL ITINERARY FOR [place, days]: a day-by-day trip plan.
8. /GIFT IDEAS FOR [person, budget]: thoughtful suggestions based on interests.
9. /BUDGET PLAN FOR [income, goals]: a starting framework for managing money.

Mind & Growth (9)

1. /JOURNAL PROMPT FOR [mood/theme]: a question to spark reflection.
2. /GRATITUDE PROMPTS: questions to notice what's good in your life.
3. /REFRAME THIS THOUGHT: [paste]: a healthier way to see a negative thought.
4. /MORNING ROUTINE FOR [goal]: a routine designed around what you want.
5. /HABIT PLAN FOR [goal]: how to build a habit using small steps.
6. /SMART GOAL FROM [vague aim]: turn "get fit" into something specific and measurable.
7. /CONVERSATION STARTERS FOR [setting]: openers for dates, networking, parties.
8. /AFFIRMATIONS FOR [theme]: positive statements for confidence, calm, self-worth.
9. /BOOK RECOMMENDATIONS LIKE [book or topic]: "if you loved X, you'll like..." suggestions.

That's the standard 100, give or take. The next seven categories are the ones I've built up myself and use more than any single category above.

Coding & Development (10)

1. /DEBUG [error or paste]: analyse an error and propose fixes.
2. /EXPLAIN CODE [paste]: walk through what a block of code does, line by line.
3. /REFACTOR [paste]: clean up code without changing what it does.
4. /CONVERT [paste] FROM [language] TO [language]: port between languages.
5. /OPTIMISE [paste] FOR [speed / memory / readability]: improve along one axis.
6. /ADD TESTS FOR [paste]: generate unit tests with realistic edge cases.
7. /CODE REVIEW [paste]: find bugs, smells, and improvement opportunities.
8. /REGEX FOR [pattern description]: build and explain a regular expression.
9. /SQL FOR [task description]: write a query and explain the joins.
10. /CRON FOR [schedule description]: generate the cron expression and read it back in English.

SEO & Content Marketing (10)

1. /META TITLE FOR [topic]: under 60 characters, keyword-led.
2. /META DESCRIPTION FOR [topic]: under 155 characters, click-worthy.
3. /KEYWORDS FOR [topic]: primary, secondary, and long-tail clusters.
4. /SEARCH INTENT FOR [keyword]: informational, commercial, transactional, or navigational.
5. /CONTENT OUTLINE FOR [topic]: H2 and H3 structure for an article.
6. /SCHEMA FOR [page type]: JSON-LD scaffolding for Article, FAQ, Product, etc.
7. /FAQ SCHEMA FROM [paste]: convert a Q&A section into valid FAQPage schema.
8. /INTERNAL LINKS FOR [topic]: suggest hub and spoke structure across a site.
9. /AEO REWRITE [paste]: restructure prose so AI engines can cite it.
10. /ALT TEXT FOR [image description]: accessible and SEO-aware alt text.

Analysis & Strategy (8)

1. /STEELMAN [position]: the strongest possible version of an opposing argument.
2. /THIRD ALTERNATIVE [A vs B]: a third option beyond the binary you've framed.
3. /SECOND-ORDER EFFECTS OF [decision]: knock-on consequences three steps out.
4. /PREMORTEM FOR [plan]: imagine it has failed, then explain what killed it.
5. /SOURCES FOR [claim]: what types of evidence would back this up.
6. /CONFIDENCE LEVEL ON [claim]: separate what's known from what's speculation.
7. /WHAT'S MISSING FROM [paste]: gap analysis of a document or plan.
8. /UNBLOCK ME ON [task]: surface what's actually stopping forward progress.

Productivity & Operating (8)

1. /TURN INTO TICKET [paste]: convert a rough idea into a bug report or user story.
2. /OKRS FOR [goal]: objectives with measurable key results.
3. /BRAINSTORM 20 [thing]: quantity-first idea generation before filtering.
4. /CONSTRAINTS FOR [task]: list the real limits before solving.
5. /PRIORITISE [list]: rank items by impact, effort, urgency.
6. /BATCH [tasks]: group similar work so you stop context-switching.
7. /DELEGATE [task]: what's worth handing off and what to keep.
8. /WEEKLY REVIEW PROMPTS: questions to run on a Friday afternoon.

Sales & Marketing (8)

1. /COLD EMAIL FOR [recipient, offer]: opener that doesn't sound like a template.
2. /VALUE PROP FOR [product, audience]: one sentence on why this matters to them.
3. /ELEVATOR PITCH FOR [thing]: thirty seconds, no jargon.
4. /LANDING PAGE COPY FOR [product, audience]: hero, features, social proof, CTA.
5. /AD COPY FOR [platform, product]: headlines and body that match the platform.
6. /SALES OBJECTIONS FOR [product]: the five objections you'll hear and how to answer them.
7. /ICP FOR [product]: ideal customer profile with firmographics and pain points.
8. /POSITIONING FOR [product]: where you sit against the alternatives.

Data & Formatting (6)

1. /JSON FROM [paste]: extract structured data from messy text.
2. /CSV FROM [paste]: convert a list or document into a comma-separated table.
3. /TABLE FROM [paste]: render the contents as a markdown table.
4. /MARKDOWN [paste]: clean up the formatting of pasted text.
5. /TRANSLATE [paste] TO [language]: a clean translation, no extra commentary.
6. /BACK-TRANSLATE [paste]: translate to a target language then back to check fidelity.

Power-User & Meta (13)

1. /THINK MORE: tells Claude to reason more deeply before answering.
2. /SHORT: forces brevity on the next answer.
3. /BULLETS: format the answer as a list.
4. /NO BULLETS: force prose, no list formatting.
5. /JUST CODE: skip the explanation, give me the code.
6. /CRITIQUE THIS [paste]: find weaknesses in the work above.
7. /ALTERNATE TAKE: give me a different perspective on the same input.
8. /ASSUME [context]: set context before the real question.
9. /CONSTRAINTS: [list]: define hard limits before asking.
10. /WHAT WOULD YOU ADD?: ask Claude what's missing from your own work.
11. /CONTINUE: pick up generating from exactly where you stopped.
12. /TRY AGAIN: same input, different approach.
13. /SHOW YOUR WORK: make the reasoning visible step by step.

How the Shortcut Trick Actually Works

These look like magic incantations. They aren't. Each one is a compressed prompt that you could write longhand if you had the patience.

/ELI5 quantum entanglement is the same as typing "explain quantum entanglement to me as if I were five years old. No jargon. Use simple language. Use an analogy if it helps." The shortcut just saves you fifty words and signals what you want in a way the model has seen thousands of times.

The implication: you can invent your own. Pick a thing you ask Claude often. Write down the long version once. Compress it to a slash command. Use it for a week. If it sticks, it's a real shortcut for you. If you stop reaching for it, kill it.

A few examples to illustrate the pattern, drawn from different kinds of work:

• A directory operator builds /LISTING REWRITE [paste] to rewrite a directory entry against a defined house style guide with E-E-A-T checks.
• A founder building software creates /BUG TICKET [paste] that turns a feature idea or bug description into a properly formatted GitHub issue with acceptance criteria.
• A content editor sets up /PILLAR OUTLINE [topic] that builds the standard pillar-page structure with H2s, FAQ block, and internal link suggestions.

None of those will land for you exactly. The point isn't to copy them. The point is to notice the moment you've typed the same long prompt three times in a week, then turn it into a shortcut you can fire in seven characters.

Combinations That Change the Answer Entirely

A single shortcut is useful. Two stacked together can change what the model produces in ways neither one would alone.

/TLDR + /BULLETS + /SHORT: when you've been sent a 4,000-word email and you need the gist by the time the kettle boils.

/STEELMAN + /COUNTERARGUMENT: ask for the strongest version of a view, then immediately ask for the strongest case against it. You end up with a much more balanced read on a contested topic than either prompt alone.

/PREMORTEM + /SECOND-ORDER EFFECTS: kill your own plan first, then trace the knock-on damage. Surprisingly useful before any decision worth fifty thousand dollars or more.

/CODE REVIEW + /CRITIQUE THIS + /WHAT'S MISSING: three passes of scrutiny on the same block of code. Each finds different problems.

/ACT AS [tough customer] + /SALES OBJECTIONS: practise a sales conversation with Claude playing the prospect's role. Faster than role-playing with a colleague who already agrees with you.

/META TITLE + /META DESCRIPTION + /SCHEMA: the full SEO metadata pass for a single post, in three quick prompts.

The general principle: shortcuts compose. The model doesn't get confused by stacking them. It treats the combination as a stronger version of the request.

Where Shortcuts Fall Short

Worth being honest about the limits.

Shortcuts don't replace context. /RECIPE FOR pasta gives you a generic pasta dish. /RECIPE FOR pasta, no dairy, on a Tuesday night, two adults and a fussy four-year-old, twenty minutes maximum gives you something you'll actually cook. The shortcut is the prefix. The context is the meal.

Shortcuts work better with examples. If you've used /EMAIL FROM bullet notes twice and the output still doesn't sound like you, paste an example of an email you've sent in the past. The model will copy your voice from one sample better than any tone instruction.

Some shortcuts are placebos. /MAKE THIS BETTER is barely a prompt. Without a definition of better, the model has to guess. /SHORTER, /CLEARER, /MORE FORMAL, /MORE CONFIDENT each give it a direction.

Compound shortcuts can fight. /SHORT + /THOROUGH is a contradiction. The model will pick one and ignore the other, usually the one closer to the end of your message. If you're stacking, make sure the directions agree.

Frequently Asked Questions

What are Claude prompt shortcuts?

Claude prompt shortcuts are short trigger phrases (often written with a slash prefix like /ELI5) that tell the model what kind of answer you want. Each shortcut is a compressed version of a longer prompt that you could otherwise write out by hand. They save typing and give the model a clear signal about the expected format and tone.

Do these slash commands actually do anything in Claude?

The slash isn't a real command. Claude doesn't have a built-in dispatcher that recognises /TLDR differently from "give me a TLDR." The shortcut works because the model has seen this kind of compressed instruction often enough during training that it responds reliably. Treat them as conventions, not features.

Will the same shortcuts work in ChatGPT, Gemini, or other AI tools?

Mostly yes. These patterns are not Claude-specific. Any large language model trained on internet text will recognise /ELI5, /TLDR, and similar conventions. The quality of the response will vary by model, but the trigger phrase itself is portable.

Can I create my own Claude prompt shortcuts?

Yes. Pick a prompt you write often. Compress it to a short label. Use it for a week. If it saves time, keep it. If you stop reaching for it, drop it. There's no central registry. The shortcut is yours.

What's the difference between /TLDR and /SUMMARIZE?

/TLDR is the shortest possible version, usually one or two sentences capturing the main point. /SUMMARIZE is longer and keeps more of the supporting detail, closer to one paragraph or a short list of key takeaways. Reach for TLDR when you need the gist in five seconds, SUMMARIZE when you need enough detail to discuss the source.

How do I get Claude to stop using bullet points?

Append /NO BULLETS to your prompt, or write "respond in prose, no lists or bullet points." Both work. For longer-running preferences, set it in your Claude system instructions so you don't need to repeat it every conversation.

What's the best Claude shortcut for SEO?

For an individual page, the three to reach for most are /META TITLE FOR [topic], /META DESCRIPTION FOR [topic], and /SCHEMA FOR [page type]. Together they cover the basic on-page metadata in three short prompts. For broader SEO research, /KEYWORDS FOR [topic] followed by /SEARCH INTENT FOR [keyword] is the sequence to run before writing any pillar page.

Are these shortcuts safe to use for sensitive work?

The shortcut itself is just a string. The safety of the work depends on what you paste into it and what you do with the answer. Treat anything legal, medical, financial, or otherwise consequential as a draft to be reviewed by a qualified person, not a final answer.

How many Claude prompt shortcuts should I actually memorise?

Fewer than you think. Five to ten that match your daily work will save more time than a hundred you've read about once. Start with the categories you live in (writing, coding, email, planning) and ignore the rest until you need them.

Where can I find more Claude prompt shortcuts?

The original 100-shortcut infographic by Ruben Hassid is a good starter. After that, the most reliable source is your own work. Pay attention to the prompts you find yourself repeating. Those are your real shortcuts in waiting.

What to Do Next

Don't try to memorise the whole list. Pick four or five that match what you actually do this week. Use them. The rest will be here when you need them.

If you use Claude for work, the categories worth committing to memory are the ones around your job. Writers should know the writing block. Founders should know analysis and strategy. Developers should know the coding block. Sales people should know sales and marketing. Skim the rest. Bookmark this page.

And start watching for the prompts you keep typing out longhand. Those are the next shortcuts. Yours. Not on anyone's list yet. The fastest way to use Claude well is to stop using other people's shortcuts and start writing your own.

Credit again to Ruben Hassid for the original 100 across ten consumer-facing categories. The seven categories added here — coding, SEO, analysis, productivity, sales, data, and power-user combinations — are the ones most builders reach for at work.

If you've built a shortcut worth sharing, send it in. The list grows from there.