提示在結果部分將目標和實績一起列出(達成 vs. 未達成),強制進行誠實評估,並使建議感覺基於證據而不是意見——利益相關者信任指明不奏效之處的回顧。
ChatGPTGeminiClaude
Product launch caption pack (3 platforms)
One launch, three native captions — Instagram, LinkedIn, and X, each in platform voice.
提示詞 3 個欄位待填
We are launching on . Write launch captions for Instagram, LinkedIn, and X — one per platform, native to each.
Rules per platform:
- Instagram: hook first line (visible before "more"), 2–4 short paragraphs, 3–5 niche hashtags at the end, one emoji max per paragraph
- LinkedIn: no hashtag stuffing, first line must work as a standalone statement, end with one question to invite comments
- X: under 260 characters, no hashtags, one concrete number or claim
Product facts to use: [3 KEY FACTS OR FEATURES]
Audience:
What we want them to do: [CTA — e.g. join waitlist / start free trial]
範例輸出
INSTAGRAM
We spent 14 months killing our own best feature.
The old export flow took 9 clicks. People used it anyway — 40,000 times a month. That felt less like love and more like hostage behavior.
So we rebuilt it. One click, any format, works offline.
Launching Tuesday. Link in bio for early access.
#productdesign #saasfounder #buildinpublic #uxdesign
LINKEDIN
Most teams do not have an export problem. They have a nine-click problem.
[...] What is the most-used-but-most-hated feature in your product?
X
We rebuilt export from 9 clicks to 1. 40k exports/month just got 8 clicks shorter. Early access opens Tuesday.
提示Feed the model real usage numbers or a concrete "before" pain (like the 9 clicks) — captions built on one specific fact outperform adjective-stacked launch copy on every platform.
ChatGPTGeminiClaude
Instagram/LinkedIn carousel from a blog post
Turn a long post into a 7–9 slide carousel: one idea per slide, swipe-worthy pacing.
提示詞 2 個欄位待填
Turn this article into a carousel of [7-9] slides for [PLATFORM — Instagram or LinkedIn].
Structure:
- Slide 1: a hook that names the payoff or the mistake (max 12 words)
- Slides 2 to N-1: ONE idea per slide, max 25 words each, no filler transitions
- Last slide: recap in 3 bullets + one CTA:
- After the slides, write the post caption (2 sentences + question)
Keep the numbers and concrete examples from the article; cut the storytelling.
Article:
範例輸出
Slide 1: Your onboarding email is why they never came back.
Slide 2: 63% of trial users open email #1. Only 11% open email #4. The sequence is the leak.
Slide 3: Email #1 job: one action, done in 90 seconds. Not a feature tour.
Slide 4: Subject lines with the user's goal beat product names 2:1 in our test.
Slide 5: Send #2 after the action happens, not 24 hours later. Behavior beats schedule.
Slide 6: One CTA per email. Two CTAs = half the clicks on both.
Slide 7: Recap — 90-second first win · behavior-triggered sends · one CTA. Steal our full sequence: link in comments.
Caption: We rewrote a 4-email onboarding sequence and doubled activation. The whole teardown is in the carousel. Which email in your sequence gets ghosted the hardest?
提示The "max 25 words per slide" constraint is what makes output usable — without it models write paragraph slides that die in design. Tighten to 18 words for Instagram, loosen to 30 for LinkedIn.
ChatGPTGeminiClaude
A/B hook lines for one post
Ten first-line variants for the same post, split across proven hook patterns.
提示詞 3 個欄位待填
Write 10 first-line hooks for a social post about , for .
Give exactly 2 hooks in each pattern:
1. Contrarian ("Everyone says X. It's wrong.")
2. Specific number/result
3. Mistake or loss framing
4. Direct question to the reader
5. Before/after snapshot
Max 12 words each. No emoji, no clickbait words (secret, shocking, insane). Audience: .
範例輸出
Contrarian
1. Posting daily is shrinking your reach, not growing it.
2. Your best content calendar is no content calendar.
Number/result
3. One caption format took us from 200 to 4,100 followers.
4. We deleted 60% of our posts. Engagement doubled.
Mistake/loss
5. You're losing followers in the first seven words.
6. That "link in bio" line costs you half your clicks.
Question
7. What made you unfollow the last brand you unfollowed?
8. Would you stop scrolling for your own post?
Before/after
9. Last March: 12 likes. This March: 1,200. Same product.
10. From ghost town comments to 80 replies — one change.
提示Run the 10 hooks past a colleague and ask them to point at one — do not describe, just point. The finger test kills committee-brain and picks the scroll-stopper faster than discussion.
ChatGPTGeminiClaude
Reply to comments in brand voice
Batch-draft comment replies that sound human, match brand tone, and never copy-paste thanks.
提示詞 2 個欄位待填
Draft replies to these comments on our post.
Brand voice: [2-4 ADJECTIVES, e.g. warm, direct, lightly funny, never corporate].
Rules:
- Each reply is different — no repeated openers, no generic "Thanks for sharing!"
- Match the commenter's energy (short comment = short reply)
- Answer questions concretely; if we don't know, say so and route to
- Critical comments: acknowledge the specific point first, no defensiveness, offer the next step
- Max 2 sentences per reply unless a question needs more
Comments:
[PASTE COMMENTS, ONE PER LINE]
範例輸出
@mia.builds ("This is exactly what I needed today")
→ Timing is everything 🙌 What are you building with it?
@dev_karol ("Does it work with Notion?")
→ Not yet — Notion sync is on the Q3 board. The waitlist for beta is at the link in our bio.
@sceptical_sam ("Feels like every app promises this and none deliver")
→ Fair — the category has earned that. If you try it and it breaks the promise, tell us where; that feedback goes straight to the roadmap.
@lena.mkt ("price??")
→ Free plan + paid from $9/mo. Full breakdown: [pricing link].
提示Paste real comments verbatim including typos and usernames — the model mirrors register much better from raw material than from your summary of "someone asked about pricing."
ChatGPTGeminiClaude
FAQ block + schema for an article
Mine the real questions under a keyword and produce an FAQ section with JSON-LD ready to paste.
提示詞 3 個欄位待填
For an article targeting , produce an FAQ section.
1. List the 5 questions real searchers ask around this keyword (People-Also-Ask style — specific, not invented corporate FAQs)
2. Answer each in 40–60 words, first sentence = direct answer (featured-snippet style), no marketing fluff
3. Output a valid FAQPage JSON-LD block with all 5 Q&As
4. Flag which single question is the best candidate for its own standalone article
Context: our product is ; the article's angle is .
範例輸出
Q1: How long does it take to migrate from spreadsheets to a CRM?
A: Most small teams complete a spreadsheet-to-CRM migration in one to two weeks. The import itself takes hours; the time goes into cleaning duplicate contacts and agreeing on pipeline stages before you import [...]
Q2: Can I import Excel files with custom columns? [...]
JSON-LD:
{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"How long does it take to migrate from spreadsheets to a CRM?","acceptedAnswer":{"@type":"Answer","text":"Most small teams complete a spreadsheet-to-CRM migration in one to two weeks..."}}, ...]}
Standalone article candidate: Q1 — migration-time queries have commercial intent and no dominant answer in the current SERP.
提示Ask for "questions real searchers ask", not "FAQs" — the latter makes models invent polite product questions nobody Googles. Cross-check the five against actual PAA boxes before publishing.
ChatGPTGeminiClaude
Content refresh brief for a decaying post
Diagnose why an old post slipped and produce a surgical update plan — not a rewrite.
提示詞 3 個欄位待填
This article used to rank for and has slipped. Build a refresh brief — surgical edits only, no full rewrite.
Article (paste or outline): [PASTE ARTICLE OR H2 OUTLINE + PUBLISH DATE]
What currently ranks top 3 (titles/outlines):
Produce:
1. Decay diagnosis: what the top results now cover that we don't (list, specific)
2. Keep list: sections that still earn their place (do not touch)
3. Update list: sections to edit, each with what exactly changes
4. Add list: new H2/H3s with 1-line content notes
5. Kill list: sections to delete and why
6. New title + meta description options (2 each)
7. Internal links to add:
範例輸出
Diagnosis: Top 3 now all cover AI-assisted workflows (added 2024), include a comparison table, and cite 2025 pricing — ours stops at 2023 tools and has no table.
Keep: "Why briefs fail" (still the best section, unique angle), the 3 real examples.
Update: "Tools" H2 — swap 2 dead tools for [current leaders], update all pricing; intro — replace 2022 stat with 2025 equivalent.
Add: H2 "Using AI to draft the brief (and where it fails)" — the query's new center of gravity; H3 comparison table of 5 tools.
Kill: "History of content briefs" — zero search demand, buries the useful part.
Title options: ...
Meta options: ...
Internal links: add /keyword-clustering-guide at "group your keywords" mention.
提示The keep/kill lists matter more than the add list — refreshes fail when everything gets touched and the sections Google already rewards get rewritten into something worse.
ChatGPTGeminiClaude
Cluster a keyword list into page groups
Sort a raw keyword dump into pages — one intent per page, no cannibalization.
提示詞 1 個欄位待填
Cluster this keyword list into page groups. One page per distinct search intent — if two keywords can be satisfied by the same page, they belong in the same cluster.
For each cluster give:
- Cluster name + the page type that wins (guide / comparison / tool page / listicle)
- Primary keyword (highest value) and supporting keywords
- One-line content angle
- Flag: any keyword that is its own intent and deserves a separate page
Also list keywords to DISCARD (zero commercial or informational value for us) with a one-word reason.
Our site: . Keywords:
[PASTE KEYWORD LIST, ONE PER LINE — VOLUME OPTIONAL]
範例輸出
Cluster 1 — "invoice template" (page type: free tool page)
Primary: free invoice template (9,900)
Supporting: invoice template word, invoice template pdf, simple invoice template
Angle: instant download, no email gate — every competitor gates.
Cluster 2 — "how to invoice" (page type: guide)
Primary: how to write an invoice (2,400)
Supporting: what to include in an invoice, invoice requirements freelance
Angle: first-invoice walkthrough for freelancers with a filled example.
Separate-page flag: "invoice vs receipt" — comparison intent, its own page.
Discard: "invoice meaning in hindi" (locale), "invoice 2019 crack" (junk).
提示Give the model your site's one-line description — clustering changes completely depending on whether you sell software, run a blog, or offer templates, and models default to generic blog clustering without it.