BoplisExplore the demo
Prompt library

Less guessing. Better first drafts.

Six starting points for briefs, posts, guides and reviews. Replace the bracketed fields with your own notes, then check the result before using it.

How to use them

Bring the facts. Keep the judgment.

01

Fill in the context

Choose one reader and one task. Supply the facts, working links, current limitations and examples of your voice.

02

Ask for the gaps

Keep instructions that mark unknowns and unverified claims. Do not let a neat answer hide missing information.

03

Review the draft

Open the sources, try the destination and read the text aloud. Keep sensitive information out of tools you have not approved for it.

A brief the whole team can use

Get the product, audience and limits onto one page before making content.

Write a short marketing brief using only the notes below.

Product: [what it does today]
Reader: [one specific audience]
Problem: [their task or frustration]
Evidence: [demo, notes and source links]
Not available yet: [current limits]
Voice examples: [two short examples]

Return: one-sentence positioning, three useful messages, claims to verify, and one next action. Mark missing information as unknown. Do not invent pricing, customers or working features.
Download .md

What to expect: A focused brief and a visible list of gaps.

Review: Check that every capability comes from the notes. A polished sentence is not evidence.

Explain one thing you shipped

Make an announcement that tells the reader what changed.

Draft a short post about this release for [channel].

Reader: [who it helps]
Previous task: [what they had to do]
New behavior: [what actually works now]
Proof: [specific screenshot or demo]
Availability and limits: [details]
Destination: [verified link]

Lead with the change, show one concrete example, state the limits and finish with one next step. Use plain language. Do not claim results we have not measured.
Download .md

What to expect: A post with a reason to click and an accurate expectation of what follows.

Review: Try the link and demo yourself. Remove any line that promises more than they show.

Answer a customer question

Turn a question into an outline with enough detail to be useful.

Create an article outline that answers this question: [exact question].

Reader's starting point: [what they already know]
Our notes and examples: [material]
Sources: [links or pasted excerpts]
Desired result: [what the reader can do afterward]

Start with the direct answer. Include a worked example, ordered steps, common mistakes and a verification list. Label unsupported facts as needing research. Do not invent sources or quotes.
Download .md

What to expect: An outline ready for someone with subject knowledge to review.

Review: Open the sources and confirm they support the claims before expanding the outline.

A useful community reply

Help with the question before deciding whether a product mention belongs.

Draft a reply to the question below using my notes.

Question: [paste the question]
Community rules: [paste the current rules]
Relevant experience: [what I actually know]
My affiliation: [what I build or sell]
Product mention allowed: [yes, no or unclear]

Answer the question directly with practical steps. Disclose my affiliation if the product is mentioned. Leave the mention and link out when the rules prohibit them or permission is unclear. Do not invent first-hand experience, endorse accounts or ask for votes.
Download .md

What to expect: A draft to read, check against the rules and post yourself if appropriate.

Review: A draft cannot grant posting permission. Read the current community rules and judge the context yourself.

Compare options without making up a winner

Help a reader choose based on the work they need done.

Draft a comparison for a reader choosing how to do [task].

Options: [options to compare]
Criteria: [important requirements]
Verified facts, sources and dates: [material for each option]
Unknowns: [what has not been checked]
Our relationship to an option: [disclosure]

Return a short summary and a table with best fit, tradeoffs and unknowns. Explain when each option could be appropriate. Do not invent prices, features, test results or time savings. Put a source next to each outside product claim.
Download .md

What to expect: A fair comparison draft with visible sources and missing information.

Review: Recheck features and prices on the provider's own pages. Keep unknowns visible.

A weekly recap you can act on

Leave the week with a small next step instead of another long task list.

Summarize this week's marketing work.

Published or shipped: [work and links]
Still in draft: [work]
Feedback: [questions and notes]
Verified measurements: [figures, dates and definitions]
Time available next week: [time]

Return: what happened, what we learned, what remains unknown, and up to three next actions with an owner and definition of done. Keep plans separate from completed work. Do not turn missing data into a success claim.
Download .md

What to expect: A readable recap and a realistic plan for next week.

Review: Check dates and definitions for each measurement. Make sure someone can own every next action.

A prompt is a starting point.

Do these prompts run in Boplis?

Copy a prompt or download its Markdown guide to use with a drafting tool of your choice. The workspace currently returns sample responses and does not run these prompts through a live agent.

What if I do not have all the inputs?

Leave the gaps visible and ask what needs checking. Do not replace a missing customer quote, metric or feature detail with an invented one.

Can I change the format?

Yes. Add a length, a channel or an output format that fits your task. Keep the factual limits and review checks intact.