Customer Interview Synthesis into Themes, Evidence, and Product Decisions
Turn raw interview notes or transcripts into evidence-backed themes, a quote bank, and a prioritized decision list. It keeps what customers said separate from what you infer.
341 prompts · last added
130 results for “soft shadows on the curtain” · page 1 of 6
Turn raw interview notes or transcripts into evidence-backed themes, a quote bank, and a prioritized decision list. It keeps what customers said separate from what you infer.
Produces an onboarding guide for one folder of a codebase: what it does, how data moves through it, the files to read first and the traps a new developer should avoid.
Builds a blog post outline for one keyword by first deciding the search intent, then structuring headings, questions and examples that match what searchers expect to find.
Builds a negotiation script for a job offer: your anchor number with a reason, word-for-word replies to common pushback, and a walk-away line, using market data you supply.
Has Claude Code define schema-based handoff contracts between agent phases, generate a validator, and add contract tests. Supports the decision of which phase boundaries need strict contracts versus lightweight checks.
Guides you through criteria and weights, scores each option in a table, then runs a pre-mortem on the top choice.
Has the Cursor agent restructure a messy component into smaller pieces while proving the behaviour stays identical, using existing tests or new characterization tests first.
Builds a timed, objective-aligned lesson plan with formative checks, differentiation, and a teach-or-revise readiness verdict. It asks for missing inputs first and keeps assumptions separate.
Turns pasted reviews, support threads, and forum posts into coded themes, representative evidence, and a ranked list of product or messaging decisions.
Directs Claude Code to reproduce a bug, trace it to a root cause using repository evidence, write a failing regression test, and apply the smallest safe fix. Ends with a verified diff, risks, and next actions.
Turns pasted account material and a source discovery plan into a evidence-labeled research brief. It helps a rep decide whether to pursue an account, which persona to target, and which outreach angle to use.
Guides Cursor Agent through reproducing a bug, isolating the root cause with evidence, applying a minimal diff, and adding a regression test, ending with a verification checklist and risks.
Builds a one-page cheat sheet of your ten most likely sales objections, each with the real concern behind it, a question to ask back, a short answer, and proof to share.
Turns your source material into a diagnostic quiz with an answer key, a misconception map, and a reteach plan. It helps you decide who needs review and what to reteach.
Builds a tailored discovery call agenda, question bank, and qualification scorecard so a rep can decide whether to advance, nurture, or disqualify an opportunity after the call.
Turns your product facts, customer evidence, and competitor notes into a tested positioning statement, messaging hierarchy, and proof-gap list so a marketing team can decide what to say and what to validate first.
Writes a timed lesson plan with one shared objective and three tiers of tasks, plus support for learners who need scaffolding and stretch tasks for those who finish early.
Checks a claim you saw online against primary sources, traces where it came from, and returns a verdict with a confidence rating and the evidence on both sides.
Sorts a pasted bank export into spending categories, shows where the money went, and builds a zero-based budget where every unit of income gets a job.
Audits an old article for outdated facts and missing subtopics, proposes new sections and rewrites the intro for your target keyword.
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.
Designs the handoff contracts, stop conditions, and review gates for a sequential chain such as researcher, writer, editor, and fact-checker. Helps you decide whether the chain is ready to run.
Plan a custom GPT before building it. Produces the instruction text, knowledge file plan, conversation starters, and a test set so you can decide whether to build, narrow, or skip it.
Runs a read-only Codex investigation that maps the relevant code paths, test commands, and likely root causes for a bug report. It ends with a ranked hypothesis table and a go/no-go recommendation before any edits.
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.