Prompt library
Every prompt here is written for one job, states what it needs from you, and is instructed to say when data is unavailable rather than estimate it. Read the worked example before you run it.
Rewrite a page passage by passage so an assistant can quote a correct, self-contained answer from it, plus a straight read on whether page edits alone can change anything.
Edit an AI first draft into publishable prose by cutting throat-clearing and machine rhythm, and flagging every claim that needs a fact instead of inventing one.
Write an X vs Y comparison page from dated, observed competitor facts, including the cases where the competitor is the better choice and a ledger of what could not be verified.
Sort an existing set of pages into keep, update, consolidate or retire, with a reason, a next action, and a named destination for every URL that comes down.
Decide what to change on a page that has lost or never gained traffic - one diagnosis, the change list it implies, and an explicit list of what to leave alone.
Draft an FAQ section from questions readers have actually been recorded asking, plus FAQPage JSON-LD whose answers match the visible text word for word.
Produce an internal link plan for one page: anchor text, the sentence each link belongs in, and a flag for any pages that overlap so heavily they should be merged instead.
Draft landing page copy that answers one search query in the first screen and then earns one action, using only the facts you supply.
Sort a keyword list by what the searcher wants and what page type each implies, reading intent from the results that currently rank and marking it unverified where nobody looked.
Turn a topic and its search intent into a section-by-section outline where every heading states what it proves, with unequal word budgets and an explicit cut list.
Turn a content brief into a full first draft that marks where first-hand evidence is needed instead of inventing statistics, customer names, or study citations.
Turn one target query into the brief a writer can work from - the page's argument, the questions it must answer, the evidence each section needs, and what is out of scope.
Group a raw keyword list into topic clusters you can actually build pages around, with one page intent per cluster.
Read the pages actually ranking for a query, get the requirements a page must meet to belong there, and a straight verdict on whether your site should target it at all.
Write title tags and meta descriptions for a batch of pages, checked for length, uniqueness across the batch, and accuracy to what each page actually contains.
Turn a subject into a hierarchy of pillar and supporting pages with internal links, an explicit out-of-scope list, and a page count that fits what your team can publish.
About this library
No. Every prompt on this page is readable and copyable as published. An account is only relevant if you want a GenGrowth agent to run this work for you instead.
A prompt is one instruction you paste into a model to get one deliverable. A skill is a whole operating procedure an agent follows repeatedly, and it usually consumes several prompts' worth of work as steps. Prompts are for a task; skills are for a loop.
Yes, and you should. The variables mark the parts that always change; the steps and quality checks are the parts worth keeping, because they are what stop the model from inventing data.
Prompts are revised when the underlying practice changes or when a run surfaces a failure the prompt should have caught. Each page shows when it was last updated.
GenGrowth