15 prompts
Read the product and its onboarding flow. Write a 7-email sequence for new sign-ups over 14 days. Each email has one goal tied to a product action that predicts retention, a subject line and 2 alternatives, preview text, a short body, and one CTA. Explain the trigger and timing of each. Save to content/email/onboarding.md.
RepoBuild responsive email templates for our transactional and marketing emails in this repo (React Email, MJML or whatever fits the stack): welcome, password reset, receipt, product update, and newsletter. Use our brand, test in dark mode, include plain-text versions, and add a preview script.
RepoWrite a 3-email re-engagement campaign for users inactive for 30+ days: what is new since they left, a quick win they can get in 2 minutes, and a final "should we stop emailing?" email. Personalise by the last feature they used. Save to content/email/re-engage.md.
Plan 12 issues of our newsletter: a theme for each, a main story or lesson, 3 link ideas, and a reader question. Fully write the first 3 issues. Save to content/newsletter/plan.md.
WebFind every email this codebase sends. For each check the subject, sender name, copy, links, unsubscribe and footer, plain-text version, and whether it renders on mobile. Rewrite the weak ones and fix the code. Output a table of every email and its trigger.
RepoWrite the announcement email for our latest feature or launch: 3 subject lines, the story of why we built it, what it does with a GIF idea, how to try it in one click, and a P.S. Also write a shorter version for the in-app banner and a social post. Save to content/email/launch.md.
RepoCheck our email setup from DNS and code: SPF, DKIM, DMARC records for our domain, sender addresses, list-unsubscribe headers, link tracking domains, and content that triggers spam filters. Report what is missing and how to fix it, with the exact DNS records to add.
Web RepoWrite a 4-email sequence for the last week of a free trial: a progress recap using their own usage, a feature they have not tried, social proof from a similar customer, and a final reminder with the plan that fits their usage. Save to content/email/trial-end.md.
Write the cancellation confirmation email, a 30-day win-back email and a 90-day win-back email. Make cancellation easy and respectful, ask for one-click feedback, and offer a pause option if we can support it. Save to content/email/cancellation.md and note any code needed.
Using research/personas.md, write a version of our main onboarding email and our main upgrade email for each persona, using their language and use case. Define how we would detect each persona from sign-up data. Save to content/email/segments.md.
For each lead magnet or free tool we have, write a 3-email follow-up for people who use it: deliver the resource, teach one related idea, then introduce the product as the next step. Save to content/email/lead-magnets.md.
Write 100 subject lines for our upcoming emails across product updates, tips, newsletters and offers. Keep them under 50 characters, specific, and not clickbait. Group them by type and mark the 20 strongest. Save to content/email/subject-lines.md.
Design milestone emails that celebrate user progress (first project, 10th use, 1-year anniversary, a usage record). Write each, define the trigger from data we already track in this repo, and include a soft ask (review, referral, share).
RepoWrite a script that turns merged PRs or changelog entries from the last month into a draft "what is new" email: grouped by theme, written for users not developers, with links. Show the output for this month.
RepoWrite a plan to grow our newsletter: sign-up placements on the site, a lead magnet, cross-promotion swaps with 10 named newsletters in our niche, a referral reward, and social posts that drive sign-ups. Implement the on-site sign-up placements.
Web Repo
How to run these while you sleep
- Open your project and start a fresh branch or git worktree, so the whole night is one diff you can review or delete.
- Add your product context above and keep overnight mode on. Claude will log its assumptions instead of waiting for answers.
- Paste one prompt into Claude Code, or save a few to a
queue/folder and loop over them headless. - In the morning, read the files it wrote and the diff. Merge what is good and send what needs sending yourself.
Want it off your laptop? Claude Code on the web runs each session in a cloud sandbox, so you can start a few before bed and close the lid.
Queue a night of prompts
git switch -c overnight/$(date +%F)
mkdir -p logs
for f in queue/*.md; do
claude -p "$(cat "$f")" \
--permission-mode acceptEdits \
--allowedTools "WebSearch" "WebFetch" "Bash(npm run *)" \
> "logs/$(basename "$f" .md).log"
doneOnly allow the tools a task needs. Browser prompts also need a browser MCP server such as Playwright; find one in the MCP directory.
More spare compute prompts
Free tools, calculators, templates and data pages that rank for long-tail searches and earn links on their own. Run these overnight and wake up to shippable pages.
Keyword research, content briefs, technical SEO audits and article drafts you can leave running overnight. Each prompt saves its output to a file so nothing gets lost.
Find link opportunities, draft pitches and build lists of podcasts, newsletters and journalists. These prompts do the slow research so you only do the sending.
Get listed everywhere your buyers look: startup directories, app stores, marketplaces, launch sites and review platforms. Claude prepares every listing so submitting takes minutes.
Lead lists, buying signals and the places your next customers are already asking for help. Claude does the digging; you decide who to contact.
Cold emails, follow-ups, sales pages and objection handling written from what your product actually does. Claude drafts; you review and send.
A month of posts, threads, carousels and replies drafted from your product, changelog and lessons learned. Wake up to a content queue instead of a blank page.
Demo videos, short-form scripts, animated explainers and screenshots generated with code. Use Remotion, Playwright and ffmpeg to render while you sleep.
Synthetic personas, simulated usability tests and interview prep built from your real product. Use them to find obvious problems before you spend time with real users, not instead of them.
Teardowns, pricing tracking, feature matrices and screenshots of competitor user flows. Leave a browser running overnight and come back to a full picture of the market.
Rewrite copy, audit the sign-up funnel, design A/B tests and build new landing pages. These prompts work directly in your codebase so the output is ready to review as a pull request.
Polish passes, onboarding fixes, feature specs and prototypes. Good for overnight runs because each one ends in a branch or a document you can review over coffee.
Tests, refactors, type safety, dependency upgrades and dead code removal. The classic overnight job: long, careful, and easy to review in the morning as a pull request.
Security reviews, secrets scans, load tests, bundle diets and backup checks. The work everyone puts off, done while your machine would otherwise sit idle.
Documentation, help centre articles, support macros, metrics, finance tidy-ups and the admin that piles up. Hand it to Claude when you have compute to spare.
Make Claude better at these jobs with skills, MCP servers and mods, or turn a prompt you run often into a skill with the skill generator.