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
260 results for “ci” · page 3 of 11
Builds a source discovery plan, evidence log, citation table, and synthesis for comparing UX patterns across competitors, without claiming live browsing.
Combines your Docs, Sheets, meeting notes, and outside sources into one decision memo. Separates internal evidence from external research and logs conflicts, gaps, and next actions.
Builds a source discovery plan, evidence review, and citation table for a video's factual claims so a producer can decide which claims to keep, soften, or cut before scripting.
Creates a cinematic golden-hour scene of your adult self shaking hands with your younger self using your current and childhood photos.
Pulls the central claims out of a long report or paper, with page numbers, the evidence behind each claim and how strong it is, so you can cite or challenge it quickly.
Turns your photo into a chunky plasticine stop-motion character doing an activity of your choice on a miniature handmade set.
Generates a handheld, creator-style demo of your product being used, with a visible AI-generated label, so you can preview social video ideas honestly.
Puts your product into a believable, styled real-world scene with props and daylight, the kind of lifestyle image used on product pages and social ads.
Has Claude Code review a branch diff like a skeptical maintainer, producing severity-ranked findings with evidence and a clear merge, fix, or block recommendation. Use it before opening or approving a pull request.
Guides Claude Code to refactor a module safely by first pinning current behavior with characterization tests, then making small, reversible commits. Helps you decide whether the refactor preserved behavior and is worth merging.
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.
Converts scrappy bullet notes into a clear report with an executive summary, findings, decisions and next steps, without inventing anything.
Converts discovery notes into a one-page proposal executive summary and a dated mutual action plan. It helps a rep decide whether the deal is ready to propose and what is still missing.
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.
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.
Creates a realistic study plan for an upcoming exam based on topics, current confidence, and available hours. It outputs a weekly schedule, practice targets, and a checkpoint to decide where to shift effort.
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.
Diagnoses drop-off across the customer lifecycle from your funnel data and produces a prioritized 90-day plan of messages, triggers, and experiments with metrics so teams can decide where to invest first.
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.
Has Cursor lock in current behavior with characterization tests before restructuring a legacy module in small steps, so you can decide whether the refactor preserved behavior and is safe to merge.
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.
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.