Prompt library

Topic: [topic]
Audience: [who]
Do not invent statistics, quotes, or product UI paths.
1) Restate the question and likely search intent.
2) List what you know vs what you need sources for.
3) Produce an outline with H2/H3s.
4) Flag claims that must be verified before publishing.
5) Suggest 3 internal links from usebot.net if relevant.

Create a routine spec for: [recurring job]
Include: purpose (1 sentence), inputs checklist, numbered steps, output contract (format/length/tone), human review gate, and failure modes.
If an input is missing, pause instead of inventing data.

Review this change as a careful teammate.
Summarize intent, list risks, note missing tests, and call out any secret or permission issues.
Do not approve language if you did not see the diff. Ask for the missing file list instead.

Goal: [one paragraph]
Out of scope: [list]
Acceptance checks: [build/tests/review]
Deliverable: a branch or PR description I can review.
Stop and ask if requirements are ambiguous. Do not deploy.

Using only the notes I provide, draft a weekly editorial brief.
Sections: movers, proposed updates, one new outline, internal links, risks.
No keyword stuffing. No fabricated traffic causes.

Rewrite the following so it never confuses Cursor’s Grok Bot with xAI’s Grok chatbot.
Keep the tone expert and friendly. Preserve facts. Remove hype.