300 prompts
- Link magnets
20 link magnet ideas ranked by effort
Read this repo and the product docs to understand what we sell and who buys it. Brainstorm 40 link magnets (free tools, calculators, generators, checkers, templates, datasets, interactive explainers) our audience would search for and bookmark. For each, give the long-tail keyword it targets, why people would link to it, how it leads back to the product, and build effort (S/M/L). Cut to the best 20 and save them ranked to growth/link-magnets.md with the top 3 marked "build first".
Web - Link magnets
Build one free tool end to end
Take the top idea from growth/link-magnets.md (or pick the strongest small free tool for our audience if that file does not exist) and build it as a new page in this codebase. It must work without sign-up, load fast, have a clear H1 that matches the keyword, 300+ words of genuinely useful explanation below the tool, an FAQ with 5 real questions, a soft CTA to the product, and correct title, meta description, canonical and Open Graph tags. Follow existing code patterns, then run the build and lint.
Repo - Link magnets
Calculator pages for every metric we touch
List every number our users calculate by hand or in a spreadsheet because of the problem we solve (costs, ROI, conversion rates, time saved, sizing, pricing). Pick the 10 with real search demand. For each, write the formula, the inputs and sensible defaults, a worked example, and the target keyword. Then build the 3 best as calculator pages using the existing components, each with an explanation section and FAQ.
Web Repo - Link magnets
Programmatic SEO page set
Find a pattern where we could make 50 to 500 useful pages from structured data, such as "[tool] alternatives", "[integration] + our product", "[job title] templates" or "[city] [service] costs". Propose 3 patterns with the keyword shape, the data source, what makes each page unique enough to not be thin content, and a sample of 10 URLs. Pick the best one, build the data file and a page template, and generate the first 20 pages with internal links between them and a sitemap entry.
Web Repo - Link magnets
Free template library
Work out which documents, checklists, spreadsheets, prompts or config files our audience copies from blog posts every week. Write 15 genuinely good templates (not filler), each with a one-line use case, when to use it, the template itself in copy-paste form, and a filled-in example. Save them to content/templates/ as one markdown file each, plus an index page draft that targets "[topic] templates".
- Link magnets
Original data study
Design a small original data study we could publish that journalists and bloggers would cite. Use public data (APIs, open datasets, GitHub, public pricing pages, our own anonymised aggregate numbers if the repo has them) and actually collect it. Produce the dataset as CSV, 5 headline findings with numbers, 3 charts described or rendered, a methodology section, and a 1,200-word write-up draft in content/study/. Flag any finding that rests on a small sample.
Web - Link magnets
Glossary that ranks
Build a glossary of the 60 terms people in our niche search for definitions of. For each term write a clear 2-sentence definition, a 150-word explanation with an example, related terms, and a natural link to the product where it fits. Group terms by theme, and output a data file the site can render as /glossary and /glossary/[term] pages. Skip any term where we have nothing better to say than Wikipedia.
Web - Link magnets
Comparison table people bookmark
Research the 15 to 25 main tools in our category from their public sites and docs. Build an honest, sortable comparison table: pricing tiers, free plan limits, key features, integrations, platforms, best for. Cite the source URL and date checked for every cell. Save the data as JSON and draft a page "Best [category] tools compared (updated [month year])" with a short verdict for each. Be fair to competitors, including where they beat us.
Web - Link magnets
Checker or grader tool
Design a free "grader" or "checker" for our niche: the user pastes a URL, text, file or config and gets a score with specific fixes (think website graders, headline analyzers, config linters). Define 10 to 15 scoring rules with clear pass/fail logic and the fix text for each. Then build it as a page in this repo that runs client-side where possible, shows the score and fixes, and ends with a CTA. Add tests for the scoring rules.
Repo - Link magnets
Interactive explainer
Pick the single concept in our space that beginners find hardest to understand. Build an interactive explainer page: a step-by-step visual with controls the reader can change, plain-language text alongside each step, and a summary at the end. Use the frameworks already in this repo, keep it accessible (keyboard, contrast, reduced motion), and target the "how does [concept] work" keyword.
Repo - Link magnets
Generator tool with shareable output
Design a free generator (names, policies, bios, briefs, configs, prompts, schemas) that solves a small job our audience does often. The output must be good enough to use as is, and shareable by URL so people send it to colleagues. Build it in this repo with a permalink for each result, a "made with" footer link back to us, and metadata so shared links preview well.
Repo - Link magnets
Statistics roundup page
Collect 80 to 100 recent, sourced statistics about our industry and audience (published within the last 2 years where possible). Verify each by opening the original source, not a roundup that quotes it. Group them by theme, write a short intro for each group, and save as content/stats.md with the source link and year next to every stat. Writers link to stats pages constantly, so accuracy is the whole point: drop anything you cannot trace to a primary source.
Web - Link magnets
Awesome list we own
Create a curated "awesome list" for our niche: 100+ resources (tools, libraries, guides, communities, datasets, people) grouped into clear sections with a one-line honest description each. Check every link works. Save it as a README.md ready for a public GitHub repo, with contribution guidelines, and suggest 10 places to announce it. Include our product only once, in the section where it genuinely fits.
Web - Link magnets
Embeddable widget or badge
Design something other sites can embed that links back to us: a badge, a live stat, a mini calculator, a status widget or a "powered by" card. Build the embed (a script or iframe plus the snippet users paste), a page that generates the snippet, and make sure the embed is lightweight, works on any site, and includes a followed link back. Explain who would embed it and why.
Repo - Link magnets
Long-tail question pages
Mine People Also Ask, Reddit, Stack Overflow, Quora and forums for 50 specific questions our audience asks about the problem we solve. Cluster them, and for the 15 clusters with the clearest intent write a draft answer page: a direct answer in the first 2 sentences, a detailed explanation, an example, and a related-questions section. Save to content/answers/.
Web - Link magnets
Free course or email series
Outline a free 7-lesson course that teaches our audience the skill our product makes easier. Write all 7 lessons in full (800 to 1,200 words each, with exercises), the landing page copy targeting "[skill] course" and "learn [skill]", and the 7 matching emails. Save everything to content/course/. The product should appear only where it truly saves a step.
- Link magnets
Benchmark or leaderboard page
Find something in our niche that can be measured and ranked (speed, price, accuracy, popularity, uptime) and is not already well covered. Design a repeatable benchmark: what is measured, how, how often, and how ties and bias are handled. Run the first round with real data, save results as JSON, and draft a leaderboard page plus a script that can refresh it on a schedule.
Web Repo - Link magnets
Cheat sheet worth printing
Write the definitive one-page cheat sheet for the main tool, language, framework or workflow our audience uses. It must fit on one printed page, be grouped logically, and include the commands or shortcuts people actually forget. Produce it as markdown and as a print-friendly HTML page with a download button, targeting "[tool] cheat sheet".
- Link magnets
Audit existing pages for link-magnet potential
Go through every public page in this codebase. Find pages that could become link magnets with modest work: a blog post that could become a tool, a docs page that could become a reference, a feature page that could become a free version. List the top 10 with what to change, the keyword it would target, and effort. Save to growth/upgrade-existing-pages.md.
Repo - Link magnets
Seasonal and trend pages
List the dates, events, reports, launches and trends in our industry over the next 12 months that cause search spikes. For each, propose a page we could publish 4 to 6 weeks earlier (a tracker, guide, template, or prediction piece), with the keyword and a publish-by date. Save as a content calendar to growth/seasonal.md and fully draft the next 2 due.
Web - SEO & content
Keyword map from the product
Read the codebase, docs and marketing pages to list every problem, feature, integration and use case we cover. Turn them into a keyword map of 150 keywords grouped into topic clusters, with search intent (informational, commercial, transactional), a rough difficulty guess with your reasoning, and which existing page should rank for each (or "new page needed"). Save to seo/keyword-map.csv and a summary of the 10 biggest gaps.
Web Repo - SEO & content
Technical SEO audit of this site
Audit this codebase for technical SEO: titles and meta descriptions (missing, duplicate, too long), canonicals, robots and noindex, sitemap coverage, broken internal links, heading structure, image alt text, structured data, Open Graph tags, hreflang if relevant, and pages that render content only client-side. Write findings to seo/technical-audit.md sorted by impact, then fix the safe ones in a branch and list what you changed.
Repo - SEO & content
10 content briefs
Pick the 10 highest-value missing pages from seo/keyword-map.csv (or research them if it does not exist). For each, write a brief: target keyword and variants, search intent, what the top 5 results cover and miss, a suggested H1 and outline, questions to answer, internal links to add, and a unique angle only we can offer. Save each to seo/briefs/[slug].md.
Web - SEO & content
Write 5 articles from briefs
Take 5 briefs from seo/briefs/ and write each article in full. Lead with the answer, use concrete examples, include original screenshots or code where it helps (describe what to capture if you cannot), avoid filler intros and generic conclusions, and link to the product only where it saves the reader real effort. Each article 1,500 to 2,500 words. Save drafts to content/drafts/ and list the facts I should double-check.
- SEO & content
Refresh decaying content
Find every blog post or guide in this repo older than 12 months. For each, check whether facts, screenshots, prices, versions or links are now out of date (verify against current sources). Rewrite the 5 most valuable ones with updated information, a new "updated [month year]" note, better structure and stronger answers to the main question. Keep the URLs the same.
Web Repo - SEO & content
Internal linking pass
Map every content page in this codebase and the topics it covers. Find pages that mention a topic we have a dedicated page for but do not link to it, orphan pages with no internal links in, and hub pages that should link to their cluster. Add contextual internal links with descriptive anchor text (no "click here"), at most 5 new links per page. Output a table of every link added.
Repo - SEO & content
Structured data everywhere it fits
Review every page type on this site and add the right schema.org JSON-LD: Organization, WebSite with SearchAction, BreadcrumbList, Article, FAQPage, Product, SoftwareApplication, HowTo or ItemList where the content genuinely matches. Use real values from the page, not placeholders. Validate the output shape, and write a short note on which rich results each page type could now get.
Repo - SEO & content
Rewrite every title and meta description
List every indexable page with its current title and meta description. Rewrite each to match the main search intent, include the primary keyword naturally, stay under 60 and 155 characters, and give a reason to click (a number, a year, a benefit, a free tool). Apply the changes in code and output a before/after table so I can review.
Repo - SEO & content
"Alternatives to" pages
For each of our 5 biggest competitors, research their product, pricing, strengths and common complaints (G2, Capterra, Reddit, Twitter/X, app store reviews). Draft a "[Competitor] alternatives" page that lists 6 to 8 real alternatives, including us, with honest pros and cons, who each is best for, and pricing. Save to content/alternatives/. Never invent claims about competitors; cite sources.
Web - SEO & content
"Us vs them" comparison pages
Write a "[Our product] vs [Competitor]" page for each of our top 5 competitors: a 2-sentence verdict, a feature table, pricing compared, where they win, where we win, and who should pick which. Pull facts from their current public pages and cite them. Keep the tone fair, because biased comparison pages do not rank or convert. Save to content/vs/.
Web - SEO & content
Topic cluster plan
Pick the 3 topics most tied to buying our product. For each, design a cluster: one pillar page and 10 to 15 supporting pages, with the keyword, intent and angle of each, and how they interlink. Mark which pages already exist in this repo. Save to seo/clusters.md and write the pillar page for the most important cluster in full.
Web Repo - SEO & content
Search intent check on key pages
For our 10 most important pages, search the main keyword and look at what Google currently ranks: format (list, tool, guide, product page), length, angle and freshness. Tell me for each page whether our format matches the intent, and if not, exactly what to change. Save to seo/intent-check.md.
Web - SEO & content
Featured snippet grabs
Find 20 queries in our niche where a featured snippet or AI overview shows. For each, note the current format (paragraph, list, table) and the page holding it. Write a better snippet-shaped answer we could place on one of our pages (40 to 60 words for paragraphs, clean steps for lists), and say which page it belongs on.
Web - SEO & content
Get cited by AI search
Research how our product and category appear in AI answers (ChatGPT, Perplexity, Claude, Google AI Overviews) for the 20 questions buyers ask. Note which sources get cited. Then recommend concrete changes so we get cited more: pages to create, facts to state plainly, comparison tables, an llms.txt file, third-party sites to get mentioned on. Write the llms.txt and the top 3 page changes.
Web Repo - SEO & content
Image SEO pass
Find every image in this codebase. Add or fix descriptive alt text, rename unhelpful filenames where safe, make sure images have width and height set, use modern formats and lazy-load below the fold. List images over 200KB with a suggested fix. Output a table of changes.
Repo - SEO & content
Core Web Vitals fixes
Run Lighthouse (or analyse the code if you cannot run it) on the 5 most important pages. Find the biggest causes of slow LCP, layout shift and slow interaction: render-blocking scripts, huge bundles, unoptimised images, fonts, third-party tags. Fix what is safe in a branch, measure again, and report the before/after numbers.
Repo Browser - SEO & content
Local or niche landing pages
If our product serves specific industries, roles, locations or use cases, list the 20 segments with the most search demand. For each, write a landing page draft that uses that segment's language, problems and examples (not a find-and-replace of the same page). Save to content/segments/ with the keyword each targets.
Web - SEO & content
Reddit and forum question harvest
Search Reddit, Hacker News, Indie Hackers, Stack Exchange and niche forums for threads from the last year where people ask about the problem we solve. Collect 100 real questions in the asker's own words, with the link and upvote count. Cluster them, and for each cluster suggest a page, a doc update or a product change. Save to seo/questions.csv and seo/questions-summary.md.
Web - SEO & content
Content gap vs a competitor
Crawl the blog, docs and resource pages of our biggest competitor (respect robots.txt). List every topic they cover that we do not, and estimate which ones bring them traffic based on how prominent and linked they are. Give me the 25 best gaps with a suggested angle that beats their version. Save to seo/content-gap.md.
Web - SEO & content
Write the docs pages that rank
Developers and power users search for "how to [do X] with [our product]" and integration guides. List 20 such tasks from our features and support questions. Write 5 of them as complete how-to docs pages with steps, code or screenshots to capture, common errors and fixes. Save them where the docs live in this repo.
Repo - Backlinks & PR
Source 20 real backlink opportunities
Find 20 specific, realistic backlink opportunities for our site: resource pages that list tools like ours, "best [category] tools" posts, broken links we could replace, unlinked mentions of our brand, and guest post spots in our niche. For each give the exact URL, why it fits, the contact (name, email or form if public), and a one-line pitch angle. Save to growth/backlinks.csv. Skip link farms and paid-link sites.
Web - Backlinks & PR
"Best tools" listicles we are missing from
Search for every "best [our category] tools", "top [category] software" and "[category] alternatives" article ranking on page 1 to 2. List the ones that do not mention us, with the author, publish date, how often they update it, and contact details if public. Draft a short, specific pitch for each explaining what we do differently. Save to growth/listicle-targets.csv.
Web - Backlinks & PR
Unlinked brand mentions
Search the web for mentions of our product name, founder names and domain that do not link to us (blogs, forums, news, directories, GitHub READMEs). List each with the URL, the context of the mention, and a friendly 3-sentence note asking for a link. Save to growth/unlinked-mentions.csv.
Web - Backlinks & PR
Broken link building
Find 30 resource pages and roundups in our niche. Check their outbound links and find dead ones (404s, expired domains, moved content) where we have or could make a better replacement. For each, note the dead URL, what it used to be (check the Wayback Machine), our replacement page, and the page owner's contact. Save to growth/broken-links.csv.
Web - Backlinks & PR
Podcast guest list
Find 30 podcasts our target customers listen to that take guests, active in the last 3 months. For each: show name, host, audience, recent guest examples, how to pitch (form, email), and 3 episode topics I could credibly talk about. Draft a personalised pitch email for the top 10 that references a specific recent episode. Save to growth/podcasts.md.
Web - Backlinks & PR
Newsletter sponsorship and feature list
Find 40 newsletters our audience reads, with subscriber count if public, frequency, whether they take sponsors (and rough price if listed), and whether they feature tools or community submissions for free. Rank by fit. Draft a submission blurb for the free-feature ones. Save to growth/newsletters.csv.
Web - Backlinks & PR
Journalist and writer list
Find 25 journalists, bloggers and analysts who wrote about our category or the problem we solve in the last 6 months. For each, list their outlet, 2 recent relevant articles, their beat, and how they prefer to be contacted (from their bio, not guessed). Suggest a story angle tailored to each. Save to growth/press-list.csv.
Web - Backlinks & PR
Press release and press kit
Write a press kit for our product: a one-paragraph boilerplate, a 300-word press release about our latest launch or milestone, founder bio, key facts and numbers, 5 quotable lines, and a list of screenshots and logos to include. Save to content/press/ and build a /press page in this repo if one does not exist.
Repo - Backlinks & PR
Guest post pitches
Find 20 blogs in our niche that accept guest posts and have real readership (check that posts get comments or shares). For each, read 3 recent posts and propose 2 article ideas that fit their audience and that they have not covered. Draft the pitch emails. Save to growth/guest-posts.md.
Web - Backlinks & PR
Answer journalist requests
Look up current public journalist request platforms and threads (Qwoted, Featured, SourceBottle, #journorequest on social media, HARO successors) for queries in our area. List the open ones we could answer credibly, and draft a concise expert reply for each with a specific insight or data point. Save to growth/journalist-replies.md.
Web - Backlinks & PR
Partner and integration links
List every tool we integrate with, depend on, or are commonly used alongside. For each, find whether they have a partners page, integrations directory, marketplace, showcase or "built with" page, and how to get listed. Draft the listing copy for each. Save to growth/partner-links.csv.
Web Repo - Backlinks & PR
University and .edu resource pages
If our product or content helps students, researchers or educators, find 20 university resource pages, course reading lists and library guides that list tools or resources like ours. Note the page, maintainer contact, and a short polite note explaining why our free resource helps their students. Save to growth/edu-targets.csv.
Web - Backlinks & PR
Open source mentions
Find GitHub repos, awesome lists and docs sites where our product or something like it would be a useful addition. For awesome lists, check the contribution rules and draft the exact pull request line and description in their format. List 20 targets with links. Save to growth/oss-targets.md.
Web - Backlinks & PR
Expert roundup contributions
Find 15 expert roundup posts, "we asked 30 founders" pieces and community surveys in our niche published regularly. Note how contributors get included. Draft 5 sharp, quotable answers I could give on common roundup questions in our field, each with a specific example or number.
Web - Backlinks & PR
Competitor backlink sources
Using any free data you can reach (public backlink checkers, "who links to" searches, mentions of the competitor's domain), find where our 3 main competitors get links from. Group the sources by type and list the 30 that we could realistically get too, with how. Save to growth/competitor-links.csv.
Web - Backlinks & PR
Testimonial-for-link swaps
List every tool, service and vendor we pay for or use (check package.json, infra config, the footer, and ask-free sources). Find which ones publish customer testimonials or case studies. Draft a short genuine testimonial for each that we would be happy to give, plus the email offering it. Save to growth/testimonials-to-give.md.
Web Repo - Backlinks & PR
Data story pitch
Take our most interesting data (from content/study/, product usage stats in the repo if any, or public data) and find the one finding that would surprise people. Write the headline, a 150-word pitch, 3 supporting numbers and a chart idea, and a list of 15 reporters and blogs who cover this exact topic. Save to growth/data-pitch.md.
Web - Backlinks & PR
Award and "best of" lists
Find awards, annual "best of" lists, startup competitions and industry rankings our product could enter in the next 6 months. List each with the deadline, entry cost, criteria and how winners are announced. Draft the entry for the 3 best fits. Save to growth/awards.md.
Web - Backlinks & PR
Conference and meetup talks
Find 20 conferences, meetups and online summits in our niche with open calls for speakers in the next 6 months. List the deadline, audience and format. Write 3 talk proposals (title, abstract, takeaways, outline) that teach something useful rather than pitch the product. Save to growth/talks.md.
Web - Backlinks & PR
Link outreach sequence
Using growth/backlinks.csv (or research targets first if it is missing), write a personalised outreach email for each target, under 120 words, that references something specific on their page, explains what we offer their readers, and makes one clear ask. Add a polite follow-up for 5 days later. Save as a CSV with columns for name, email, subject, body and follow-up so I can load it into a mail tool.
Web - Directories & launches
Find 50 directories to list on
Find 50 directories, launch sites and listing platforms that fit our product: startup and SaaS directories, AI tool directories, category-specific listings, review sites, alternative-to sites, and regional startup lists. For each give the URL, whether it is free, whether the link is followed if you can tell, rough traffic or authority signals, and the submission requirements. Rank by fit and save to growth/directories.csv. Skip anything that looks like a spam link farm.
Web - Directories & launches
Write every listing variant once
Write our listing copy in every length directories ask for: a 60-character tagline, a 160-character short description, a 500-character description, a 1,500-character long description, 10 tags and categories, a feature list, pricing summary, and a founder comment. Base it on the real product in this repo. Save to growth/listing-copy.md so I can paste into any form.
Repo - Directories & launches
Submit to directories in the browser
Using growth/directories.csv and growth/listing-copy.md, open each free directory submission form in the browser and fill it in with our details. Stop before any step that needs payment, a captcha, email verification or creating an account with a password, and log those for me. Keep a log in growth/directories-log.csv with the status of each.
Browser - Directories & launches
Product Hunt launch kit
Prepare a full Product Hunt launch: tagline options, the description, the first maker comment, 5 gallery image ideas with captions, a 30-second demo video script, the topics to pick, a hunter shortlist with reasons, a launch-day timeline in Pacific time, and messages to send supporters (asking for feedback, not upvotes). Save to growth/launch/product-hunt.md.
Web - Directories & launches
Show HN post
Write a Show HN post for our product following the community guidelines: a plain title that says what it is, a first comment that explains why we built it, how it works technically, what is free, and what we want feedback on. Read the top 10 Show HN posts of the last month to calibrate tone. Also list the 10 hardest questions HN will ask and draft honest answers. Save to growth/launch/show-hn.md.
Web - Directories & launches
Reddit launch plan
Find 15 subreddits where our product is on-topic and self-promotion is allowed (read each subreddit's rules and note them). For each, draft a post that leads with something useful to that community, such as what we learned, a free resource, or a story, and mentions the product naturally. Note the best day and time to post. Save to growth/launch/reddit.md.
Web - Directories & launches
App store and marketplace listings
List every marketplace where our product could be listed: browser extension stores, app stores, Slack/Zapier/Shopify/WordPress/Figma/VS Code marketplaces, cloud marketplaces, GPT and AI agent stores, MCP and plugin directories. For each, describe what we would need to build or package to qualify and the effort. Rank by audience fit. Save to growth/marketplaces.md.
Web Repo - Directories & launches
Review site profiles
Write complete profiles for G2, Capterra, GetApp, Software Advice, TrustRadius, AlternativeTo, SaaSHub and Slashdot: categories, description, features, pricing, screenshots to upload, and the competitors to list against. Draft a short email asking happy users to leave a review on the one that matters most for us. Save to growth/review-sites.md.
Web - Directories & launches
AI tool directory blitz
If our product uses AI in any way, find 40 AI tool directories and newsletters that list tools (There's An AI For That, Futurepedia, Toolify and the many smaller ones). Check which are free, which still accept submissions, and their categories. Save to growth/ai-directories.csv with the listing copy adapted to how each describes tools.
Web - Directories & launches
GitHub repo that gets found
If any part of our product is or could be open source (SDK, CLI, examples, templates), make the repo discoverable: a README with a clear one-liner, a GIF or screenshot, install in one command, badges, topics, a good social preview description, and a contributing guide. Draft the changes in this repo and list the topics and awesome lists to submit to.
Repo - Directories & launches
Startup database profiles
Write our profile for Crunchbase, Wellfound (AngelList), LinkedIn company page, BetaList, F6S, Indie Hackers products and any regional startup databases. Include the fields each asks for. Save to growth/startup-profiles.md and flag fields that need a decision from me (funding, team size, founding date).
Web - Directories & launches
Launch week calendar
Plan a 2-week launch: which directories and communities to hit on which day so traffic is spread out, what to post on each social channel each day, the emails to send, and the follow-ups. Base it on growth/directories.csv and growth/launch/ if they exist. Save as growth/launch/calendar.md with a checklist I can tick off.
- Directories & launches
Listing screenshots
Run the app locally and take a clean set of screenshots for listings: the hero view, 4 key features, mobile view, and an empty-to-done flow, at the sizes directories commonly need (1270x760, 1920x1080, square 1080). Use realistic demo data, hide anything personal, and save them to growth/screenshots/ with a caption file.
Browser Repo - Directories & launches
Directory listing audit
Search for every place we are already listed online. Check each listing for out-of-date descriptions, old pricing, broken links, old logos or wrong categories. List what needs updating and the exact new copy for each. Save to growth/listing-audit.md.
Web - Directories & launches
Niche community launch posts
Find the Slack groups, Discord servers, Facebook groups, LinkedIn groups and forums where our buyers hang out and that have a "show your project" or tools channel. List them with the rules for promotion. Draft a short, non-spammy post for each that fits its culture. Save to growth/communities.md.
Web - Finding customers
Find 20 potential customers
From the product in this repo, define our ideal customer in one paragraph (company type, size, role, trigger). Then find 20 real companies or people who match, using public sources only. For each give the name, website, why they fit, the signal you found (a job post, a tweet, a forum question, a tech stack, a funding round), the best person to contact and a public way to reach them. Save to sales/leads.csv. Do not guess email addresses.
Web Repo - Finding customers
People asking for exactly what we do
Search Reddit, Hacker News, Twitter/X, LinkedIn posts, Indie Hackers, Stack Overflow and niche forums from the last 60 days for people asking for a tool, recommendation or workaround for the problem we solve. List 30 threads with the link, date, what they asked, and a helpful reply draft that answers their question first and mentions us only if it truly fits. Save to sales/intent-threads.md.
Web - Finding customers
Ideal customer profile from real data
Look at whatever customer data exists in this repo (seed data, analytics events, admin views, test fixtures, CRM exports) and the product's features. Write an ideal customer profile: firmographics, roles, the job they hire us for, triggers that make them look, objections, where they hang out, and words they use. Then write 3 anti-personas we should not chase. Save to sales/icp.md.
Repo - Finding customers
Job posts as buying signals
Search job boards for companies hiring for roles whose work our product automates or supports (for example a company hiring 3 support agents needs support tooling). Find 25 such companies posted in the last 30 days. For each list the role, link, company size, and a one-line reason we can help right now. Save to sales/hiring-signals.csv.
Web - Finding customers
Competitor customers who are unhappy
Find public complaints about our competitors: G2 and Capterra reviews of 3 stars or less, Reddit threads, tweets, app store reviews, GitHub issues. List 30 with the source, the specific pain, and whether we solve it. Summarise the 5 most common complaints and how we could speak to them. Save to sales/switchers.md. Do not contact anyone; this is research.
Web - Finding customers
Tech stack lead list
Our product works best with certain tools (check integrations and dependencies in this repo). Find 30 companies that publicly use those tools (case studies, "built with" pages, public job posts naming the stack, GitHub orgs). Note which tool, the evidence, and the company size. Save to sales/stack-leads.csv.
Web Repo - Finding customers
Communities where buyers gather
List 30 online communities where our buyers talk shop: subreddits, Slack and Discord groups, forums, LinkedIn and Facebook groups, newsletters with comment sections. For each give the size, activity level, rules on promotion, and the 3 most common questions asked there recently. Save to sales/communities.md with a plan to be useful in the top 5.
Web - Finding customers
Recently funded companies in our niche
Find 20 companies that announced funding in the last 90 days and fit our customer profile. For each list the round, date, what they do, and why new funding makes our product timely for them (hiring, scaling, new launch). Save to sales/funded.csv.
Web - Finding customers
Partners who already have our customers
List 20 agencies, consultants, freelancers, educators, and complementary tools whose clients are our ideal customers. For each, explain the overlap, what a partnership could look like (referral, integration, bundle, co-marketing), and who to contact. Draft one partnership email I can adapt. Save to sales/partners.md.
Web - Finding customers
Find our first 10 power users
Look through whatever user data, logs, analytics queries or database seed scripts this repo exposes and write the query that would find our most engaged users (usage frequency, features used, team size). Then draft a personal message to send each one asking for a 20-minute call, and the 8 questions to ask. Do not run anything against production; save the query and drafts to sales/power-users.md.
Repo - Finding customers
GitHub users with the problem
Search GitHub issues, discussions and READMEs for people struggling with the problem we solve (for example issues asking for a feature we have, or repos that hand-roll what we offer). List 25 with the link, what they are trying to do, and a helpful comment that solves their issue. Save to sales/github-signals.md. Do not post anything.
Web - Finding customers
Lookalikes of our best customers
I will list our 3 best customers in sales/best-customers.md (or infer them from case studies on our site). For each, find 10 lookalike companies: same industry, size, model and stack. Explain the match for each. Save to sales/lookalikes.csv.
Web - Finding customers
Local and offline leads
If our product could serve local businesses, pick 3 cities and find 20 businesses in each that fit, using public listings. Note their website, what they currently use if visible, and an observation about their site or service that shows how we could help. Save to sales/local-leads.csv.
Web - Finding customers
Twitter/X and LinkedIn people to follow and help
Find 40 people on Twitter/X and LinkedIn who are our ideal buyers or influence them, and who post regularly about the problem we solve. List their handle, follower range, what they post about, and 2 recent posts I could reply to with something useful. Save to sales/people-to-engage.md.
Web - Finding customers
Lead scoring rules
Using sales/icp.md and the leads in sales/*.csv, design a simple 100-point lead scoring model: fit signals, intent signals, timing signals, each with points. Score every lead we have, sort them, and explain the top 10. Save the model to sales/scoring.md and the scored list to sales/leads-scored.csv.
- Finding customers
Events where buyers will be
Find 15 conferences, trade shows, meetups and webinars in the next 6 months where our buyers attend. For each give the date, location, cost, audience, and a cheap way to be present (attend and meet, speak, sponsor a small slot, host a side event). Save to sales/events.md.
Web - Finding customers
Marketplace and RFP opportunities
Find places where people post projects or requests we could fulfil: public RFPs, government tenders, freelance job boards, "looking for a tool" posts and procurement portals in our niche. List 15 current opportunities with the deadline and requirements. Save to sales/opportunities.md.
Web - Finding customers
Churned or inactive user win-back list
Write the query (do not run against production) that finds users who signed up but went inactive, grouped by where they stopped in onboarding. Draft a different win-back message for each group that addresses the likely reason, offers help, and asks one question. Save to sales/win-back.md.
Repo - Finding customers
Free consult offer for leads
Design a small free offer that gets ideal customers to talk to us: an audit, a teardown, a setup session, or a custom report. Write the landing page copy, the booking form questions, a deliverable template, and the follow-up email that leads into the product. Save to sales/free-offer.md.
- Finding customers
Weekly lead report
Write a script that I can run each week to collect new buying signals from public sources (RSS feeds, subreddit searches, job board feeds, GitHub search) for our keywords, dedupe against sales/leads.csv, and write a short markdown report of new leads with links. Add instructions for scheduling it. Keep it within each site's terms.
Repo Web - Outreach & sales
Personalised cold emails for every lead
For each lead in sales/leads.csv, research their company and the signal that made them a lead. Write a cold email under 100 words: a specific observation about them, the one problem we solve for companies like theirs, a proof point, and a low-effort ask. No flattery and no "I hope this finds you well". Add 2 follow-ups. Save to sales/outreach.csv with subject, body, follow-up 1 and follow-up 2 columns.
Web - Outreach & sales
Objection handling guide
List the 20 objections prospects raise about products like ours (price, switching cost, security, "we built it ourselves", timing, a competitor). Use reviews, forums and our own docs as evidence. For each write a short, honest response, a proof point, and a question to ask back. Save to sales/objections.md.
Web - Outreach & sales
Sales one-pager
Write a one-page sales sheet for our product: the problem in the buyer's words, what we do, 3 outcomes with numbers where we have them, how it works in 3 steps, pricing, security and compliance notes, a customer quote, and a call to action. Make a markdown version and a print-ready HTML version. Save to sales/one-pager/.
Repo - Outreach & sales
Demo script
Write a 15-minute demo script for a sales call: discovery questions for the first 3 minutes, a demo path that shows the "aha" moment within 5 minutes, the 3 features to show for each persona, how to handle the top questions mid-demo, and a close. Base it on the real product flows in this repo. Save to sales/demo-script.md.
Repo - Outreach & sales
LinkedIn outreach messages
Write a LinkedIn connection note (under 300 characters) and a 3-message follow-up sequence for each of our 3 personas. Each message should give something (an insight, a resource, a relevant post) before asking for anything. Save to sales/linkedin.md.
- Outreach & sales
Case study from a happy customer
Draft a case study template and then a full example using what I can tell you or what is in our testimonials: the customer's situation before, why they chose us, how they rolled it out, results with numbers, and a quote. Also write the 10 interview questions to send a customer to collect this. Save to sales/case-study.md.
- Outreach & sales
Pricing page objections audit
Read our pricing page and plans in this repo. List every question a buyer would have that the page does not answer (limits, overages, annual discount, cancellation, what counts as a seat, refunds, data export). Write the answers as an FAQ section and suggest any plan naming or layout changes. Save to sales/pricing-faq.md.
Repo - Outreach & sales
Security questionnaire answers
Read this codebase and infra config and draft honest answers to a standard security questionnaire (data storage, encryption at rest and in transit, access controls, backups, logging, incident response, subprocessors, compliance). Mark every answer as "verified in code", "assumed" or "needs input". Save to sales/security-answers.md. Never claim certifications we do not have.
Repo - Outreach & sales
Follow-up emails after calls
Write 6 follow-up email templates for after sales calls: no-reply after demo, needs to talk to the team, price concern, timing not right, went with a competitor, and trial started but inactive. Each under 120 words with one clear next step. Save to sales/follow-ups.md.
- Outreach & sales
Referral program design
Design a referral program that fits our pricing and audience: who refers, what both sides get, how it is tracked, abuse rules, and the emails and in-app copy. Then outline the code changes this repo would need to support it. Save to sales/referrals.md.
Repo - Outreach & sales
ROI story for buyers
Build a simple ROI model for our product: inputs a buyer knows (team size, hours spent, current tool cost), the savings we create, and payback period. Write it as a spreadsheet-ready table and as a short paragraph a champion can paste into an internal email to get budget. Save to sales/roi.md.
- Outreach & sales
Champion enablement pack
Write what an internal champion needs to sell our product to their boss: a 5-sentence summary, a comparison against doing nothing, risks and how we handle them, a rollout plan, cost, and a draft email to their manager. Save to sales/champion-pack.md.
- Outreach & sales
Warm intro requests
For the top 10 leads in sales/leads-scored.csv, draft a short forwardable intro request: a note to a mutual connection plus a 3-sentence blurb they can forward as is. Save to sales/intros.md.
- Outreach & sales
Sales email teardown
Review every sales and outreach email template in this repo or sales/ folder. Score each for clarity, length, personalisation, proof and call to action. Rewrite the weakest 5 and explain each change. Save to sales/email-teardown.md.
- Outreach & sales
Sales FAQ for the website
Write the 25 questions prospects ask before buying, with clear answers based on the actual product in this repo: setup time, integrations, data, support, contracts, migration, team plans. Add it to the site as a FAQ section with FAQPage structured data.
Repo - Video & visuals
20 short video scripts
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.
- Video & visuals
Product demo video with Remotion
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.
Repo - Video & visuals
Record the app with Playwright
Write 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 Browser - Video & visuals
Animated explainer
Write 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/.
Repo - Video & visuals
YouTube video plan
Research 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.
Web - Video & visuals
Feature GIFs for docs and launches
For 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 Browser - Video & visuals
Thumbnails and cover images
Build 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 Browser - Video & visuals
Captions and transcripts
For 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.
Repo - Video & visuals
Talking-head video scripts
Write 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.
- Video & visuals
Data animation video
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.
Repo - Video & visuals
Onboarding video series
Write 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 Browser - Video & visuals
Repurpose a long video into clips
Take 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/.
Repo - Video & visuals
Ad creative variants
Write 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 Browser - Video & visuals
Diagrams for the docs
Find 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.
Repo - Video & visuals
Video SEO pack
For 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 - Simulated user research
Simulated usability test of the main flow
Create 5 distinct personas who match our target users (different skill levels, goals, devices, patience). For each, walk through our main flow in the running app in the browser, acting as that persona, and narrate what they expect, notice, misunderstand and give up on. Take screenshots at each confusing moment. Write a report ranking the 10 biggest usability problems with evidence and a suggested fix. Save to research/usability-sim.md. Note clearly that this is simulated and should be checked with real users.
Browser Repo - Simulated user research
Synthetic customer interviews
Build 8 realistic personas from what we know about our customers (sales/icp.md, reviews, forum posts). Run a simulated 30-minute discovery interview with each, using good interview technique: past behaviour, not hypotheticals. Write each transcript, then synthesise the patterns, surprising points and the hypotheses we should test with real people. Save to research/synthetic-interviews/.
Web - Simulated user research
First-time user walkthrough
Act as someone who has never heard of us, arriving from a Google search. Open the homepage in the browser, and in under 2 minutes of reading decide: what is this, who is it for, what does it cost, and what do I do next. Write down every moment of doubt. Then go through sign-up and onboarding as that person. Save the walkthrough with screenshots to research/first-time.md.
Browser - Simulated user research
Jobs to be done map
From the product, reviews of us and competitors, and forum discussions, write a jobs-to-be-done map: the main job, related jobs, the steps of the job, the outcomes users measure success by, and where current tools fail. Mark where our product helps and where it does not. Save to research/jtbd.md.
Web Repo - Simulated user research
Interview script for real users
Write a 30-minute customer interview script for each of our 3 personas: warm-up, past behaviour questions, the switching story, pains, and wrap-up. Avoid leading questions and anything that asks people to predict the future. Add a note-taking template and a screener survey to recruit the right people. Save to research/interview-kit.md.
- Simulated user research
Survey design and analysis plan
Design a 10-question survey for our users that tells us why they signed up, what they use most, what nearly stopped them, and what they would pay for. Include answer options, logic, and how each answer would change a decision. Then write the code to analyse a CSV export of responses. Save to research/survey/.
Repo - Simulated user research
Mine reviews for voice of customer
Collect every public review and comment about us and our top 3 competitors (G2, Capterra, app stores, Reddit, X, Product Hunt comments). Pull out the exact phrases people use for their problems, desired outcomes and frustrations. Group them and save the best 100 quotes with sources to research/voice-of-customer.md. These are for copywriting, so keep the original wording.
Web - Simulated user research
Accessibility user simulation
Test our main flows as 4 users with different needs: a screen reader user, a keyboard-only user, someone with low vision using 200% zoom, and someone with a slow connection on an old phone. Use the browser and accessibility tooling (axe, keyboard tabbing, zoom, network throttling). Report what blocks each person and the fix. Save to research/accessibility-sim.md.
Browser Repo - Simulated user research
Pricing sensitivity simulation
Create 10 buyer personas at different company sizes and budgets. For each, look at our pricing page and simulate their reaction: which plan, whether they would buy, what would make them hesitate, and the price at which it feels too expensive. Summarise into a Van Westendorp-style range and 3 pricing experiments to run for real. Save to research/pricing-sim.md.
Repo - Simulated user research
Onboarding drop-off hypotheses
Read the onboarding code and any analytics events in this repo. Map every step from sign-up to first value, count the fields, clicks and waits, and list where users are most likely to drop off and why. Propose 10 changes ranked by expected impact and effort, and the events we would need to measure each. Save to research/onboarding.md.
Repo - Simulated user research
Five-second test on key pages
For the homepage, pricing page and main feature page, take a screenshot and simulate a 5-second test with 5 different personas: what they remember, what they think the product does, and whether they would keep reading. Compare with what we want them to take away. Save findings and copy fixes to research/five-second.md.
Browser - Simulated user research
Card sort for navigation
List every page and feature in our app and site. Simulate an open card sort with 6 personas who group them in ways that make sense to them, and name the groups. Compare with our current navigation and propose a clearer information architecture. Save to research/card-sort.md.
Repo - Simulated user research
Persona profiles with evidence
Write 3 to 4 personas for our product backed by evidence: each claim linked to a review, forum post, interview note or analytics finding. Include goals, frustrations, tools used, buying role, and a day in their life. Mark anything that is a guess. Save to research/personas.md.
Web - Simulated user research
Feature request analysis
Collect every feature request we can find: GitHub issues, support notes in the repo, TODO comments, public roadmap, community posts. Deduplicate, cluster by underlying need, count requests, and estimate effort from the code. Give me a ranked list with a recommendation for each (build, decline, workaround). Save to research/feature-requests.md.
Repo Web - Simulated user research
Mental model check
Look at the words we use in the UI (buttons, menus, settings, errors) and compare them with the words users use in reviews and forums. List every term that is jargon, internal naming or ambiguous, with a plain alternative. Apply the clear wins in code and list the rest for me. Save to research/terminology.md.
Repo Web - Simulated user research
Error state empathy pass
Find every error message, empty state and failure path in this codebase. For each, simulate the user who hits it: what were they trying to do, do they know what went wrong, do they know how to fix it? Rewrite the messages that fail, and list error states that have no message at all. Apply the copy changes.
Repo - Simulated user research
Competitor user test
Run the same simulated usability test on our top competitor's public sign-up and onboarding flow in the browser (do not create accounts that break their terms; stop at walls). Compare step counts, time to value, clarity and polish against ours, with screenshots. Save to research/competitor-ux-test.md.
Browser - Simulated user research
Mobile experience review
Open our site and app in the browser at iPhone SE, iPhone 15 and a mid-range Android viewport. Go through the main flows as a mobile user on the go. List layout breaks, tiny tap targets, horizontal scroll, slow pages and anything that only works with a mouse, with screenshots. Fix the CSS issues that are safe to fix.
Browser Repo - Simulated user research
Why users churn
Write the queries (do not run against production) to find churned users and their last actions. Then, using reviews, cancellation flow copy, and support patterns, list the top 10 likely churn reasons and simulate an exit interview with a persona for each. Propose fixes and a cancellation survey. Save to research/churn.md.
Repo - Simulated user research
Research repository
Gather every research artefact in this repo (notes, personas, interviews, survey results, usability reports) into a single research/README.md: what we learned, the evidence, confidence level, open questions, and what we changed because of it. Flag findings that came from simulation so they are not mistaken for real-user evidence.
Repo - Competitor research
Map every competitor
Find every product that competes with us: direct competitors, indirect ones, open source options, spreadsheets and agencies people use instead. For each, give the URL, one-line positioning, target customer, pricing model, founded year and funding if public, and an estimated size signal. Group them and save to research/competitors.csv with a market map summary in research/competitors.md.
Web - Competitor research
Scrape competitor user flows
For our top 3 competitors, use the browser to go through their public flows: homepage, pricing, sign-up and the first screens of onboarding, as far as possible without paying or breaking their terms. Screenshot every step at desktop and mobile size, note the number of steps, fields asked, and the first "aha" moment. Save screenshots to research/flows/[competitor]/ and a side-by-side comparison to research/flows/summary.md.
Browser - Competitor research
Full teardown of one competitor
Do a complete teardown of [COMPETITOR]: positioning and messaging, target audience, features, pricing and packaging, onboarding, content and SEO strategy, social presence, reviews (what people love and hate), team and hiring signals, recent changes, and where they are weak. End with 5 ways we can win against them. Save to research/teardowns/[competitor].md.
Web Browser - Competitor research
Feature comparison matrix
Build a detailed feature matrix of us vs our top 6 competitors, using their docs, changelogs and pricing pages (cite the source for each cell). Include which plan each feature is on. Highlight features everyone has (table stakes), features only we have, and features we are missing that matter. Save to research/feature-matrix.csv and a summary to research/feature-matrix.md.
Web Repo - Competitor research
Pricing intelligence
Collect the current pricing of our top 10 competitors: plans, prices (monthly and annual), what limits each plan, free tiers, trials, and add-ons. Use the Wayback Machine to find their pricing 12 months ago and note what changed. Save to research/pricing.csv and write what the trends suggest for our own pricing in research/pricing.md.
Web - Competitor research
Competitor messaging analysis
Capture the homepage headline, subheadline, main CTA, top 3 benefits and social proof for 10 competitors. Lay them out side by side. Find the overused phrases everyone uses, the angles nobody owns, and suggest 3 positioning angles that would make us stand out. Save to research/messaging.md.
Web - Competitor research
Competitor changelog tracker
Find the changelog, release notes, blog or product update feed for each of our top 5 competitors. Summarise what each shipped in the last 6 months and what it says about their direction. Then write a script that checks these sources weekly and reports new updates. Save to research/competitor-updates.md and scripts/.
Web Repo - Competitor research
Competitor SEO strategy
For our top 3 competitors, work out their SEO strategy from public signals: sitemap sizes and sections, programmatic page patterns, blog topics and frequency, free tools, and which pages appear for our main keywords. List what we should copy, what we should ignore, and the gaps. Save to research/competitor-seo.md.
Web - Competitor research
Competitor review mining
Read 200+ public reviews of our top 3 competitors. Tally the most praised features, the most common complaints, and the reasons people switched to or away from each. Pull 30 representative quotes. Give me the 5 complaints we can turn into our marketing message. Save to research/competitor-reviews.md.
Web - Competitor research
Competitor email and onboarding capture
Plan how to sign up for competitor free trials with a test inbox to capture their onboarding emails over 2 weeks. For any competitor where I have already done this, read the emails in research/emails/ and break down the sequence: timing, subject lines, goals of each email, and what we should borrow. Save to research/competitor-emails.md.
- Competitor research
Tech stack of competitors
Find out what our competitors are built with from public signals: page source, headers, JS bundles, job posts, engineering blogs, open source repos. Note front-end, back-end, hosting, analytics, payments and AI providers. Point out anything that suggests their cost structure or limits. Save to research/competitor-stacks.md.
Web - Competitor research
Competitor hiring signals
Look at the open jobs of our top 5 competitors. What teams are they growing, what new markets or products do the job posts hint at, and what tech are they adopting? Save a short brief per competitor to research/competitor-hiring.md.
Web - Competitor research
Competitor social and community
For each top competitor, review their social accounts, community (Discord, Slack, forum), and founder presence. Note follower counts, posting frequency, what content gets engagement, and how they treat their community. Pick 3 things worth copying. Save to research/competitor-social.md.
Web - Competitor research
Battle cards
Write a one-page battle card for each of our top 5 competitors: when we win, when we lose, their strengths, their weaknesses, landmines to set in a sales call (questions that expose their gaps), how to answer "why not [competitor]?", and pricing comparison. Base it on research/ findings. Save to sales/battle-cards/.
Web - Competitor research
Open source alternatives
Find every open source project that does what we do, even partly. For each, list stars, activity, licence, maintainers, and what users complain about in issues. Decide whether each is a threat, a source of leads (people who want hosted), or a possible integration. Save to research/oss-alternatives.md.
Web - Competitor research
Adjacent markets scan
Find 10 products in adjacent categories that could add our feature and become competitors, or that we could expand into. For each explain the overlap, their user base, and the signals that they are moving toward us. Save to research/adjacent.md.
Web - Competitor research
Competitor ad copy
Find the ads our competitors run, using public ad libraries (Meta Ad Library, LinkedIn Ad Library, Google Ads Transparency Center). Capture the copy, creative format and landing pages. Summarise the angles they test and how long ads have been running (long-running ads usually work). Save to research/competitor-ads.md.
Web Browser - Competitor research
Competitor landing page screenshots
Take full-page screenshots of the homepage, pricing page and top 3 landing pages of 8 competitors at desktop and mobile width. Save them to research/screenshots/ with a date in the filename, and write a short note on any layout or design ideas worth borrowing.
Browser - Competitor research
Where competitors get traffic
Using public signals (their content, social accounts, communities, directories they appear in, newsletters that mention them, partner pages), estimate where each top competitor gets its traffic and customers. Find 10 channels they use that we do not. Save to research/competitor-channels.md.
Web - Competitor research
Quarterly market report
Write a quarterly market report on our category: major launches, funding, pricing changes, acquisitions, notable shutdowns, trends in what customers ask for, and what it means for our roadmap. Use research/ files plus fresh web research. Save to research/market-[quarter].md.
Web - Landing pages & conversion
Homepage copy rewrite
Read our homepage and product. Write 3 alternative versions of the hero (headline, subheadline, CTA, supporting line) based on different angles: outcome, pain, and audience. Then rewrite the full homepage in the strongest angle using voice-of-customer phrases from research/ if available. Make the change in a branch and save the alternatives to growth/homepage-copy.md.
Repo - Landing pages & conversion
Conversion audit of the funnel
Walk through our funnel in the browser from homepage to paid: landing, pricing, sign-up, onboarding, upgrade. At each step list friction (extra fields, unclear copy, slow loads, distractions, missing trust signals) with screenshots, and score it. Give me the 15 highest-impact fixes ranked by impact and effort. Save to growth/cro-audit.md.
Browser Repo - Landing pages & conversion
A/B test backlog
Write 20 A/B test ideas for our site and app, each with the hypothesis, the change, the metric, the minimum sample size needed at our likely traffic, and expected impact. Rank them with ICE scores. Then implement the top one behind a feature flag if this repo has a flag system. Save to growth/ab-tests.md.
Repo - Landing pages & conversion
Landing page for each persona
Using research/personas.md (or infer personas from the product), build a dedicated landing page for each persona in this codebase: their headline, their pains, the features they care about, a relevant proof point, and a CTA. Reuse existing components and set unique metadata for each.
Repo - Landing pages & conversion
Pricing page redesign
Review our pricing page against the best SaaS pricing pages. Propose a clearer structure: plan names, the recommended plan, feature comparison table, annual toggle, FAQ, guarantees and trust signals. Implement it in a branch using existing components, keeping current prices unless I said otherwise.
Repo - Landing pages & conversion
Social proof inventory
Find every piece of social proof we have or could get: testimonials, logos, user counts, GitHub stars, reviews, press, case studies, awards. Then add the right proof next to each major decision point in the funnel (hero, pricing, sign-up). List what is missing and how to get it.
Repo Web - Landing pages & conversion
Sign-up form diet
Find every field and step in our sign-up and onboarding forms. For each, decide if it is needed now, can be asked later, or can be inferred. Remove or defer what is safe, add social sign-in if it exists in the stack, improve validation messages, and make sure the form works with password managers and autofill.
Repo - Landing pages & conversion
Exit intent and retention offers
Design a few non-annoying ways to recover leaving visitors: an exit-intent offer on pricing, a "send me this later" email option, a lighter free plan or trial extension. Write the copy and implement the one that best fits our product, with a way to turn it off.
Repo - Landing pages & conversion
Feature pages that sell
For each main feature, check whether we have a dedicated page. Write or improve each one: the problem it solves, how it works with a screenshot or GIF, a use case, a mini FAQ, and a CTA. Implement them in the codebase with unique metadata.
Repo - Landing pages & conversion
Microcopy pass
Review every button, label, tooltip, placeholder and confirmation message in the app. Replace vague labels ("Submit", "OK", "Click here") with specific actions, make sure tone is consistent, and fix any truncated or awkward copy. Apply the changes and list them.
Repo - Landing pages & conversion
Upgrade prompts in the app
Find where free users hit limits or would benefit from paid features. Design upgrade prompts that show up at those moments, explain the value in context, and never block work without warning. Implement them using existing UI patterns, and add events so we can measure them.
Repo - Landing pages & conversion
Trust and security page
Write a trust page covering how we handle data, security practices, uptime, privacy, subprocessors and how to contact us about security, based on what the code and infra actually do. Add it to the site and link it from the footer, pricing and sign-up. Mark anything I need to confirm.
Repo - Landing pages & conversion
Speed up the landing pages
Measure the load time of our top 5 landing pages. Find the heaviest assets and scripts, defer non-critical third-party tags, compress images, and preload the hero. Report the before/after numbers and the changes.
Repo Browser - Landing pages & conversion
Use case pages
List 10 concrete use cases for our product from reviews, docs and support. For each build a page with a specific scenario, the workflow step by step, a template or example output, and a CTA. Target "[use case] tool" or "how to [use case]" keywords.
Repo - Landing pages & conversion
Free trial to paid sequence
Map what a trial user experiences from day 1 to the end of the trial: emails, in-app messages, limits and nudges. Find gaps where they get no help, and write the in-app messages and emails to fill them, each tied to a specific action that predicts conversion.
Repo - Landing pages & conversion
Headline testing bank
Write 50 headline variations for our homepage in 10 styles (outcome, how-to, question, number, contrarian, before/after, audience call-out, speed, comparison, story). Score each for clarity and specificity, and pick the 5 to test first. Save to growth/headlines.md.
- Landing pages & conversion
CTA audit
Find every call to action across the site and app. Check they are consistent, specific about what happens next, visible above the fold where needed, and not competing with each other on the same screen. Fix the weak ones and output a table of changes.
Repo - Landing pages & conversion
Demo or sandbox mode
Design a way for visitors to try the product without signing up: a read-only demo account, a sandbox with sample data, or an interactive tour. Outline the code changes, the risks (abuse, cost) and how to limit them, then build the simplest safe version in a branch.
Repo - Landing pages & conversion
Comparison table on the homepage
Write an honest "us vs the old way vs alternatives" comparison block for the homepage that answers why someone should choose us. Keep it to 6 to 8 rows of things buyers care about. Implement it with existing components, responsive on mobile.
Repo - Landing pages & conversion
Analytics events for the funnel
Check which funnel steps we track with analytics events in this codebase. Add missing events for each key step (viewed pricing, started sign-up, completed onboarding step, first key action, upgrade clicked) with consistent names and properties, and document them in docs/analytics-events.md.
Repo - Email & lifecycle
Welcome and onboarding sequence
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.
Repo - Email & lifecycle
Email templates in code
Build 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.
Repo - Email & lifecycle
Re-engagement campaign
Write 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.
- Email & lifecycle
Newsletter content bank
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.
Web - Email & lifecycle
Transactional email audit
Find 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.
Repo - Email & lifecycle
Launch announcement email
Write 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.
Repo - Email & lifecycle
Deliverability check
Check 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 Repo - Email & lifecycle
Trial ending sequence
Write 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.
- Email & lifecycle
Cancellation and win-back flow
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.
- Email & lifecycle
Segmented emails by persona
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.
- Email & lifecycle
Lead magnet delivery sequence
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.
- Email & lifecycle
Subject line library
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.
- Email & lifecycle
Customer milestone emails
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).
Repo - Email & lifecycle
Changelog digest automation
Write 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.
Repo - Email & lifecycle
Cold newsletter growth plan
Write 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 - Product & UX
UI polish pass
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 Repo - Product & UX
Empty states that teach
Find 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.
Repo - Product & UX
Onboarding checklist
Design 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.
Repo - Product & UX
Dark mode
Add 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 Browser - Product & UX
Keyboard shortcuts and command palette
Add 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.
Repo - Product & UX
Write the spec for the next feature
Take 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.
Repo - Product & UX
Prototype a feature in a branch
Build 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.
Repo - Product & UX
Settings page cleanup
Review 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.
Repo - Product & UX
Loading and skeleton states
Find 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 Browser - Product & UX
Form validation everywhere
Review 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.
Repo - Product & UX
Product roadmap draft
Based 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.
Repo - Product & UX
Import and export
Check 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.
Repo - Product & UX
Notifications review
List 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.
Repo - Product & UX
Templates and sample data
Add 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.
Repo - Product & UX
Search inside the app
Add 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.
Repo - Product & UX
Responsive layout fixes
Check 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 Repo - Product & UX
Public roadmap and changelog pages
Add 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.
Repo - Product & UX
In-app feedback widget
Add 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.
Repo - Product & UX
Design system audit
Inventory 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.
Repo - Product & UX
Delight details
Find 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 - Code quality
Raise test coverage on critical paths
Find the code paths that handle money, auth, data writes and the main user flow. Measure current test coverage for them. Write meaningful tests (behaviour, edge cases, failures, not just lines) until each critical module is well covered. Run the full suite, fix flaky tests you find, and report coverage before and after.
Repo - Code quality
End-to-end tests for the main flows
Write Playwright end-to-end tests for our 5 most important user flows (sign-up, core action, upgrade, settings, and one more you think matters). Use stable selectors, seed data, and run them headless. Add a script and CI step to run them. Report anything that failed as a bug list.
Repo Browser - Code quality
Dead code removal
Find unused files, exports, components, routes, dependencies, feature flags that are always on, and commented-out code. Verify each is truly unused (search for dynamic references too). Remove them in small commits, run the build and tests after each, and list what was removed.
Repo - Code quality
Dependency upgrades
List outdated dependencies with their current and latest versions and changelogs for breaking changes. Upgrade the safe ones (patch and minor) first, run the build and tests, then tackle major upgrades one at a time with the migration steps from their docs. Stop and report any that need a decision.
Repo Web - Code quality
Strict TypeScript
Turn on stricter TypeScript settings one at a time (strict, noUncheckedIndexedAccess, noImplicitOverride). Fix the resulting errors properly rather than with any or ts-ignore. Commit after each setting with the build passing. Report anything you had to leave and why.
Repo - Code quality
Refactor the worst file
Find the file with the most complexity, length and churn in git history. Refactor it into smaller, well-named units without changing behaviour. Add tests first that pin current behaviour, then refactor, then run them again. Explain the new structure in the PR description.
Repo - Code quality
Fix every lint warning
Run the linter and type checker. Fix every warning and error properly, grouping fixes by rule in separate commits. Where a rule is wrong for this codebase, propose disabling it with a reason instead of sprinkling ignores.
Repo - Code quality
Error handling review
Find every try/catch, promise without a catch, empty catch block, and API call without error handling. Make errors surface properly: log with context, show users a useful message, and never swallow failures silently. Add tests for the main failure paths.
Repo - Code quality
TODO and FIXME sweep
Find every TODO, FIXME, HACK and XXX comment. For each, decide: fix it now if it is small and safe, turn it into a GitHub issue description if it is real work, or delete it if it is stale. Do the small fixes, and save the issue drafts to docs/todo-issues.md.
Repo - Code quality
Database query review
Find every database query in the codebase. Look for N+1 queries, missing indexes on filtered or joined columns, unbounded selects, queries in loops and missing pagination. Fix what is safe, write migrations for new indexes (do not run them on production), and report the rest.
Repo - Code quality
API contract tests
Document every API endpoint with its inputs, outputs and errors (OpenAPI if possible). Add request validation where it is missing and contract tests that check each endpoint's response shape. Generate typed clients if the stack supports it.
Repo - Code quality
Consistent naming and structure
Review the folder structure and naming conventions. Find inconsistencies (mixed casing, duplicate helpers, components in the wrong place, utils grab-bags). Propose a clean structure, then make the moves in small commits with imports updated and the build passing.
Repo - Code quality
Remove duplicated logic
Find duplicated or near-duplicated code (copy-pasted functions, components with small differences, repeated validation). Consolidate them into shared, tested helpers where it makes the code simpler, not more abstract. List each consolidation.
Repo - Code quality
Make the build faster
Measure build, test and dev-server start times. Find what is slow (huge dependencies, unnecessary transpilation, missing caching, slow tests) and fix it. Report the before and after timings.
Repo - Code quality
CI pipeline setup
Set up or improve CI for this repo: install with caching, lint, type check, unit tests, build, and end-to-end tests on pull requests, with clear job names. Keep it fast. Add a status badge to the README.
Repo - Code quality
Write a CLAUDE.md
Write or improve the CLAUDE.md for this repo: how to install, run, test and build; the architecture in a few paragraphs; conventions and gotchas; where key things live; and what not to touch. Keep it short and accurate, verified by actually running the commands.
Repo - Code quality
Fix flaky tests
Run the test suite 10 times and record which tests fail intermittently. For each flaky test, find the root cause (timing, shared state, order dependence, network, randomness) and fix it properly rather than adding retries. Report each cause and fix.
Repo - Code quality
Migrate off a deprecated API
Search the codebase for deprecated APIs, libraries and patterns (check deprecation warnings in build output and library changelogs). Pick the most important one and migrate every usage, with tests passing. List the remaining deprecations.
Repo Web - Code quality
Logging and observability
Review logging across the app. Add structured logs with request IDs at key points (requests, background jobs, external calls, errors), remove noisy or sensitive logs, and make sure errors are reported to the error tracker if one is configured. Document how to debug a failed request.
Repo - Code quality
Fix open GitHub issues
List open bug issues for this repo. Pick the 5 that look smallest and clearest. For each, reproduce it, write a failing test, fix it, and prepare a commit message that references the issue. Stop and summarise any that turned out to be bigger than expected.
Repo - Security & performance
Security review of the codebase
Do a security review of this codebase: authentication and session handling, authorisation checks on every endpoint (can user A read user B's data?), input validation, SQL and command injection, XSS, CSRF, file uploads, SSRF, secrets in code, and dependency vulnerabilities. Rank findings by severity with the exact file and line, and fix the clear-cut ones in a branch.
Repo - Security & performance
Secrets scan
Scan the repo and its full git history for committed secrets: API keys, tokens, passwords, private keys and connection strings. List each with the file, commit and whether it looks live. Do not print full secret values. Recommend which to rotate and add a pre-commit secret scanner.
Repo - Security & performance
Dependency vulnerability fixes
Run the package manager's audit and check for known vulnerabilities in dependencies. Upgrade to patched versions where safe, verify the build and tests, and explain any vulnerability that does not affect us and why. Add automated dependency updates if not set up.
Repo - Security & performance
Authorisation test suite
List every endpoint and server action that reads or changes data. Write tests that check a logged-out user, a user from another account, and a user without the right role are all refused. Fix any endpoint that fails.
Repo - Security & performance
Security headers
Check and add security headers: Content-Security-Policy (start in report-only), Strict-Transport-Security, X-Content-Type-Options, Referrer-Policy, Permissions-Policy and frame-ancestors. Make sure nothing on the site breaks, and document the policy.
Repo - Security & performance
Rate limiting and abuse
Find endpoints that could be abused: login, sign-up, password reset, contact forms, expensive API calls, anything that sends email or costs money (like AI calls). Add rate limiting and basic abuse protection using what the stack already supports. Document the limits.
Repo - Security & performance
Bundle size diet
Analyse the JavaScript bundles. Find the biggest dependencies and code that ships to the client unnecessarily. Replace heavy libraries with lighter ones or native APIs, lazy-load routes and heavy components, and remove unused code. Report the size before and after for each main page.
Repo - Security & performance
Load test
Write a load test (k6, autocannon or similar) for our main API endpoints and pages against a local or staging environment only. Ramp up traffic, find where response times degrade and what breaks first, and suggest fixes. Never point it at production.
Repo - Security & performance
Caching strategy
Review what is cached and what is not: HTTP cache headers, CDN, static generation, server-side caches, and database query caching. Find expensive repeated work that could be cached safely, implement the clear wins, and document invalidation for each.
Repo - Security & performance
Backup and restore check
Find out how our data is backed up from the infra config and docs. Write a runbook for restoring from backup, and a script to test a restore into a scratch database. Flag any data that is not backed up at all.
Repo - Security & performance
Privacy and data audit
Map every piece of personal data we collect, where it is stored, who can access it, which third parties receive it, and how long we keep it. Check the privacy policy matches reality. Find what we collect but do not need. Save to docs/data-map.md and fix the clear issues.
Repo - Security & performance
Cookie and tracking consent
List every cookie, local storage key, analytics tag and third-party script. Check whether a consent banner is legally needed for our audience, and if so implement one that blocks non-essential scripts until consent. Keep it simple and fast.
Repo Web - Security & performance
Incident runbooks
Write runbooks for the 8 most likely incidents for this app: site down, database full, payment failures, email not sending, third-party API outage, a leaked key, a bad deploy, and a traffic spike. Each with how to detect, diagnose, fix and communicate. Save to docs/runbooks/.
Repo - Security & performance
Uptime and alerting setup
Add a health check endpoint that checks the app and its key dependencies. Write the config for uptime monitoring and alerts for error rate and latency with whatever tools we already use, and document who gets alerted and how.
Repo - Security & performance
Image and asset optimisation
Find every image, font and video in the repo. Convert images to modern formats at sensible sizes, add responsive srcset, subset fonts, self-host where it helps, and lazy-load below the fold. Report bytes saved.
Repo - Security & performance
Slow endpoint hunt
Add timing around API handlers in a local run, seed realistic data volumes, and find the slowest 10 endpoints. Profile each, fix the causes (queries, serial awaits, heavy computation), and report before and after timings.
Repo - Security & performance
Cloud cost review
Read our infra config, deployment files and any usage data in the repo. List what we pay for and estimate where money is wasted: oversized instances, unused resources, chatty logging, missing caching, expensive API calls including AI. Propose savings with estimated amounts. Save to docs/cost-review.md.
Repo - Security & performance
Disaster recovery drill plan
Write a disaster recovery plan: what our recovery time and data loss targets should be, what we would do if our main region or provider went down, and a step-by-step drill to test it once a quarter. Save to docs/disaster-recovery.md.
Repo - Security & performance
Accessibility audit and fixes
Run axe or Lighthouse accessibility checks on every page and audit by hand: keyboard navigation, focus order, labels, contrast, alt text, ARIA misuse and screen reader announcements. Fix what you can and write docs/accessibility.md listing remaining issues by WCAG criterion.
Repo Browser - Security & performance
Threat model
Write a threat model for this application: assets, entry points, trust boundaries, and the top 15 threats using STRIDE, each with likelihood, impact and current mitigations. Recommend the 5 most valuable fixes. Save to docs/threat-model.md.
Repo - Docs, support & ops
Help centre from the codebase
Read the app's features, settings and error messages. Write a help centre: getting started, one article per feature, troubleshooting for every error users can hit, and account and billing questions. Plain language, short steps, a screenshot list for each. Save to docs/help/ in a structure ready to publish.
Repo - Docs, support & ops
Support reply macros
Write 30 support reply templates for the questions we get most (or are most likely to get, based on the product): login issues, billing, refunds, bugs, feature requests, how-to questions, cancellations. Friendly, short, with placeholders and a link to the right help article. Save to docs/support-macros.md.
Repo - Docs, support & ops
API documentation
Document our public API from the code: authentication, every endpoint with parameters, example requests in curl and JavaScript and Python, responses, errors, rate limits and pagination. Generate an OpenAPI spec if we do not have one and check it against the code.
Repo - Docs, support & ops
README that sells and explains
Rewrite the README: what it is in one line, a screenshot or GIF, quick start in under 5 commands, key features, configuration, how to contribute, and licence. Verify every command works by running it.
Repo - Docs, support & ops
Metrics dashboard queries
Define the 10 metrics that matter for this business (activation rate, retention by cohort, MRR, churn, conversion by channel and so on) with exact definitions. Write the SQL or analytics queries for each against our schema. Do not run against production; save to docs/metrics.md for me to plug in.
Repo - Docs, support & ops
Weekly founder report template
Build a weekly report template and a script that fills in what it can automatically (commits shipped, issues closed, analytics numbers if an API key is available). Sections: metrics, wins, problems, learnings, next week priorities. Save to ops/weekly-report/.
Repo - Docs, support & ops
Investor update draft
Draft this month's investor or advisor update from what you can find: shipped features from git, metrics from docs/metrics.md or my notes, and research findings. Sections: highlights, numbers, lowlights, asks. Leave clear placeholders for numbers you cannot verify. Save to ops/investor-update.md.
Repo - Docs, support & ops
Onboarding doc for a new hire
Write an onboarding guide for a new developer or contractor: how to set up the project, architecture overview, how we deploy, where secrets live (not the secrets themselves), conventions, and a first-week task list with good first issues. Test the setup steps in a clean checkout.
Repo - Docs, support & ops
Architecture decision records
Read the codebase and git history to identify the 10 most important technical decisions (framework, database, auth, hosting, key libraries). Write a short ADR for each: context, decision, alternatives, and consequences, inferred from the code and commits. Save to docs/adr/.
Repo - Docs, support & ops
Pricing experiment plan
Review our pricing, costs per user (from infra and API usage in the code), competitor prices in research/pricing.csv, and conversion data if available. Propose 3 pricing changes with expected impact and risk, and how to test each safely. Save to ops/pricing-plan.md.
Repo Web - Docs, support & ops
Unit economics model
Build a simple unit economics model: cost to serve one user per month (hosting, AI, email, payments fees from our code and config), price, gross margin, and break-even user counts. Make it a spreadsheet-ready CSV with formulas described. Save to ops/unit-economics.md.
Repo - Docs, support & ops
Legal pages review
Read our terms of service, privacy policy and cookie policy. Compare them with what the product actually does (data collected, third parties, AI use, payments). List mismatches and missing sections. Draft updated text for review by a lawyer, clearly marked as a draft, not legal advice.
Repo - Docs, support & ops
Tidy the project board
Read all open GitHub issues. Close duplicates and stale ones (with a polite note drafted, not posted), add labels and clear titles, group related issues, and write a prioritised list of the top 15 with effort estimates. Save the plan to ops/issue-triage.md before making any changes.
Repo - Docs, support & ops
FAQ from support patterns
Look for common questions in our issues, discussions, support macros and community posts. Write a public FAQ page with the 25 best questions and answers, add it to the site with FAQPage structured data, and link it from the footer and pricing page.
Repo Web - Docs, support & ops
Grant and credit applications
Find startup programs, cloud credits, AI API credits, grants and accelerator programs we could apply to in the next 3 months (cloud providers, AI labs, regional grants, open source funds). List eligibility, deadline and value. Draft the application answers for the top 3. Save to ops/grants.md.
Web - Docs, support & ops
Tool and subscription audit
List every service this repo depends on (package.json, env var names, config files, integrations). For each, note what it is used for, whether it looks still used, and a cheaper or free alternative where one exists. Save to ops/tools-audit.md so I can cancel what we do not need.
Repo - Docs, support & ops
Personal to-do triage
Read my notes in ops/todo.md (or any TODO or notes files in this repo). Group the tasks, mark which ones Claude Code could do for me without supervision, which need me, and which can be dropped. Then do the first 3 that you can do safely, and report back.
Repo - Docs, support & ops
Meeting and call prep
For each upcoming call I list in ops/calls.md (name, company, purpose), research the person and company from public sources and write a one-page brief: background, recent news, likely priorities, 5 smart questions, and what I want from the call.
Web - Docs, support & ops
Translate the product
Set up internationalisation if missing, extract all user-facing strings, and translate them into the 3 languages our traffic or market suggests. Keep strings natural, not literal. Check layouts in the browser with longer translations, and list strings that need a native speaker to review.
Repo Browser - Docs, support & ops
Plan tomorrow's overnight run
Look at everything in this repo and my notes: open issues, docs/roadmap.md, growth/, research/, ops/todo.md. Write a ranked queue of the 10 best tasks for an unattended overnight Claude Code run tomorrow, each as a complete, self-contained prompt with the files to read, the output to produce, and a clear "done" check. Save to ops/overnight-queue.md.
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.
Questions
What are spare compute prompts?
They are long, self-contained tasks you can hand to Claude Code when your plan or machine would otherwise sit idle: overnight, over a weekend, or while you are in meetings. Each one names the files to read, the output to produce and where to save it, so you can start it, walk away and review the result later.
How do I run a prompt overnight with Claude Code?
Open Claude Code in your project and paste the prompt, or run it headless with claude -p "<prompt>". Start the session on a new git branch or worktree so every change is easy to review or throw away, and allow only the tools the task needs. Claude Code on the web runs sessions in a cloud sandbox, so you can close your laptop and check back in the morning.
Is it safe to let Claude Code run unattended?
Keep the blast radius small. Run on a branch or in a sandbox, never point a prompt at production data, keep API keys with spending power out of the environment, and review the diff before you merge. These prompts ask Claude to research, draft and change code, and to save its work to files. None of them should send email, post publicly or spend money without you; overnight mode on this page adds that rule to every prompt you copy.
What do the Web, Browser and Repo labels mean?
Web prompts need web search or fetch, which Claude Code has built in. Browser prompts click through real pages and take screenshots, so they need a browser tool such as the Playwright MCP server or Claude in Chrome. Repo prompts read or change your codebase, so run them inside your project folder.
Can I queue several prompts for one night?
Yes. Save each prompt to its own file and loop over them with claude -p, writing each run to a log file, or start several cloud sessions at once. The last prompt in the Docs, support & ops category writes tomorrow night's queue for you.
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.