Competitor UX Pattern Research Plan with Evidence Table and Design Recommendation
Builds a source discovery plan, evidence log, citation table, and synthesis for comparing UX patterns across competitors, without claiming live browsing.
341 prompts · last added
116 results for “deal-review” · page 3 of 5
Builds a source discovery plan, evidence log, citation table, and synthesis for comparing UX patterns across competitors, without claiming live browsing.
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.
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.
Guides a source-backed evaluation of software or service vendors against weighted criteria. Ends with a decision memo covering risks, open questions, and verification steps before purchase.
Builds a behavior-based test matrix for a function or module and then generates test code in your framework. Covers edge cases, failures, and mocking boundaries, with coverage gaps stated honestly.
Turn a crawl export and Search Console data into a scored, sprint-ready technical SEO fix list. It separates facts from assumptions and flags what needs verification before developers start work.
Produces a 60-180 second explainer video script from a brief, with a scene-by-scene table for voiceover and visuals, a fact-check list, and a go/no-go checklist for recording.
Has Gemini inspect uploaded images, screenshots, charts, and PDFs, extract what is visible, and verify claims against online sources. Ends in a findings log with confidence ratings and next steps.
Diagnoses what a price objection really means and builds response scripts, trade-based concession rules, and escalation criteria. It helps a rep decide whether to hold price, trade scope, or walk away.
Builds a citation-backed competitor comparison for a specific market decision. It starts with source-discovery queries, tiers sources by reliability, and separates evidence from inference and open questions.
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.
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.
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.
Guides GitHub Copilot agent mode to inspect the repository, state assumptions, plan a minimal change, implement it, and add tests. It ends with a verification report you can use to decide whether to open a PR.
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.
Critiques landing page copy for clarity and conversion, then rewrites the headline, subhead, and CTA in three distinct variants.
Turns a pasted CLAUDE.md or AGENTS.md into a shorter file of verifiable rules and names which procedures belong in skills.
Summarizes an uploaded long video or PDF with timestamp or page citations, then lists key claims with evidence and action items.
Audits an existing multi-agent pipeline for failure modes and produces retry limits, fallback paths, escalation triggers, and a test plan. Supports the decision on what to harden before wider rollout.
Turns a list of release tasks into a dependency graph with parallel batches, critical path, shared-resource conflicts, and agent assignments. Supports the decision on what to run now versus wait on.
Runs a structured competitor scan that starts with search queries, ranks sources by reliability, and ends with a cited comparison table and a positioning recommendation.
Produces a least-privilege tool inventory, function definitions, and approval rules for an agent that calls APIs or internal systems.
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.