Meta Muse Wonder Prompt Generator

Analyze this screenshot of my web app's checkout flow. Identify: (1) any UX friction points — elements that slow users down or cause confusion; (2) accessibility issues — contrast, target size, label clarity; (3) trust signals that are present or missing; (4) the single highest-impact improvement I could make in under 2 hours of dev time. For each issue, rate severity: Critical / Should Fix / Nice to Have. [Attach screenshot]

Read these three research papers and write a 600-word synthesis that: (1) identifies the single key finding each paper contributes; (2) shows where the three papers agree; (3) shows where they contradict each other and why — methodology difference, sample size, or definitional disagreement; (4) identifies the most important question the combined research leaves unanswered. Write for a policy audience: confident, direct, no academic hedging. [Attach papers]

Review this contract for risk to the party named [Your Company Name]. Identify: (1) clauses that expose us to unlimited liability; (2) IP ownership provisions and what we are giving up; (3) termination conditions we cannot control; (4) payment terms and what happens if we miss one; (5) any clause that is unusual compared to standard industry practice and why it matters. For each issue give: the clause reference, the risk in plain language, and the specific change I should request. [Attach contract PDF]

Watch this short product demo video and write: (1) a 60-second script for a voice-over that highlights the three strongest value propositions shown; (2) three 280-character tweets that could accompany the video on launch day — each using a different angle (feature, outcome, social proof); (3) a 150-word LinkedIn post for the CEO to share on launch day. Keep all copy benefit-led, not feature-led. Avoid superlatives. [Attach video file]

Review the attached codebase for security vulnerabilities. Focus on: authentication and session handling; SQL/NoSQL injection vectors; hardcoded secrets or credentials; unsafe deserialization; CORS configuration; third-party dependency risks in package.json/requirements.txt. For each vulnerability found: severity (Critical / High / Medium / Low), the file and line, how it could be exploited in a realistic attack scenario, and the exact code change needed to fix it. List what you checked and found clean, too. [Attach codebase]

Read this full meeting transcript and extract: (1) every decision made — word it as a statement of what was decided, not who said what; (2) every action item with owner and deadline as stated; (3) every commitment made to a person not in the room; (4) any open question that was raised but not resolved. Format as a structured document I can email to all attendees. If an owner or date was not stated, write 'unassigned' or 'no date set'. [Paste transcript]

Transcribe this audio recording and then produce: (1) a clean, formatted transcript with speaker labels if multiple speakers are present; (2) a 150-word executive summary of the main points; (3) a list of any names, numbers, dates, or proper nouns mentioned that I should double-check for accuracy; (4) the single most important thing I need to act on from this recording. [Attach audio file]

Read these three annual reports from my main competitors. For each one, identify: their stated strategic priorities for the coming year; any new product lines, markets, or partnerships announced; any acknowledged risks that are relevant to us; and changes in R&D spend. Then write a 400-word briefing for our leadership team comparing their trajectories and flagging where we are most exposed. [Attach PDFs]

Extract all the data from this chart image into a clean CSV. Then: (1) describe the trend in two sentences as if presenting to a board; (2) identify the highest and lowest data points with their labels; (3) flag any anomaly or break in trend that would warrant further investigation; (4) state the single most important business implication of this data. [Attach chart image]

Review this technical documentation against the actual codebase I have attached. Identify: (1) anywhere the documentation contradicts the code; (2) public API endpoints or parameters that are in the code but not documented; (3) documented features that no longer exist in the code; (4) examples in the documentation that are syntactically incorrect. Format as a prioritised list: Documentation Errors / Missing Coverage / Outdated Examples. [Attach docs and code]

I am attaching screenshots of 50 user reviews from our app store listing. Read each one and produce: (1) the top 5 most frequently mentioned complaints, ranked by frequency; (2) the top 5 most frequently mentioned praise points; (3) three distinct user segments visible in the feedback — describe each by what they value and what frustrates them; (4) the one product change that would address the most complaints simultaneously. Use exact quotes to support each finding. [Attach screenshots]

Read this clinical study and summarize it for a patient with no medical background. Include: (1) what the study was testing in one plain-English sentence; (2) what they found — the main result in terms a non-specialist can understand; (3) what the limitations are — small sample, short follow-up, specific population; (4) what this means for someone with this condition in practical terms. Do not use statistical jargon. Do not overstate certainty. If the study is preliminary, say so clearly. [Attach PDF]

Watch this tutorial video and produce a written step-by-step guide that someone could follow without watching the video. Include: timestamps for each major section, exact commands or actions shown, expected outputs after each step, and any caveats mentioned verbally. Format as a numbered list with clear section headers. Note any step where the video moves too fast or skips an assumption that a beginner would need explained. [Attach video]

Read the attached quarterly financial statements for the last four quarters. Calculate and explain: (1) revenue growth rate quarter-over-quarter; (2) gross margin trend; (3) operating expense as a percentage of revenue — is it improving or worsening; (4) cash runway if current burn rate continues. Then write a 300-word narrative summary for a non-financial founder that explains the overall trajectory honestly — good and bad. [Attach financial statements]

Read this podcast transcript and turn it into a 1,200-word blog post. Keep the speaker's opinions, examples, and specific data points — these are the most valuable parts. Structure: a compelling opening that hooks readers who did not listen to the podcast; 3–4 sections with descriptive H2s covering the main ideas; a closing paragraph with one concrete takeaway. Remove filler phrases and repetition. Do not say 'In this podcast' or 'The host asked' — write as if the ideas are being shared directly. [Paste transcript]

I am attaching screenshots of my main competitor's website — homepage, pricing page, and features page. Analyze: (1) how they position their product and who their primary buyer persona appears to be; (2) their key value propositions and how they communicate them; (3) their pricing strategy and what signal it sends; (4) any UX patterns that are working particularly well; (5) three things we should copy and one thing they are doing wrong. Be specific — reference elements visible in the screenshots. [Attach screenshots]

Read this draft chapter and give me a professional editor's critique. Structure your feedback as: (1) Argument — is the central claim clear and supported throughout? Where does it weaken? (2) Structure — does the chapter flow logically? Where does a reader lose the thread? (3) Prose — identify the three weakest sentences or paragraphs and rewrite each; (4) Evidence — are the claims supported? Where does the author assert without proof? (5) Priority fix — the single change that would most improve this chapter. [Paste chapter]

Examine this screenshot of my website and evaluate it against WCAG 2.2 AA accessibility standards. For each issue found, provide: the WCAG criterion it violates (e.g. 1.4.3 Contrast), the specific element on screen, the problem in plain language, and the change needed to pass. Then rate the overall accessibility: what is working well; what is the single most critical issue to fix first; and the estimated effort level (High / Medium / Low) for each fix. [Attach screenshot]

Write a 2-page feasibility study for this project: [describe the project — e.g. 'launching a B2B SaaS product for property managers in the UK']. Structure: (1) Executive Summary — is this feasible and on what conditions; (2) Market Analysis — size, growth, key players, our position; (3) Technical Feasibility — what needs to be built and key risks; (4) Financial Feasibility — estimated costs, revenue assumptions, break-even timeline; (5) Recommendation — go, no-go, or go with conditions. Write for a board audience: confident, evidence-based, no filler.

I am attaching our product specification document and our marketing website copy. Read both documents completely and identify: (1) any claim in the marketing copy that the spec document does not support; (2) features listed in the spec that are absent from the marketing copy; (3) any terminology that is used inconsistently between the two documents; (4) pricing or limitations mentioned in one document but not the other. Format as a table: Issue / Location in Document A / Location in Document B / Recommended Correction. [Attach both documents]