Copy-ready prompts for clearer writing, stronger campaigns, and faster creative work.
You may have seen “secret Claude codes” like /human or /artefact. The slash labels in this guide are memorable names for full prompts you can copy. They are not built-in Claude commands, and typing a label by itself is not the reliable way to get the result.
Choose a card, click Copy prompt, replace the [bracketed inputs] with your material, and paste the whole instruction into Claude. Attach source material when the prompt calls for it. In Claude Code, you can later turn repeated recipes into your own skills.
Start with the outcome, not a magic word.
Give Claude facts, examples, and limits.
Check truth, voice, fit, and usefulness.
Save the best version as a template or skill.
Find your voice · Turn a rough draft into writing that sounds like you.
/humanRewrite [text] for [audience] in a natural, specific voice. Preserve the facts and intent. Cut stock AI phrases, inflated claims, and repetitive sentence patterns. Return only the revised version plus three short notes on what changed.
/voiceprintStudy these three writing samples: [samples]. Identify my recurring vocabulary, sentence rhythm, point of view, humor, and phrases I avoid. Create a one-page voice guide and a 100-word test paragraph on [topic].
/plainspokenRewrite [text] for a smart reader new to [topic]. Replace jargon with everyday words, explain unavoidable terms once, and keep the original meaning. Flag any claim that becomes less precise.
/cutfluffCut [text] by 30% without losing the promise, proof, or call to action. Remove throat-clearing and repeated ideas. Show the shorter version and a list of material cuts.
/toneflipRewrite [text] in three tones: warm expert, bold challenger, and calm premium. Keep the facts identical. Label each version and explain when each tone fits.
/readaloudEdit [script] so it sounds natural when read aloud. Use shorter breaths, contractions where appropriate, and a clear spoken transition between points. Mark likely tongue-twisters.
/specificsFind vague adjectives and claims in [copy]. For each, propose a concrete example, observable detail, or proof point. Do not invent evidence; mark missing proof as [NEEDS INPUT].
/brandguardCompare [draft] with this brand guide: [guide]. Score fit for vocabulary, tone, audience, and promise. Quote the lines that drift, then revise them without changing factual claims.
/localizeAdapt [copy] for readers in [country or region]. Adjust spelling, idioms, currency references, and cultural examples. Keep the offer and facts intact, and flag anything that needs local verification.
/onebreathReduce [offer or idea] to one clear sentence a customer could repeat. Then write a 12-word version, a 25-word version, and a version for a skeptical buyer.
Know who it is for · Turn assumptions into useful customer questions and angles.
/personaUsing only [interviews, reviews, or notes], create a customer profile with goals, triggers, objections, language they use, and buying context. Separate direct evidence from inference.
/jobsAnalyze [customer notes] for the progress customers want, what starts their search, alternatives they use now, and what might block a switch. Cite the exact input behind each conclusion.
/painmapFor [audience] considering [offer], map current frustrations, desired outcomes, and anxieties. Mark assumptions and write five interview questions to test them.
/objectionsList the ten most plausible objections to [offer] from [audience]. Group them by trust, timing, money, effort, and fit. Suggest an honest response and the proof needed for each.
/positionGiven [product], [audience], [alternatives], and [evidence], propose five positioning angles. For each, state the promise, reason to believe, likely weakness, and best channel.
/offerstackTurn [product or service] into three offer packages for [audience]. Specify outcome, deliverables, boundaries, proof, and a clear next step. Do not invent prices or guarantees.
/promisecheckAudit this promise: [promise]. Identify ambiguity, overclaiming, missing proof, and likely misinterpretations. Rewrite it as a credible headline and supporting sentence.
/segmentSplit [audience or customer list] into three to five useful segments by need or behavior rather than demographics alone. For each, give a distinct message and question to validate it.
/beforeafterDescribe [offer] as a before-to-after transformation grounded in [evidence]. Write the customer's starting state, useful progress, and realistic outcome. Avoid miracle language.
/interviewWrite 12 neutral customer interview questions about [problem]. Ask for recent real behavior and examples. Avoid leading questions and hypothetical praise; add one follow-up per question.
Choose the next move · Explore opportunities without pretending guesses are facts.
/anglesGenerate 20 distinct angles about [topic] for [audience]. Mix myths, mistakes, how-to, behind-the-scenes, case examples, and contrarian views. Give the core insight and strongest format for each.
/gapscanReview [existing posts or content inventory] against [audience questions]. Identify repeated themes, unanswered questions, and underused formats. Rank five gaps by likely usefulness, with evidence from the inputs.
/trendcheckInvestigate whether [trend] matters to [audience]. If web access is available, cite dated primary sources; otherwise state what cannot be verified. Separate durable behavior from short-lived attention.
/competitorlensCompare [our offer] with [named alternatives] on buyer criteria: [criteria]. Use supplied or cited evidence. Highlight where we truly differ and where the difference is only wording.
/swipeauditAnalyze these [ads, pages, or posts]: [examples]. Extract reusable structural patterns, hooks, proof devices, and calls to action. Do not copy distinctive wording.
/contentpillarBuild four content pillars for [brand] serving [audience]. For each, give the customer question, business purpose, sample topics, and one measurable signal of usefulness.
/calendarMake a four-week publishing plan for [channels], [frequency], [team size], and [goal]. Reuse core ideas across formats without repeating identical copy. Include production time and dependencies.
/priorityScore these ideas: [ideas] against impact, confidence, effort, and strategic fit. State assumptions, show the scoring table, and recommend the next three tests.
/experimentDesign a low-cost test for [hypothesis]. Define audience, single variable, success metric, minimum observation period, and what result would change our decision.
/briefCreate a one-page brief for [campaign or asset] using [context]. Include audience, problem, single-minded message, proof, deliverables, constraints, examples, and approval criteria. Flag missing inputs.
Make substantial work · Draft useful assets that deserve attention.
/outlineCreate an outline for [article or guide] aimed at [reader] who wants [outcome]. Lead with the decision or problem, cover prerequisites, examples, objections, and a clear next action. Note claims needing sources.
/draftUsing this outline [outline] and source material [sources], write a [length] draft for [audience]. Use our voice [guide]. Do not invent facts, quotations, or case results; mark missing evidence.
/ledeWrite ten opening paragraphs for [piece] that start with a vivid problem, surprising evidence, direct question, or useful promise. Avoid clickbait; name the reader's stake within two sentences.
/storyTurn [raw notes] into a short narrative with situation, tension, decision, and result. Preserve chronology and uncertainty. Mark any missing details as questions rather than filling them in.
/case-studyBuild a case study from [client-approved facts]. Cover context, constraint, approach, measurable outcome, and lessons. Quote only provided language and flag anything requiring permission or verification.
/leadmagnetDesign a practical lead magnet for [audience] on [topic]. Give the specific promise, section outline, one quick win, worksheet idea, and opt-in page copy. Keep the outcome achievable.
/faqTurn [customer questions] into a concise FAQ. Answer each directly in two to four sentences, link to provided proof where possible, and flag policy or product details that need checking.
/repurposeTurn [article, webinar, or transcript] into five channel-specific assets: email, LinkedIn post, short video script, carousel outline, and FAQ. Preserve meaning and vary the opening, not just the length.
/summarySummarize [long content] for [busy audience] in five bullets: main idea, evidence, implications, action, and open question. Include section references or timestamps when available.
/editorEdit [draft] for structure, repetition, clarity, and reader value. First give a prioritized edit memo, then a revised draft. Preserve the author's voice and identify unsupported claims.
Help people find it · Plan discoverable content with honest evidence.
/intentFor [query or topic], describe the likely reader intent, stage of awareness, questions to answer, and page type. If search results are unavailable, label this as a hypothesis to validate.
/keywordclusterGroup [keyword list] by searcher intent and semantic overlap. Pick a primary page for each cluster, supporting articles, and internal-link ideas. Avoid treating volume estimates as facts unless supplied.
/serpbriefWith web search enabled, inspect current results for [query] in [market]. Cite the pages and dates. Summarize common coverage, missing useful answers, and a differentiated outline.
/titlelabWrite 15 search-friendly titles for [page] targeting [topic]. Keep each accurate and compelling; give approximate character count and avoid promises the page does not fulfill.
/metaWrite eight meta descriptions for [page summary] under about 155 characters. Make the benefit specific, include a natural next step, and avoid claiming a ranking benefit.
/snippetWrite a direct 40-60 word answer to [question] using [verified facts]. Then add a short list or table that expands it. Flag anything that needs a current source.
/internal-linksGiven [site map and page summaries], suggest internal links for [new page]. For each, name source page, target page, natural anchor text, and reader reason for the link.
/refreshAudit [existing article] for outdated claims, weak examples, broken logic, and missing reader questions. Produce a section-by-section update plan; mark all facts that require fresh verification.
/schema-briefFrom [page content], identify any structured-data type that genuinely matches the visible page. List required fields, missing information, and validation steps. Do not fabricate reviews or ratings.
/content-auditReview [content inventory with metrics]. Classify each page as keep, improve, merge, or retire using explicit criteria. Explain uncertainty and give the first five actions.
Create for the feed · Tailor ideas to how each channel is consumed.
/linkedinTurn [insight and proof] into three LinkedIn posts for [audience]: story, practical tip, and opinion. Start with a concrete line, use short paragraphs, and end with a genuine question or takeaway.
/carouselCreate an eight-slide carousel on [topic] for [audience]. Give one idea per slide, a strong first-slide promise, concise body copy, and a final action. Include an alt-text summary.
/threadTurn [source] into a seven-post thread that progresses from problem to insight to action. Make each post useful on its own and preserve factual nuance from the source.
/reelWrite a 45-second vertical video script about [topic]. Include spoken hook, visual beats, on-screen text, a useful example, and a non-pushy close. Aim for natural speech.
/hookbankGive 25 opening hooks for [topic] aimed at [audience]. Group by curiosity, problem, proof, and point of view. Avoid fake urgency and misleading claims.
/captionWrite six captions for [asset] on [platform] in our voice [guide]. Vary length and angle. Include a specific call to action only when it fits the post's goal.
/commentsDraft thoughtful replies to these comments [comments]. Acknowledge the point, answer concretely, and avoid defensiveness. Flag any reply that needs private follow-up.
/communityCreate ten discussion prompts for a community of [audience] around [topic]. Favor questions that invite experiences and decisions over yes/no engagement bait.
/seriesDesign a six-part series on [theme] for [platform]. Give a recognizable format, episode titles, distinct takeaways, and a low-effort production template.
/transcriptFrom [transcript], extract ten quotable insights, five short clips with timestamps, and three deeper article ideas. Quote the speaker exactly and flag unclear audio.
Earn the next click · Write messages that respect the reader.
/subjectWrite 20 subject lines for [email] to [audience]. Group by benefit, curiosity, and directness. Keep them accurate, avoid spammy urgency, and suggest two sensible A/B candidates.
/welcomeWrite a welcome email for people who signed up for [promise]. Deliver the promised resource, set expectations for future emails, and invite one simple reply. Use [voice guide].
/nurturePlan five emails for [audience] moving from [current situation] toward [offer]. Give each email one job, one useful idea, proof needed, and a clear but low-pressure next step.
/launchPlan a launch sequence for [offer], [dates], and [audience]. Include announcement, education, objections, proof, reminder, and close. Use only real deadlines and verified claims.
/reengageDraft a respectful re-engagement email for subscribers inactive for [period]. Remind them why they joined, offer a useful resource, and give a clear preference or unsubscribe option.
/segmentedAdapt [base email] for these segments [segments]. Keep the offer consistent while changing the opening, example, objection, and call to action for each.
/ctaGenerate 15 calls to action for [page or email] with goal [goal]. Match the commitment level of the reader. Pair each button label with one line of supporting microcopy.
/landingDraft a landing page for [offer] using [evidence]. Include hero, problem, benefits, how it works, proof, objections, FAQ, and CTA. Mark any missing testimonials or results.
/formReview [form and page context] for unnecessary fields, unclear labels, trust gaps, and weak confirmation copy. Recommend changes with a reason and draft improved microcopy.
/sequence-auditMap [emails and landing pages] from opt-in to conversion. Identify message gaps, repeated claims, confusing transitions, and unearned asks. Recommend the top five fixes.
Test clear messages · Build campaigns around evidence and controlled experiments.
/ad-angleCreate 12 ad angles for [offer] and [audience]. For each, state the customer tension, core message, proof needed, and best creative format. Avoid unverified performance claims.
/ad-copyWrite five ad copy variants for [platform] using [approved claims and offer]. Vary the opening and benefit. Respect [character limits or policy notes] and label anything needing review.
/creative-briefWrite a creative brief for [campaign]. Include audience, one message, visual concept, script or frame sequence, proof asset, CTA, placement, and what the designer must avoid.
/testimonialTurn [permissioned customer quote] into three ad or page treatments. Preserve wording and context; do not imply a typical result or add numbers not in the quote.
/abtestDesign an A/B test for [page or ad] changing only [variable]. Define hypothesis, primary metric, guardrail metric, sample considerations, and decision rule without claiming statistical certainty prematurely.
/offercompareCreate a comparison table for [offer A] and [offer B] using [facts]. Show who each is for, included deliverables, trade-offs, and questions buyers should ask.
/frictionReview [page copy, screenshots, and analytics]. Identify moments where a visitor may hesitate, the evidence for each, and the smallest change to test next. Separate observed problems from hypotheses.
/urgencyAudit [campaign] for urgency and scarcity language. Keep only claims supported by actual dates or inventory. Rewrite the rest as value-based reasons to act.
/retargetCreate messages for visitors who viewed [page] but did not act. Address likely unanswered questions, add useful proof, and cap the ask at a sensible level. Do not assume why an individual left.
/postclickCompare [ad] with [landing page]. Check promise, audience, wording, visual continuity, proof, and CTA. Write a prioritized alignment checklist and revised hero section.
Make ideas tangible · Use Claude to plan and make reusable visual assets.
/artefactCreate a self-contained artifact for [audience] that helps them [task]. Include clear inputs, useful output, accessible labels, and a short example. Ask for any missing requirements before building. (In Claude, the product feature is called Artifacts.)
/wireframeCreate a text wireframe for [page] serving [audience]. Lay out sections in reading order, explain each section's job, and include mobile considerations and CTA placement.
/infographicTurn [verified data or process] into an infographic brief. Suggest hierarchy, chart or diagram type, labels, source footnotes, and alt text. Do not invent data.
/diagramCreate a simple diagram of [process or relationship]. Use five or fewer primary nodes, plain labels, and a caption that explains the key takeaway. If the tool supports it, make an editable artifact.
/dashboardDesign a dashboard for [role] tracking [goal]. Choose only decision-useful metrics, define each one, propose layout and filters, and flag data gaps before building.
/worksheetCreate a fillable worksheet for [task] with a short instruction, six to ten prompts, an example row, and a final decision box. Make it usable without a facilitator.
/quizDesign a short quiz for [audience] that helps them assess [problem]. Give questions, scoring logic, result bands, and tailored next steps. Avoid pretending it is a validated assessment.
/mockupWrite a precise visual brief for [asset]: layout, focal point, palette, typography direction, imagery, text hierarchy, dimensions, and accessibility needs. Include what should remain editable.
/storyboardTurn [video idea] into a six-frame storyboard. For each frame, specify visual, narration, on-screen copy, duration, and transition. Keep the full runtime under [length].
/alttextWrite concise alt text for [image] based only on what is visible and its role on [page]. Skip decorative detail, include meaningful text in the image, and do not infer identity or intent.
Check the evidence, then ship work you can trust.
/sourcecheckCheck this claim: [claim]. If browsing is available, find recent primary sources and link them. State what each source actually supports, any date limits, and a safer wording if evidence is weak.
/evidenceFrom [documents and links], make a table of claims, supporting passages, source dates, strength of support, and gaps. Do not treat repeated secondary claims as independent evidence.
/reviewmineAnalyze [reviews] for recurring themes, exact customer language, surprising use cases, and unresolved complaints. Count themes only within the supplied sample and note selection bias.
/factgapRead [draft] and list every factual, numerical, comparative, or time-sensitive claim. Mark each as supported, needs source, or opinion. Propose cautious wording where proof is missing.
/assumptionsFor [plan or argument], list the assumptions that must be true. Rank them by impact and uncertainty. Suggest the cheapest credible way to test the top three.
/clarifyBefore working on [task], ask up to five high-value questions whose answers would materially change the result. If the task can proceed, state sensible assumptions and begin.
/templateTurn [finished example] into a reusable template. Replace specific details with clear placeholders, add instructions for each field, and include one filled example.
/checklistCreate a concise pre-publish checklist for [asset or campaign]. Cover factual accuracy, brand fit, accessibility, links, permissions, measurement, and final owner sign-off.
/redteamAct as a skeptical but fair reviewer of [draft]. Find the five most consequential weaknesses in clarity, evidence, audience fit, and execution. Suggest concrete fixes.
/nextbestGiven [goal], [current state], [constraints], and [options], recommend the next best action. Explain the reason, what to measure, and when to reconsider.
Claude Code has actual slash commands. Its command menu appears when you type /, and availability can vary by plan, platform, and version. Useful examples include /help, /compact, /model, /plan, and /artifacts. Anthropic spells the last one with an i and a final s; /artefact above is a mnemonic prompt label, not that command.
Claude's regular chat supports Artifacts as a product feature: ask in ordinary language for a reusable document, page, tool, or visual. Custom skills can also be created for repeatable work. The 100 recipes here are original prompts based on documented prompting practices, not a claimed list of hidden native commands.
Researched and prepared 6 October 2026. Check product documentation for later changes.