20 prompts
Go through every screen in the app in the browser. Fix inconsistent spacing, misaligned elements, mixed font sizes, inconsistent button styles, missing hover and focus states, and anything that looks broken at common widths. Keep changes small and in line with the existing design system. Take before/after screenshots and list every change.
Browser RepoFind every list, table, dashboard and page that can be empty. Replace blank or "No data" states with helpful ones: what this area is for, a single clear action, and a sample or template where it helps. Implement them with existing components.
RepoDesign and build an in-app onboarding checklist with the 4 to 6 actions that best predict a user sticking around. It should track progress from existing data, be dismissible, and celebrate completion. Add analytics events for each step.
RepoAdd or fix dark mode across the app using the existing styling approach: tokens or CSS variables, respect the system preference, a toggle that persists, and no hard-coded colours left. Check every page in the browser in both themes and fix contrast problems.
Repo BrowserAdd a command palette (Cmd/Ctrl+K) that searches pages, actions and recent items, plus keyboard shortcuts for the 10 most common actions, with a "?" overlay listing them. Make sure shortcuts do not fire while typing in inputs.
RepoTake the top item from research/feature-requests.md (or the most requested thing you can find in issues). Write a product spec: the problem and evidence, users affected, goals and non-goals, user flows, edge cases, UI sketch in words or ASCII, data model changes, rollout plan and success metric. Save to docs/specs/[feature].md.
RepoBuild a working prototype of the feature in the newest spec in docs/specs/ on a new branch. Aim for the happy path end to end with real data, behind a feature flag if one exists. List the shortcuts you took and what production-ready would need.
RepoReview the settings pages. Group settings logically, write clear descriptions for each, add sensible defaults, show what changed with a save confirmation, and remove or hide settings almost nobody should touch. Implement the changes.
RepoFind every place the app waits on data. Replace spinners on full pages with skeletons that match the final layout, add optimistic updates where safe, and make sure slow requests show progress instead of freezing. Test with network throttling.
Repo BrowserReview every form in the app. Add inline validation with clear messages, keep user input on errors, disable double-submit, show what is required, and make error messages say how to fix the problem. Implement with the existing form library.
RepoBased on the codebase, open issues, research/ findings and competitor gaps, write a 3-month roadmap: themes, the bets in each, why now, what we are not doing, and how we will measure each. Save to docs/roadmap.md for me to edit.
RepoCheck whether users can get their data in and out. Add CSV/JSON export for the main data types and an import from the most common tool our users switch from, with a preview and error report. Switching cost is a top objection, so make it smooth.
RepoList every notification, toast, email and alert the app sends. Remove noisy ones, group related ones, add user controls, and make sure every important event has a notification. Implement and document the notification matrix in docs/notifications.md.
RepoAdd 5 to 10 starter templates or sample projects that show what the product can do and let new users start from something real. Write them with realistic content and wire them into onboarding.
RepoAdd or improve search in the app: search across the main entities, highlight matches, handle typos where cheap, show recent searches, and keep it fast. Use the database's built-in full text search if possible before adding a new service.
RepoCheck every page at 360px, 768px, 1024px and 1440px wide in the browser. Fix overflow, cramped tables (stack or scroll them), unreadable text and broken navigation. Screenshot before and after.
Browser RepoAdd a public changelog page built from our release notes or merged PRs, and an optional public roadmap page. Give each entry a date, a plain-language summary and an image slot, with an RSS feed. Both pages help SEO and trust.
RepoAdd a lightweight feedback button that captures a message, the current page, and optional screenshot, and sends it to wherever we already store data or email. Include a thank-you message and rate limiting.
RepoInventory every colour, font size, spacing value, radius, shadow and component variant used in the codebase. Find duplicates and near-duplicates, propose a consolidated set of tokens, and refactor the worst offenders to use them. Save the inventory to docs/design-system.md.
RepoFind 10 small moments in the app where a touch of delight would help: a success animation, a friendly empty state, a helpful default, a smart suggestion, a nice share preview. Implement the 5 cheapest without hurting performance or accessibility.
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.
Welcome sequences, onboarding emails, newsletters and re-engagement campaigns written from your actual product, plus the templates to send them.
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.