26 copy-paste prompts with their inputs, output rules, and a verification step each. Paste into the AI tool you already use. Every prompt says what it will not do — invent testimonials, fake metrics, skip disclosures — so the failure modes stay visible.
Use when: You have a possible niche but no page ideas.
Inputs to provide: Reader, problem, and any forum/support/documentation notes.
Generate 20 plain-language reader questions for [reader] facing [problem]. Group by learn, compare, choose, fix, and maintain. Mark claims that require expert or official sources. Do not call these high-volume keywords without evidence.
Check before acting: Are these questions specific enough to answer without pretending expertise?
Use when: A draft contains a factual statement.
Inputs to provide: Claim and source links.
Check this claim only against the supplied sources: [claim and sources]. Return supported, contradicted, incomplete, or unsupported. Quote the relevant sentence and state the source date. Do not invent a citation.
Check before acting: Open the source yourself and confirm it says what the draft claims.
Use when: You are choosing the next article.
Inputs to provide: Reader question and site thesis.
Create a reader-first brief for [question] using this site thesis: [paste]. Return direct answer, reader situation, outline, evidence needed, limits, honest affiliate relevance, and one practical next step. Reject any angle requiring a fabricated experience.
Check before acting: Does the page remain useful with affiliate links removed?
Use when: You add a recommendation or affiliate link.
Inputs to provide: Page draft, program terms, and your relationship.
Identify material connections and recommend clear, plain-language disclosure placement near the recommendation. Separate FTC-style general disclosure needs from program-specific language. Flag items for policy or legal review. Do not provide legal advice.
Check before acting: Is the relationship visible before the reader decides to click?
Use when: You want to work but cannot face the giant version of the task.
Inputs to provide: Current project and available minutes.
My project is [project]. I have [minutes] and low energy. Give one action that produces a saved artifact, one optional next action, and a stopping point. Do not add a new tool or project.
Check before acting: Can I start this before another tab steals me?
Use when: You have a week of notes or metrics.
Inputs to provide: Pages, feedback, clicks, income/expense notes, time used.
Summarize this week without overclaiming causation. Return what changed, what is unknown, one reader hypothesis, one page improvement, one experiment, and one task to drop. Do not promise revenue outcomes.
Check before acting: Which observation is evidence and which is a story you are telling yourself?
Use when: You need to compare one topic without overthinking.
Inputs to provide: Topic and reader.
Score [topic] for reader pain, specificity, learning runway, content depth, safety risk, product fit, and ethical comfort. Label each score evidence, hypothesis, or unknown.
Check before acting: Would you be comfortable helping this reader without a commission?
Use when: You are considering an affiliate program.
Inputs to provide: Official program URL.
Extract eligibility, qualifying action, exclusions, payment timing, promotional restrictions, disclosure language, and termination rules from this official page: [URL]. Quote each item and state the date checked. Mark missing terms unknown.
Check before acting: Did you read the official terms, not a roundup blog?
Use when: Your site has begun to sprawl in your head.
Inputs to provide: Reader, problem, page ideas, values.
Write a one-page thesis with reader, stuck moment, better decision, three page types, non-goals, trust practices, disclosure approach, first five pages, and a 30-day definition of done.
Check before acting: Can this thesis reject an off-topic idea?
Use when: You are stuck choosing tools.
Inputs to provide: Budget, skill, time, requirements.
Compare [options] for setup effort, editing ease, ownership, backup/export, recurring cost, basic performance, and learning curve. Recommend the simplest option that can publish and revise useful pages. Do not claim ranking guarantees.
Check before acting: Can you edit a typo without a rescue mission?
Use when: You need About, Contact, Disclosure, or Editorial Policy text.
Inputs to provide: Your real facts and practices.
Draft a plain-language [page type] from these facts: [paste]. Use placeholders rather than inventing credentials, testing, or legal language. State how recommendations and commissions work if relevant.
Check before acting: Does every claim describe your real practice?
Use when: You have a question but not a format.
Inputs to provide: Reader question.
Choose review, comparison, tutorial, or resource for [question]. Explain the reader decision, the evidence required, the author limits, and a five-section outline.
Check before acting: Does the format fit the question rather than the commission?
Use when: A reader must choose between options.
Inputs to provide: Options and evidence packet.
Build a comparison matrix from these verified sources: [paste]. Include criteria, who each option suits, limits, source/date, and unknowns. Do not select a winner without stated reader priorities.
Check before acting: Are all facts sourced and dates visible?
Use when: Your page gives instructions.
Inputs to provide: Draft and audience.
Audit this tutorial for unsafe, incomplete, or overconfident instructions. Identify steps requiring professional help, current documentation, or safety warnings. Rewrite only supported sections.
Check before acting: Could a novice follow this without hidden assumptions?
Use when: Your introduction wanders.
Inputs to provide: Draft opening and reader question.
Rewrite the opening to answer [question] in the first 120 words, then state who the answer applies to, key exceptions, and what the rest of the page will help decide. Preserve uncertainty.
Check before acting: Does the answer arrive before the backstory?
Use when: You have not personally tested a product.
Inputs to provide: Draft claim and actual experience.
Rewrite this passage so it clearly separates what I personally used, what official documentation states, and what remains unknown. Remove implied first-hand experience.
Check before acting: Could a reader mistake research for testing?
Use when: An AI draft sounds like everybody else’s.
Inputs to provide: Draft, viewpoint, source packet.
Identify generic phrases, unsupported filler, repeated ideas, and missing decision criteria. Suggest revisions that use my actual viewpoint and the supplied sources. Do not add new facts.
Check before acting: Did the revision gain information, not just length?
Use when: You publish a new page.
Inputs to provide: New page and existing page titles.
Suggest up to five contextual internal links that answer the reader’s natural next question. Explain why each link helps. Do not force links or recommend links to unrelated pages.
Check before acting: Would you click the link at that exact moment?
Use when: You have several existing pages.
Inputs to provide: Page list, notes, metrics if available.
Rank pages by reader-value opportunity, stale-fact risk, disclosure risk, and ease of improvement. Recommend one update with a before/after outline. Do not infer causation from sparse metrics.
Check before acting: Does the priority improve reader trust?
Use when: You are considering posting in a community.
Inputs to provide: Community rules and the question.
Draft a helpful standalone answer to [question] that follows these rules: [paste]. Mention my resource only if it fully answers a need and disclosure is appropriate. No engagement bait, copied replies, or false urgency.
Check before acting: Would this still be welcome without a link?
Use when: You start a small email list.
Inputs to provide: Reader promise and disclosure practice.
Write a concise welcome email that sets expectations, states what readers will receive, explains unsubscribe options, and transparently notes affiliate relationships when relevant. Avoid income claims.
Check before acting: Does it respect attention and consent?
Use when: You begin spending on the project.
Inputs to provide: Current tools and purchases.
Create a simple income-and-expense tracking template with date, vendor/program, purpose, amount, category, receipt location, and notes. Include a reminder to check local tax requirements. Do not provide tax advice.
Check before acting: Can you find the supporting record later?
Use when: A page is almost ready.
Inputs to provide: Page draft and source list.
Audit this page for direct answer, factual sourcing, author limits, disclosure placement, reader usefulness without links, accessible structure, and next-step clarity. Return pass/fix/unknown for each category.
Check before acting: Fix the highest-trust risk first.
Use when: You avoided the project for a while.
Inputs to provide: Last completed action and current energy.
Create a restart plan with one 15-minute action, one saved artifact, and one optional next step. Do not include catch-up work, self-judgment, a new tool, or a new project.
Check before acting: Does it make starting lighter?
Use when: You want to expand.
Inputs to provide: Site thesis, pages, feedback, records, time.
Recommend deepen, improve, or expand. Use only the supplied evidence. State uncertainties, risks, a 30-day experiment, and explicit reasons to delay expansion.
Check before acting: Is expansion earned by useful evidence?
Use when: You are about to buy a course, join a program, or act on a pitch.
Inputs to provide: The claim, the promise, and any proof offered.
Run this pitch through a hype filter. For each of these signals, say present or absent and quote the line that triggers it: income screenshots without disclosure, fail-proof or guaranteed outcomes, manufactured urgency, fake-regret or FOMO wording, "passive income forever" framing, and pay-to-play secrets. Then give one-line honest alternative phrasing for each signal that is present, and a single sentence on what the offer would need to show to be trustworthy. Do not add income claims or timelines.
Check before acting: Would this advice still sound honest if every deadline were removed and no screenshot were attached?