Reference · paste & adapt
Starter prompts grouped by goal. Work in any major chat / coding / cloud-agent tool. Pick the closest, paste into your tool of choice, fill the brackets, send.
You'll get: An email draft + a subject line + two alternatives
Here are my rough notes for an email. Produce three things: 1) A clean version in a warm but direct tone — no corporate puffery. 2) A one-sentence subject line. 3) Two alternatives — shorter and more formal — so I can pick. Ask one clarifying question if anything is unclear. Notes: [paste here]
You'll get: TL;DR + paragraph + bulleted breakdown
Summarize the attached document at three lengths so I can pick: - one-sentence TL;DR - one-paragraph summary - bulleted breakdown of the most important 5–8 points Keep numbers and proper nouns exact.
You'll get: Owners, due dates, blockers
Read the attached meeting transcript and extract: (a) decisions made, (b) action items with owner + due date if mentioned, (c) any blockers. Format as three short markdown sections.
You'll get: Self-contained HTML page
Build a single-page website. Self-contained HTML (style and JS inline, no external files). Purpose: a one-page "what I'm working on" portfolio. Sections: short intro, three projects with title + one-line description, a contact link. Style: warm, minimal, generous whitespace, serif headings. Works offline, no external assets.
You'll get: Production-ready React/HTML
A pricing page with three tiers: Starter (free), Pro ($12/mo), Team ($29/seat). Visual style: modern, warm, generous whitespace. Pro tier highlighted as recommended. Each card: name, price, 3 features, CTA button. Mobile-responsive, single column on small screens.
You'll get: Hero section + a CTA
Build a hero section for a product called [name] that does [one-sentence description]. Audience: [who]. Tone: [pick: playful / serious / premium / retro]. Include: headline (max 8 words), supporting subhead, primary CTA button, secondary link. Above the fold on a laptop.
You'll get: Working code in your repo
I want to add a [feature] to my project. Before writing any code: 1) Read the relevant files and tell me which ones you'd change. 2) Propose a one-paragraph plan. 3) List any risks or open questions. Then wait for my OK before editing.
You'll get: Green build, diagnosis explained
The build is failing with the error below. Read the relevant files, find the root cause, and propose a fix. If there are multiple possible causes, list them and recommend which to try first. Error: [paste here]
You'll get: A working script
Write a Python script `[name].py` that: - Takes [inputs] as arguments. - Does [the thing]. - Prints what it's about to do and asks for confirmation before any destructive change. Then run it against a tiny sample I can `mkdir`/`touch` into existence as a sanity check.
You'll get: A PR you can merge
Repo: [repo]. Goal: rename `oldName` to `newName` everywhere it appears, including imports, exports, tests, and docs. Don't touch comments that reference the old behavior. Verify by running the existing test suite. Open a PR when green.
You'll get: PR with deps updated + tests green
Repo: [repo]. Bump all dependencies to their latest minor version. Run the test suite. If any tests break, stop and open a draft PR explaining what broke. If they pass, open a normal PR.
You'll get: A persistent background assistant
(Run in Claude Code) /plugin marketplace add sypsyp97/claude-hermes /plugin install claude-hermes@claude-hermes /claude-hermes:start Then send Hermes: "Every weekday at 9am, read my Linear inbox and draft three follow-up replies for me to review."
You'll get: Terminal pair-programming
(Run in terminal) pip install aider-chat export ANTHROPIC_API_KEY=sk-ant-… cd my-project aider --model sonnet Then describe the change you want and aider edits the files + commits to git.