Turn a Vague Question into a Gemini Deep Research Brief
Converts a fuzzy research question into a paste-ready Gemini Deep Research brief with scope, sub-questions, source types, date range and report format.
341 prompts · last added
184 results for “which need softer wording” · page 6 of 8
Converts a fuzzy research question into a paste-ready Gemini Deep Research brief with scope, sub-questions, source types, date range and report format.
Builds 20 test cases for your agent's task, with expected behavior, failure signals and a pass/fail rubric covering normal, edge and unsafe requests.
Turns pasted customer reviews into evidence-based personas, jobs-to-be-done, objections and a bank of exact customer phrases ready to reuse in copy.
Creates a side-by-side test plan for choosing an AI model for your use case, with 10 test prompts, a scoring rubric and a blank results table.
Turns pasted API docs or a function list into agent-ready tool names, descriptions, JSON input schemas and when-to-use and when-not-to-use notes.
Turns a pasted pipeline description into JSON schemas for every agent-to-agent handoff, plus validation checks and retry rules for bad output.
Holds a casual conversation at your CEFR level, corrects mistakes inline in brackets, and recaps new vocabulary every 10 turns.
Writes a cover letter under 250 words that links three real achievements from your CV to the role's top requirements, without cliches.
Produces a set of testable guardrail rules for your coding agent, covering blocked commands, approval gates, secret handling and hook checks.
Produces a 3-5 subagent roster with system prompts, minimal tool permissions, model tiers and explicit handoff rules for your project.
Gives a funny but kind roast of your resume or LinkedIn profile, followed by the five fixes that would improve it most, ranked.
Turns the changes in a branch into a clear pull request description: what changed and why, how to test it, risks and screenshots to add, in your repo's template if it has one.
Directs Claude Code to reproduce a reported bug with a failing test, apply the smallest fix, and prove the fix with command output. Use it to decide whether a bug is fixed and safe to merge.
Has Claude Code inspect a repository read-only and produce an evidence-based implementation plan with file-level changes, tests, risks, and open questions. Use it to decide whether to start, split, or clarify a feature before any code is written.
Splits a research question across parallel research agents, defines source discovery and evidence review steps, merges findings into a citation table, and produces a decision memo without claiming live browsing.
Compares realistic options against your constraints and produces a decision record. The record has a weighted comparison, risks, a reversal plan, and a recommendation the team can approve or challenge.
Guides Codex through reproducing a failing CI job locally, classifying the cause as code, test, environment, or flaky, applying a minimal fix when safe, and producing an evidence-based handoff for anything it cannot resolve.
Turns your common support questions and policies into ten reusable reply macros with a warm tone, the right policy detail, and a placeholder only where agents must personalise.
Rewrites a product description so it leads with the buyer's outcome, keeps every spec accurate, answers the top objection, and fits an online store page.
Shapes your real stories and memories into a three-to-five-minute wedding toast with a clear arc, warm humour, and a closing toast line.
Rewrites any paragraph so it sounds like a real person wrote it, keeping every fact and cutting stock AI phrasing.
Claude Code inspects your repository and writes a CLAUDE.md under 200 lines with verified commands first, checkable conventions, anti-patterns and the reasons behind key decisions.
Turns a repetitive task into a build-ready automation spec with triggers, AI steps, human checkpoints, failure handling and a test plan.
Writes a cold email under 90 words that opens with a real trigger such as hiring, funding or a launch, and ends with one easy question.
Guide
Nothing that fits? Write a prompt with AI.
341 copy-ready prompts for productivity, writing, business and coding and more. Each one sets the role, the steps and the output format, and marks the parts you fill in with curly brackets.
Most are written for ChatGPT (285), Gemini (260), Claude (217) and Claude Code (42); the number is how many prompts list that tool. Each prompt page lists its tools, and most text prompts also work in any capable chat model.
Words in curly brackets, such as {audience}, are the parts you replace with your own details. Choose “Ready to use (no blanks)” in the filters to see prompts you can paste as they are.
By how often they are copied, unless you choose another order. Newest shows the latest additions first. Trending ranks prompts by copies, opens and saves over the last two weeks.
No. Every prompt is free to copy or open in your AI tool. A free account lets you save prompts to your vault.
Yes. Write with AI asks what you need, builds a short form for it, and writes the prompt as you fill it in.