Explore a prompt, imagine the result, and make it your own. These original examples are here to get your curiosity moving.
Browse the example library
12 examples to spark an idea
WritingChatGPT
Turn rough notes into a clear email
Shape a few hurried notes into a warm, direct message without adding promises you did not make.
See the example
A prompt to try
Turn these notes into a friendly, concise email to a colleague. Keep the tone calm, include the Tuesday deadline, and do not promise that the work is finished: [paste notes]. Give me a subject line too.
What you could create
A short subject line and a draft email organised around the request, the Tuesday deadline and the next step. The draft keeps the status honest and leaves a clear place to add any missing detail.
Make it your own
Paste the notes
Name the audience and tone
State facts the draft must preserve
Check the final message before sending
ResearchChatGPT
Start research with traceable sources
Build a first-pass comparison from current material and make gaps visible instead of hiding them.
See the example
A prompt to try
Compare the current guidance from these three organisations on home insulation grants. Use recent primary sources, cite each key claim, make a table of eligibility and dates, and list anything you could not verify: [links].
What you could create
A structured table with source links, differences in eligibility, relevant dates and a short list of unanswered questions to verify with the organisations.
Make it your own
Provide a specific question
Ask for primary sources and dates
Request citations beside major claims
Open the sources and verify the details
ResearchChatGPT
Explain a difficult idea simply
Learn a new concept through a plain explanation, a concrete example and a chance to check your understanding.
See the example
A prompt to try
Explain what an API is to someone who has used websites but has never programmed. Use a library-book example, define any technical words, then give me three questions to check my understanding.
What you could create
A short explanation that compares an API to a library catalogue and borrowing desk, followed by a small glossary and three questions with answers available on request.
Make it your own
Say what you already know
Choose a useful everyday comparison
Ask for technical terms to be defined
Follow up where the explanation is unclear
PlanningChatGPT
Find actions in meeting notes
Separate decisions, owners and open questions so the next steps are easy to review.
See the example
A prompt to try
From these meeting notes, list only actions that were actually agreed. Show the owner and due date if stated. Put uncertain or missing details in an open-questions section; do not guess: [paste notes].
What you could create
A compact action list with owners and due dates where present, followed by questions for details the notes do not establish.
Make it your own
Share the notes
Define what counts as an agreed action
Tell it how to mark missing information
Confirm the list with meeting attendees
WritingChatGPT
Review page copy for clarity
Spot jargon, vague links and dense sentences before a page goes live.
See the example
A prompt to try
Review this page copy for plain English. Find jargon, long sentences, unclear calls to action and link text that may make little sense out of context. Suggest edits in a table and explain why; do not claim this checks full accessibility conformance: [paste copy].
What you could create
An editorial review with the original phrase, a suggested rewrite and a short reason for each change. It focuses on the supplied text rather than claiming to test the whole website.
Make it your own
Provide the copy and audience
Set the review scope
Ask for reasons with suggested edits
Have a person approve changes
CreativeChatGPT
Explore a visual concept
Develop a visual direction for a fictional neighbourhood garden poster before commissioning final artwork.
See the example
A prompt to try
Create a poster concept for a fictional community garden open day. Use a screen-print feel, bold leaves and hand-drawn lettering. Leave clear space for the real date and address; do not invent either. Describe the visual choices before generating an image.
What you could create
A visual direction with a limited colour palette, layered leaf shapes and a reserved information area, followed by an illustrative concept that still needs real event details and design review.
Make it your own
Describe the audience and purpose
Name the style and must-have elements
Call out details that must stay blank
Review the concept before publishing
CodingCodex
Trace a bug from its error message
Ask Codex to locate the relevant code, explain a likely cause and test a focused fix.
See the example
A prompt to try
Investigate why the settings page crashes when the saved theme is missing. Follow the existing project patterns, explain the cause, add a safe default and a focused test, then report which checks you ran. Do not change unrelated files.
What you could create
A reviewable code change with a safe fallback, a focused regression test and a summary of the files and checks involved. A developer should inspect the diff and confirm the expected behaviour.
Make it your own
Open the correct repository
Describe the failure and expected behaviour
Ask for a focused fix and regression test
Review the diff and run relevant checks
CodingCodex
Plan a reusable interface component
Translate a design need into a small implementation plan grounded in the existing codebase.
See the example
A prompt to try
Inspect this repository and propose a reusable alert component for success, warning and error messages. Follow its current styling and accessibility patterns. First show the files you would touch and the keyboard and screen-reader behaviour; wait for review before implementation.
What you could create
A concise component proposal that identifies relevant files and explains the semantics, accessible name and visual variants before any code is changed.
Make it your own
Give Codex the repository
Describe the user need and variants
Ask it to inspect local patterns
Review the plan before asking for code
CodingCodex
Find a missing test case
Use Codex to compare a behaviour with existing tests and propose one useful regression check.
See the example
A prompt to try
Read the date-formatting function and its tests. Find one important edge case the tests do not cover, explain why it matters, and add a focused test using the existing test style. Do not change the function unless the test exposes a bug.
What you could create
A targeted test for an uncovered boundary case and a report of whether the existing implementation passes it, using the repository's established test style.
Make it your own
Point to the code and test area
Ask for a meaningful uncovered edge case
Keep the requested change small
Read the test and verify it fails for the intended regression
PlanningChatGPT
Turn a goal into a manageable plan
Break a broad personal project into steps with visible assumptions and a first action.
See the example
A prompt to try
Help me plan a small portfolio site over four weekends. I can spend about three hours each weekend and want to show three projects. Make a week-by-week plan, identify what depends on what, and ask about any assumptions that could change the plan.
What you could create
A four-part plan with realistic work blocks, a sequence for the three projects and explicit assumptions to confirm before the schedule is treated as final.
Make it your own
Give the goal and available time
Name what success looks like
Ask for dependencies and assumptions
Adjust the plan after trying the first step
PlanningDots
Prepare a recurring weekly brief
Ask a dot to gather updates from connected project sources and return a short reviewable summary.
See the example
A prompt to try
Each Friday, review the project notes and task board I connected. Prepare a brief with completed work, changes to deadlines, blockers and decisions I need to make. Include a link or source for each item. Ask me before sending the brief to anyone.
What you could create
A draft brief with sourced updates, deadlines, blockers and decisions for review. The instruction keeps sharing under the user's control.
Make it your own
Confirm dots are available for the account
Connect only the relevant sources
Set a schedule and a clear brief format
Review the first brief and adjust access or timing
ResearchDots
Keep a research task moving
Have a dot monitor a defined set of material and return with new findings for your review.
See the example
A prompt to try
For the next two weeks, check the connected reading list for new papers about urban tree cover and heat. When something relevant appears, add its title, date, source link and a three-sentence summary to a draft note. Flag uncertainty and do not contact authors or share the note.
What you could create
A running draft note with relevant items, dates and links, plus clear flags for uncertain matches. The scope and sharing boundary remain explicit.
Make it your own
Define a narrow topic and time window
Choose the sources the dot can access
Specify what counts as relevant
Review the draft and stop or revise the task when needed