15 prompts
Write 20 short-form video scripts (30 to 60 seconds) for TikTok, Reels, Shorts and LinkedIn. Each with a hook in the first 2 seconds, the on-screen text, what is shown, the voiceover, and an ending that invites a comment. Mix tutorials, myths, before/after, and quick wins tied to our product. Save to content/video/shorts.md.
Set up Remotion in a video/ folder (if not already there). Build a 60-second product demo: an opening hook, 3 key features shown with screenshots from the app, captions, our brand colours and a closing call to action. Render it to MP4 at 1920x1080 and a vertical 1080x1920 version. Document how to re-render.
RepoWrite a Playwright script that walks through our main user flow in the running app with realistic demo data, slow enough to watch, and records it as video. Add on-screen highlights for clicks. Save the recording and the script to content/video/recordings/ so it can be re-run after UI changes.
Repo BrowserWrite a 90-second animated explainer script that explains the problem, the old way, our way, and the result. Then build it in Remotion or as an HTML/CSS animation with simple shapes and text, render it, and save it to content/video/explainer/.
RepoResearch what our audience searches on YouTube around our niche. Propose 15 YouTube video ideas with search-friendly titles, a thumbnail concept, the hook, an outline with timestamps, and the keywords for the description. Write the full script for the best one. Save to content/video/youtube.md.
WebFor each of our 8 main features, write a Playwright script that performs it in the running app, record it, and convert it to an optimised GIF and MP4 (under 5MB) with ffmpeg. Save to content/video/gifs/ and add them to the matching docs pages.
Repo BrowserBuild an HTML template for YouTube thumbnails (1280x720) and blog cover images (1200x630) in our brand style, then render 10 variants for our planned videos and articles using a headless browser. Save to content/video/thumbnails/.
Repo BrowserFor every video file in content/video/, generate captions (SRT and VTT) using a local speech-to-text tool such as whisper if available, clean up the text, and write a transcript and a blog-post version of each. Save next to each video.
RepoWrite 10 talking-head video scripts I can record on my phone in one take: under 90 seconds, conversational, one idea each, with a cue card version of 5 bullet points. Topics should mix advice, product tips and founder lessons. Save to content/video/talking-head.md.
Take our most interesting dataset (content/study/ or public data in our niche) and build an animated chart video, such as a bar chart race or a line that builds over time, with Remotion or D3 plus a recorder. Add a title, source note and voiceover script. Render to MP4.
RepoWrite scripts for a 5-part onboarding video series (2 to 3 minutes each) that takes a new user from sign-up to their first real result. Include what to show on screen at each step based on the actual flows in this repo, and then record the screen parts with Playwright.
Repo BrowserTake the long video or webinar in content/video/ and its transcript. Find the 10 best 30 to 60 second moments (a strong claim, a story, a tip). Cut them with ffmpeg, crop to vertical, burn in captions, and write a post caption for each. Save to content/video/clips/.
RepoWrite 10 short video ad concepts and 10 static ad concepts for our product, each with a different angle (pain, outcome, social proof, comparison, curiosity). Then render the static ones as images from an HTML template at 1080x1080 and 1080x1920. Save to content/ads/.
Repo BrowserFind the 10 concepts in our docs that would be clearer with a diagram (architecture, data flow, lifecycle, setup steps). Draw each as Mermaid or SVG in our colours, add them to the docs pages, and make sure they read well in dark mode.
RepoFor each video we have or plan, write a YouTube title, description with chapters, tags, a pinned comment, and the matching blog embed page with a transcript and VideoObject structured data. Save to content/video/seo.md and add the embed pages to the site.
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.
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.
Welcome sequences, onboarding emails, newsletters and re-engagement campaigns written from your actual product, plus the templates to send them.
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.