Paste rough lab notes and get owners, next checks, risks, and one clean status update.

Convert these lab notes into: 1. decisions made, 2. open questions, 3. owner/action/date, 4. concise status note.

Give the sender's note and your rough answer. The prompt preserves your intent but makes it professional.

Rewrite my rough reply. Preserve my intent and timing. Add one useful context sentence if my answer is too short. Return only the reply.

A prompt post is much more useful when the author shows the bad output, the changed prompt, and the improved output.

Turns long meeting transcripts into decisions, owners, and follow-up emails.

Extract decisions, rejected options, action owners, deadlines, and a follow-up email draft from this transcript.

A process for turning schematic screenshots and comments into a review summary and action list.

Review these schematic notes. Separate confirmed issues, questions, component value checks, and follow-up emails.

Paste informal instructions and get a clear SOP with scope, prerequisites, steps, and checks.

Turn this rough process into an SOP with purpose, scope, prerequisites, steps, failure checks, and owner.

Each prompt should list exactly what the user needs to provide before it can work well.

Use a screenshot to catch layout overlap, text fit, missing states, and visual hierarchy issues.

Inspect this screenshot for UI bugs. Focus on overlap, text truncation, spacing, hierarchy, and missing states.

Instead of fixed levels, an AI game can ask what kind of challenge the player wants and tune story, hints, and stakes in real time.

Track launches across labs and startups, then rank them by likely effect on your roadmap.

Compare these AI launches by capability, pricing, integration friction, and which teams should care.

Sketch a compact game loop with clues, suspicion, consequences, and escalating stakes.

Design a replayable AI mystery game with core loop, clue economy, failure states, and three escalating scenes.

Generate quests that respond to party composition, inventory, and recent failures so sessions feel less scripted.

Create three adaptive quests for this co-op party. Use their abilities, last two failures, and one surprise reward.

Turn a long AI magazine feature into a crisp summary for operators who do not have time to read the full piece.

Summarize this AI magazine article into: headline takeaway, what changed, why it matters to teams, and one risk worth watching.

Merge YouTube, magazine, research blog, and tech site coverage into one ranked board so you can see where sources agree or conflict.

Combine these AI news sources, cluster them by story, mark source type, and rank stories by practical importance for builders.

Useful when timelines are noisy and teams need a grounded read on whether a story matters yet.

Assess this AI rumor and return credibility, likely source motivation, what to watch next, and whether a team should react now.

Track policy, export controls, copyright cases, and standards updates without flooding the team.

Summarize these AI policy links into decision risk, likely timeline, who is affected, and what product teams should prepare.

Every big story is more useful if readers know exactly what they can try today and what they still cannot verify.

Push an AI companion system through conflicting moods, memory callbacks, and abrupt tone shifts.

Write a dialogue stress test with five player tone changes, three memory callbacks, and one contradiction trap.

Prototype a courtroom loop with testimony gaps, bluffing, evidence pressure, and escalating reveals.

Design a replayable AI courtroom game with witness contradiction mechanics, evidence economy, and late-case twists.

Players believe the AI mattered when they can see the village, crew, or map react to earlier choices.

Generate events tied to faction grudges, scarce resources, and long-term consequences across runs.

Write eight roguelike events for these factions. Include one dilemma, one scarce resource tradeoff, and one long-tail consequence each.

Plan weekly events that remix existing mechanics, nudge social play, and surface overlooked systems.

Generate a four-week live ops plan for this AI game with event theme, player goal, reward logic, and reuse of existing assets.

Drop in a screenshot and get a harsh but useful review focused on clarity, hierarchy, and conversion friction.

Act as a top-tier conversion designer. Critique this page for message clarity, information hierarchy, CTA friction, and trust signals. Then propose a tighter hero section.

This prompt turns a pile of notes, bugs, and feature asks into one ranked plan the team can act on Monday morning.

You are my product chief of staff. Review the notes below, cluster them into themes, rank by urgency and revenue impact, and produce a 7-day execution plan with tradeoffs.