15 Best Claude Code Prompts That Earn Me 30 Hours a Week

Most "best Claude Code prompts" lists give you 50 developer templates organized by task. These 15 are organized by what you're actually doing: writing, research, coding, systems… with before/after time comparisons for each one. 30+ hours earned back per week, built from 55 production slash commands running daily.

How many "best AI prompts" lists have you bookmarked? At least one. Probably three.

I have way too many. Browser tabs, local repos, Notion pages… everywhere. I created hundreds and shared dozens to paid members, clients, coworkers, friends, family.

Some of them came back:

Too many prompts. It's overwhelming. I'm losing track of what to use. They're all good but I don't know which one to reach for.

Fair. I was overwhelmed too. So I went deeper, learned the core principles underneath, shared the methodology. I thought that would fix it.

Different questions started coming back:

What prompt did you actually use for that? Why am I not getting the same output? I'm tired of having conversations with AI that bring up more problems than I have the bandwidth to resolve.

Not which prompt should I use. But this whole process is exhausting.

That made me I realize, the best prompt isn't the cleverest one. It's the one that earns you time back, so quietly you stop noticing it's running.

That requires evaluation between tools and mapping them against your workflow. So I stopped sharing more prompts and started tracking the ones I actually reach for every day. 15 of them. Across writing, research, coding, and systems. I'm surprised at how much time each one earns back. And especially when Claude Code already has your context: your articles, your codebase, your files; the process can't be smoother.

Full-time job. Two toddlers. Maybe 4 hours a day for everything else, and I'm building products, running a newsletter, taking on clients. That math only works if something is doing the heavy lifting.

Here's every prompt and what it earns me per week:

These prompts are optimized for Claude Code, but with enough context, any AI can use them. Use these as anchors. Modify them. Make them yours. The best Claude Code prompt is the one you build from an example and never have to look up again.

What's Inside:

• Claude Code Witing Prompts (4): voice extraction, article pipelines, humanizing, and repurposing
• Claude Code Research Prompts (4): idea validation, deep research, competitive strategy, and fact verification
• Claude Code Coding Prompts (4): building features, debugging, refactoring, and clean commits
• Claude Code Systems and Orchestration Prompts (3): structural auditing, search analysis, and workflow automation
• How to Turn Claude Code Prompts Into Slash Commands — copy-paste to slash commands to MCP-connected systems

🎁 Towards the end, you'll get all 15 prompts, the slash command table, the prompt progression framework, and access to the full 241-prompt kits across writing, research, and coding.

Hi, I'm Jenny 👋 I build AI systems and tools, then share how I did it. I run the Practical AI Builder program — for people who already use AI and want to build real things with it. Check it out if that sounds like you.

If you're new to Build to Launch, welcome! Here's what you might enjoy:

• Everything in Claude
• The Universal AI Prompting Framework
• Claude Code Beginner's Guide
• Make the Most of Claude Code: 15 Projects

Claude Code Writing Prompts

Most people underestimate this workflow. Four prompts covering the full content creation cycle: voice extraction, AI drift detection, article pipelines, and cross-platform repurposing.

---

Prompt 1: Voice Extraction — Make AI Learn How You Write

⏱ ~1 hr/week — runs once, saves re-describing your voice every session

The prompt:

Read the articles in [Your Vault], pick the 5 most recent or most engaged. They're all by the same author (me). Analyze them and produce a Voice Card as a reusable style profile to add to my CLAUDE.md under a "## Writing Voice" section. Cover these 6 layers, from most visible to invisible. The questions are examples of what to look for, not a checklist, follow whatever patterns actually stand out.

1. STRUCTURE: How I organize a piece. Front-load value or build to it? How I open and close? Headers, lists, blockquotes, what tools do I reach for?
2. SENTENCE PATTERNS: Rhythm and construction. Average length, variation, fragments. Where the punch lands. How I handle complex ideas, break them up or let them flow?
3. VOCABULARY FINGERPRINT: Signature words and phrases I lean on. Words conspicuously absent. Register choices ("use" vs "utilize," "but" vs "however") that reveal formality and personality.
4. TONE: Directness level, warmth-to-authority ratio, how I handle disagreement, where humor shows up, how I address the reader.
5. PHILOSOPHY & EMOTIONAL ANCHORS: Beliefs that recur across pieces. What values drive my topic selection. What emotion I consistently try to create in the reader. This is what makes two writers with identical mechanics feel completely different.
6. WHAT I AVOID: The negative space, patterns, words, structures, and angles conspicuously absent from my writing. This defines a voice as much as what's present. Format the Voice Card as markdown I can drop directly into CLAUDE.md. Then list 3 sentences from the samples that are most "me", the lines where my voice comes through strongest. Explain why.

Why it works:

• Captures why you write (philosophy, emotional anchors, negative space), not just mechanics. Two writers can have identical sentence patterns and feel completely different.
• Runs once, works forever. Analyzes 5 articles in under 2 minutes, saves to CLAUDE.md. Every future session starts with your voice loaded.

When to use it:

• Once, at workspace setup. Update every 6 months. I caught AI-induced drift in my own writing workflow this way: longer sentences and smoothed-out edges I genuinely liked.

What makes it different:

• Portable artifact, not session-bound. Pasting samples into ChatGPT trains one conversation. The Voice Card persists across every session and project.

---

Prompt 2: Voice-Checked Humanization Pass

⏱ ~1 hr/week — 90 seconds per article vs. 30-45 min of manual AI-pattern hunting

The prompt:

Read the Voice Card in my CLAUDE.md (under "## Writing Voice"). Then read the draft at [Your Vault]/[article].md.

Run these 7 checks against both the Voice Card and the draft:

1. VOICE DRIFT CHECK: Compare the draft's sentence patterns, rhythm, and tone against the Voice Card. Flag any sections where the writing drifted from my documented style. Be specific — quote the drifted sentence and explain what my Voice Card says I'd actually write.
2. EVALUATE INTENSIFIERS: For each "actually," "truly," "genuinely," "just," "really" — apply the 3-second test. Read with the word, then without. Did you lose punch or contrast? If yes, keep. If no, cut. Example: "What actually works" keeps it (implies most advice doesn't). "I actually think" loses it (filler).
3. EM-DASH DISCIPLINE: Limit to 2-3 per article max. For each em-dash, try a period first (works 80% of the time). "You're not building an app — you're encoding how you think" becomes "You're not building an app. You're encoding how you think."
4. KILL FORMULAIC CONTRASTS: "It's not X, it's Y" gets rewritten every time. That pattern is the fingerprint of AI writing.
5. REMOVE AI VOCABULARY + PATTERNS: delve, embark, craft, realm, game-changer, unlock, tapestry, pivotal, harness, landscape, ever-evolving. Also cut: "Here's the thing..." "It's worth noting that" "In conclusion" "Moreover" "Furthermore"
6. ADD SPECIFICITY: "hundreds" → "300+", "takes some time" → "20 hours", "really cheap" → "$0.03 per query". Name every vague "something," "in a different way," or "things started to change."
7. PUBLISHED COMPARISON: Read my 3 most recent articles in [Your Vault]/. Find one sentence in the draft that sounds least like something I'd publish, and one that sounds most like me. Explain why.

For each change, note what was changed and why. Flag any words you evaluated and chose to KEEP (with reasoning). Apply all fixes directly to the draft file.

Why it works:

• Checks against two sources of truth: your Voice Card and your published articles. Not a vague "make it more human."
• Catches drift you can't see yourself. The slow creep of longer sentences and smoothed-out edges from weeks of writing with AI.

When to use it:

• Last step before publishing. ~90 seconds per article, catches 8-12 changes I wouldn't spot manually.

What makes it different:

• Targets the two most reliable AI fingerprints: em-dashes (lazy rhythm) and "It's not X, it's Y" contrasts (AI produces 10x more than humans). Edits the file in place. No copy-pasting.

This is my last-mile editing step. I run it as part of a 3-4 prompt sequence before publishing. The full pre-publish pass includes a grammar-and-tense fixer, a line editor for clarity, and a formatting check.

---

Prompt 3: Draft to Published — The Full Article Pipeline

⏱ >5 hrs/week — 20-min re-runs vs. 6-8 hours juggling phases manually

The prompt:

Run the complete article pipeline for [article folder]:

Phase 1: Check status — what exists, what's missing Phase 2: Create draft using the pillar article template Phase 3: Generate hero image prompt + alt text Phase 4: Run full audit chain (structure → sections → polish) Phase 5: Add internal backlinks at philosophy moments Phase 6: Generate title, subtitle, URL slug, meta description Phase 7: Pre-publish checklist

Skip any phase that's already complete. Pause after Phase 6 for my review before the final checklist.

Why it works:

• Sequenced workflow with skip logic. Picks up where you left off. Run it mid-process and it skips completed phases.
• Built-in review gate before the final checklist.

When to use it:

• Every content cycle. First run: 2-3 hours. Re-runs: ~20 minutes. I run this for every Wednesday article.

What makes it different:

• 7 phases in one context window. "Skip what's done" makes it a system, not a checklist.

I encode this as /audit-full-article. One command that routes to 7 sub-workflows. The full orchestrator handles 10+ phases including post-publish distribution.

---

Prompt 4: Turn One Article Into a Dozen Social Posts

⏱ ~30 min/week — 12 notes in 30 seconds vs. writing each one from scratch

The prompt:

Generate 10-12 social media notes from this article.

Distribution (adjust these percentages to match your content style):

• [X]% thought-provoking (pattern reveals, mindset shifts, contrarian takes)
• [Y]% educational (system breakdowns, honest metrics, tool comparisons)
• [Z]% personal (building journey moments, vulnerable shares)

THE FIRST LINE OF EVERY NOTE MUST STOP THE SCROLL. Open with a hook pattern like:

• "Stop [bad habit]."
• "Most people will never [desirable outcome]."
• "I [stopped/started] [specific thing]." (I have a full library of 40+ hook templates with engagement data — link at the end of this article.)

For each note:

• Assert, don't hedge. "This works" not "this might help."
• Short sentences (15 words max)
• Specific numbers, not vague ("300+" not "hundreds")
• One quotable line per note (screenshot-worthy)
• Under 80 words total

Use the debate method for thought-provoking notes:

1. Identify a tension in the article (e.g., "building fast vs. building right")
2. Argue both sides (2-3 points each)
3. Synthesize into a nuanced insight
4. Write the note from that synthesis

Why it works:

• Not Claude Code-specific, and that's the point. Distribution ratio prevents all-educational (textbook) or all-personal (no value) output.
• The debate method (argue both sides of a tension, then synthesize) produces original notes, not summaries. (Full system in The Viral Substack Notes Creation System.)

When to use it:

• After publishing. 12 notes in about 30 seconds. That's 2-3 weeks of content from one article. Works in Claude Code, ChatGPT, or both.

What makes it different:

• The debate methodology. "Find tensions, argue both sides, synthesize." I haven't found this in other repurposing prompts.

If any of these prompts saved you from typing the same instructions again, share this with someone who's still copy-pasting from browser tabs.

If you're a paid subscriber, I've bundled these 4 plus 78 more into one Writing Prompts Kit — grab it and drop the whole set into your workspace.

Those are the 4 writing prompts I reach for most. Next: research prompts for validating ideas and verifying claims before you launch.

The writing prompt that surprised me most was Prompt 4 — I wrote about what happened the first time I went viral with a prompt in Lessons From a Viral Prompt.