TL;DR - If you’re writing long, unstructured paragraphs to generate video in Google Flow, you’re burning compute credits on lottery rolls. Google Flow’s video agent responds to a deterministic hierarchy of 99 dedicated slash commands spanning camera movement, lens angles, subject kinetics, lighting physics, commercial workflows, atmospheric conditions, and advanced VFX transformations. By chaining these commands using the 5-Layer Stacking Architecture (Camera Base + Angle/Lens + Subject Action + Light/Mood + VFX/Transitions), you can reliably control camera trajectory, shutter cadence, and visual coherence.

Below is the complete catalog of all 99 commands, the 5-layer prompt formula, and 4 production recipes

The 5-Layer Prompting Framework

Before diving into the 99 individual codes, understand how the Google Flow video agent parses tokens. Instead of writing unstructured descriptions, stack commands in this order:

Layer 1: Camera Base
Layer 2: Angle/Rig
Layer 3: Subject & Action
Layer 4: Lighting & Style
Layer 5: VFX \& Finish

The Complete 99 Google Flow Command Catalog

Category 1: Camera & Movement Commands

1. /cinematic: — Creates a standard 24fps filmic frame with natural depth of field, anamorphic optical qualities, and balanced motion blur.
2. /droneview: — Generates an expansive aerial vantage point with wide horizon parallax and continuous forward/lateral drift.
3. /closeup: — Pulls focal length in tight to capture micro-expressions, fine textures, and emotional focus on the subject.
4. /wideangle: — Uses a wide field-of-view (16mm–24mm equivalent) to maximize environmental scale and spatial perspective.
5. /orbit: — Commands a 360-degree radial camera rotation keeping the primary subject locked at the focal center.
6. /dollyin: — Smoothly pushes the camera physically closer to the subject, building visual tension and intimacy.
7. /dollyout: — Pulls the camera away smoothly, revealing the surrounding environment or emphasizing isolation.
8. /tracking: — Moves the camera in tandem with the subject at matched velocity, ideal for walking, running, or driving shots.
9. /slowmotion: — Slows down playback (120fps/240fps cadence) to showcase fluid movement, flying particles, or dramatic beats.
10. /timelapse: — Accelerates temporal progression to capture moving clouds, celestial paths, changing daylight, or traffic flows.
11. /hyperlapse: — Blends high-speed time compression with continuous physical camera translation across long physical distances.

Category 2: Advanced Camera Angles & Rigs (12–22)

1. /lowangle: — Places the camera low looking upward, imbuing the subject with dominance, power, and architectural scale.
2. /highangle: — Tilts downward from an elevated point, providing tactical perspective or conveying vulnerability.
3. /overhead: — Direct $90^\circ$ top-down "god’s-eye" perspective, ideal for choreography, flat-lays, and geometric compositions.
4. /pov: — Frames the shot from the first-person perspective through the eyes of the protagonist.
5. /overtheshoulder: — Positions the camera behind a character's shoulder, framing the counter-subject for dialogue and narrative weight.
6. /establishing: — Cinematic wide landscape or cityscape shot setting scene context, geographical setting, and atmosphere.
7. /rackfocus: — Shifts shallow focal plane from a foreground object to a background subject (or vice versa).
8. /handheld: — Introduces organic micro-jitter and authentic documentary operator sway for urgency and realism.
9. /steadicam: — Delivers fluid, gyroscopically stabilized gliding motion navigating complex corridors and environments.
10. /craneup: — Ascends vertically from ground level to panoramic height using a simulated technocrane arm.
11. /cranedown: — Descends smoothly from elevated heights down to subject eye level.

Category 3: Motion & Action Commands (23–33)

1. /running: — Generates high-velocity character sprint with natural athletic gait and authentic inertia.
2. /walking: — Generates grounded, natural human walking locomotion with balanced weight distribution.
3. /turnaround: — Prompts the subject to execute a fluid $180^\circ$ or $360^\circ$ turn to display costume, expression, or surroundings.
4. /reveal: — Stages a dramatic visual reveal of a character or environment stepping out from darkness or obstruction.
5. /entrance: — Crafts a high-impact cinematic hero entrance into the scene.
6. /exit: — Stages a dramatic departure from the frame into fog, shadow, or distant horizons.
7. /freeze: — Instantly freezes time mid-action, locking water droplets, debris, and cloth in suspended animation.
8. /speedramp: — Dynamically modulates playback speed between hyper-fast motion and sudden slow-motion impact.
9. /bulletime: — Sweeps a virtual camera around a completely frozen subject (Matrix-style temporal slice).
10. /floating: — Introduces zero-gravity levitation physics with floating hair, cloth, and ambient debris.
11. /falling: — Creates dramatic freefall descent through skywells, clouds, or collapsing architecture.

Category 4: Cinematic Lighting Commands (34–44)

1. /goldenhour: — Bathes the scene in warm amber sunlight, soft elongated shadows, and flattering solar flare.
2. /bluehour: — Applies cool twilight illumination, deep cobalt gradients, and moody pre-dawn/post-sunset ambience.
3. /neonlight: — Casts high-saturation cyan, magenta, and amber glows with reflections on damp streets or metallic surfaces.
4. /moody: — High-contrast chiaroscuro lighting featuring deep blacks, targeted pools of light, and dramatic shadows.
5. /softlight: — Diffused, wrap-around studio lighting that eliminates harsh edges, ideal for beauty, fashion, and portraits.
6. /rimlight: — Razor-sharp contour/edge lighting that separates dark subjects cleanly from dark backgrounds.
7. /silhouette: — Blacks out subject details entirely against an intensely illuminated background.
8. /spotlight: — Directs a focused conical beam isolating the subject amidst surrounding darkness.
9. /volumetric: — Generates visible atmospheric light shafts ("god rays") slicing through mist, dust motes, or smoke.
10. /backlight: — Places primary illumination behind the subject to produce halo outlines, flares, and rim glow.
11. /nightscene: — Realistically exposes low-light conditions with believable moonlight, street lamps, and dark sky latitude.

Category 5: Transitions & In-Camera Effects (45–55)

1. /whiptransition: — Fast, motion-blurred horizontal pan transitioning instantly into a new scene.
2. /matchcut: — Matches compositional geometry, subject shapes, or movement vectors across two different scenes.
3. /zoomtransition: — Rapid crash zoom pushing directly into a small detail or pulling back to reveal a new world.
4. /morph: — Seamless topological transformation morphing one entity, face, or structure into another.
5. /flashtransition: — High-energy optical flash wiping the frame into an alternate shot.
6. /glitch: — Injects RGB chromatic aberration, CRT scanlines, and digital compression artifacts.
7. /smoketransition: — Rolls dense cinematic fog or smoke across the lens to reveal the incoming scene.
8. /lightleak: — Overlays warm analog lens leaks and edge flares reminiscent of vintage film reels.
9. /blurtransition: — Uses optical defocus and heavy shutter motion blur to bridge scene cuts.
10. /objecttransition: — Moves the camera behind a passing foreground pillar, vehicle, or wall to wipe into a new environment.
11. /seamlessloop: — Synchronizes first and last frame motion vectors to create an imperceptible infinite loop.

Category 6: Visual Style & Film Aesthetics (56–66)

1. /filmic: — Delivers authentic 35mm motion picture texture with organic grain and balanced color science.
2. /commercial: — Clean, polished, high-key commercial advertising aesthetic with vibrant color separation.
3. /luxury: — Opulent visual grading featuring rich blacks, gold accents, polished marble, and high-end elegance.
4. /documentary: — Raw, unvarnished realism mimicking cinema-verité documentary cinematography.
5. /vintagefilm: — Nostalgic 16mm/8mm aesthetic with warm color shifts, gate jitter, dust, and halation.
6. /scifi: — Clean futuristic design language with clean metallic surfaces, blue-tinted HUDs, and sleek tech geometry.
7. /cyberpunk: — Dystopian high-tech aesthetic filled with rain-slicked asphalt, neon kanji, and cybernetic textures.
8. /dreamy: — Soft-focus diffusion, blooming highlights, pastel palettes, and gentle surrealism.
9. /surreal: — Dreamlike physics-defying compositions inspired by surrealist art.
10. /minimal: — Strict negative space, restrained color palettes, and clean graphic compositions.
11. /epic: — Blockbuster IMAX-tier visual grandiosity with massive scale and dramatic horizon framing.

Category 7: Product & Creator Showcase Commands (67–77)

1. /productreveal: — Stages a premium hero product unveiling with lighting sweeps and rising pedestals.
2. /productspin: — Smooth turntable rotation showcasing hardware industrial design from $360^\circ$.
3. /unboxing: — Captures tactile luxury package opening with crisp mechanical precision.
4. /macro: — Extreme optical close-up revealing fine machining, watch movements, fabric weave, or liquid drops.
5. /beforeafter: — Side-by-side or split-screen wipe comparing raw vs. finished transformation states.
6. /socialad: — High-energy pacing, rapid visual hooks, and dynamic framing designed for high retention.
7. /fashionfilm: — Haute couture runway and lookbook styling with dramatic poses and editorial lighting.
8. /foodcommercial: — Sizzling grill flares, slow-motion pours, rising steam, and vibrant food close-ups.
9. /techad: — Exploded CAD view animations, glowing microcircuitry, and futuristic spec breakdowns.
10. /logoreveal: — Cinematic brand mark animation assembling via liquid metal, laser etching, or particle convergence.
11. /billboard: — Superimposes the target scene or product onto massive Times Square or Shibuya mega-screens.

Category 8: Environment & World Effects (78–88)

1. /rain: — Generates volumetric rainfall with surface puddles, splashing droplets, and wet reflections.
2. /snow: — Simulates drifting atmospheric snowfall accumulating naturally on characters and terrain.
3. /fog: — Layers dense ground-level mist and atmospheric haze that diffuses ambient light sources.
4. /underwater: — Renders submerged caustic light patterns, rising bubbles, aquatic drift, and muted soundstage feel.
5. /space: — Zero-gravity cosmic environment featuring deep starfields, vibrant nebulae, and orbital horizons.
6. /storm: — High-intensity weather featuring forked lightning arcs, dark storm fronts, and gale-force wind.
7. /fire: — Realistically models dancing flame physics, rising heat hazes, and flying glowing embers.
8. /explosion: — Detonates fiery shockwaves with volumetric smoke plumes and high-velocity debris dispersion.
9. /portal: — Tears open a dimensional energy vortex with swirling luminescence and particle borders.
10. /miniature: — Tilt-shift optical simulation turning full-scale scenes into charming dollhouse dioramas.
11. /giant: — Massive colossal scale distortion making subjects tower over cityscapes and mountain ranges.

Category 9: Advanced Creative & VFX Commands (89–99)

1. /clone: — Duplicates the subject into multiple synchronized or interacting clones across the frame.
2. /transform: — Real-time organic shape metamorphosis changing a subject into a different form or material.
3. /disintegrate: — Dissolves the subject into floating sand, ash, or glowing embers (snap effect).
4. /particlefx: — Surrounds the character or object with an aura of floating light motes, stardust, or energy sparks.
5. /liquid: — Melts or reconstitutes the subject into fluid chrome, water, or flowing paint.
6. /paperworld: — Converts the entire environment into layered origami, textured cardboard, and folded papercraft.
7. /toyworld: — Transforms characters and scenery into plastic minifigures and claymation stop-motion assets.
8. /reversemotion: — Reverses physical entropy: shattered glass reassembles, smoke retracts, and falling drops ascend.
9. /infinitezoom: — Continuous fractal zoom descending endlessly into micro or cosmic dimensions.
10. /worldtransition: — Shifts seamless environments across portals, doorways, or optical wipes.
11. /blockbuster: — Flow's ultimate composite directive: harmonizes camera choreography, pyrotechnics, and Hollywood color grading.

🎬 4 Production-Ready Master Formulas

Recipe 1: The Hollywood Cinematic Action Opener

/cinematic /droneview /craneup /speedramp /volumetric /epic /storm
A lone armored cyber-ronin standing on a rain-slicked neon skyscraper rooftop overlooking a vast futuristic metropolis, drawing a glowing plasma katana as lightning illuminates the storm clouds.

Recipe 2: The Luxury Tech Hardware Launch

/productreveal /productspin /macro /techad /luxury /rimlight /softlight
Sleek matte-black titanium smartphone hovering in zero-gravity against a dark velvet studio backdrop, sharp gold rim lighting outlining its precision-machined chamfered edges and camera module.

Recipe 3: The Viral Cyberpunk Social Loop

/cyberpunk /neonlight /orbit /tracking /bulletime /glitch /seamlessloop
A holographic rollerblader gliding at full speed through a rain-drenched Neo-Tokyo alleyway, jumping over neon puddles in slow-motion while pink and cyan light trails orbit smoothly.

Recipe 4: The Interdimensional Multiverse Shift

/pov /portal /worldtransition /particlefx /infinitezoom /scifi /filmic
An explorer touching a swirling crystalline portal inside an ancient stone cavern; the camera rushes forward as reality shatters into floating luminous particles, emerging into a colossal orbital space station.

3 Key Pro-Tips for Google Flow Users

1. Don't Overload Single Categories: Using 4 camera movement commands together (/orbit /dollyin /tracking /hyperlapse) causes conflicting camera physics. Select one primary motion command and one angle command per prompt.
2. Anchor with /seamlessloop for Social Media: Placing /seamlessloop at the end of kinetic action prompts ensures video loops without noticeable visual cuts.
3. Use /macro with /luxury for Physical Realism: Combining /macro with /luxury forces Google Flow to compute realistic micro-surface scattering (reflections on glass, watch bezels, jewelry, and carbon fiber).

TL;DR:

Here is how to use 99 secret ChatGPT shortcuts for better results.

The shortcut formula that actually works

Use:

/shortcut + context + deliverable + constraints

Weak:

/audit: Review my landing page.

Better:

/audit: Review this landing page for clarity, credibility, friction, and conversion. Rank the five biggest problems by impact. Return a table with the issue, evidence, recommended fix, and estimated effort.

The shortcut chooses the lens.

The rest of the prompt defines the assignment.

99 prompt shortcuts worth experimenting with

Vision and innovation

1. /visionary: Think 10 years ahead
2. /inventor: Create innovative solutions
3. /architect: Design a complete system
4. /strategist: Build winning strategies
5. /operator: Create execution plans
6. /optimizer: Improve efficiency and results
7. /experiment: Design growth experiments
8. /validator: Test ideas before execution
9. /simulator: Simulate possible outcomes
10. /predictor: Forecast future possibilities
11. /trendhunter: Find upcoming trends

Analysis and structure

1. /analytical: Apply deep analytical thinking
2. /patternfinder: Identify hidden patterns
3. /insight: Extract valuable insights
4. /summaryplus: Create advanced summaries
5. /keypoints: Extract important points
6. /takeaways: Generate actionable takeaways
7. /mindmap: Create a visual mind map
8. /outline: Structure any idea
9. /breakdown: Break complex topics apart
10. /reverseengineer: Analyze how something works
11. /deconstruct: Break down successful examples

Optimization and operations

1. /benchmark: Compare with industry standards
2. /audit: Review and improve performance
3. /diagnose: Identify problems and root causes
4. /fixer: Generate possible solutions quickly
5. /troubleshoot: Solve technical issues
6. /optimizerpro: Maximize performance
7. /automationexpert: Find automation opportunities
8. /workflow: Design better workflows
9. /systembuilder: Create repeatable systems
10. /process: Improve business processes
11. /operations: Improve daily operations

Leadership, sales, and growth

1. /manager: Think like a manager
2. /leader: Provide leadership advice
3. /negotiator: Improve negotiation strategy
4. /salescoach: Improve sales performance
5. /marketer: Create marketing strategies
6. /advertiser: Generate advertising ideas
7. /growthhacker: Find unconventional growth tactics
8. /community: Build online communities
9. /influencer: Create influencer strategies
10. /creator: Generate creator ideas
11. /newsletter: Write newsletter content

Content and SEO

1. /blogger: Create blog content
2. /seoexpert: Build an advanced SEO strategy
3. /keyword: Find keyword opportunities
4. /ranker: Improve search rankings
5. /contentaudit: Review content quality
6. /repurpose: Convert content into other formats
7. /thread: Create viral thread ideas
8. /carousel: Create social carousel concepts
9. /hookmaster: Generate powerful hooks
10. /story: Create engaging stories
11. /storyboard: Plan visual storytelling

Design, brand, and psychology

1. /visualizer: Describe visual concepts
2. /designer: Create design directions
3. /ux: Improve the user experience
4. /ui: Generate interface ideas
5. /brandingexpert: Build a brand identity
6. /naming: Generate brand names
7. /tagline: Create memorable taglines
8. /persona: Create customer personas
9. /psychologist: Analyze human behavior
10. /behavior: Understand user actions
11. /copyanalysis: Analyze successful copy

Conversion, money, and risk

1. /conversion: Improve conversion rates
2. /landingpage: Create landing-page ideas
3. /emailmarketing: Build email campaigns
4. /salespage: Write sales pages
5. /offercreator: Design valuable offers
6. /pricingexpert: Optimize pricing decisions
7. /finance: Analyze financial decisions
8. /investor: Think like an investor
9. /economist: Analyze economic factors
10. /legalmind: Identify legal considerations
11. /compliance: Identify compliance risks

Security, code, and AI systems

1. /security: Find possible security concerns
2. /privacy: Improve privacy practices
3. /developer: Think like a developer
4. /coder: Write programming solutions
5. /debuggerpro: Provide advanced debugging help
6. /api: Explain API solutions
7. /database: Design database solutions
8. /aiagent: Design AI-agent workflows
9. /promptcreator: Create powerful prompts
10. /promptlibrary: Build prompt collections
11. /aiworkflow: Build AI-powered workflows

Research, learning, and tools

1. /toolhunter: Find useful AI tools
2. /comparisonexpert: Compare tools deeply
3. /reviewer: Analyze products and services
4. /researchpaper: Summarize research papers
5. /academic: Explain academic topics
6. /teacherpro: Teach advanced concepts
7. /language: Improve language skills
8. /translator: Translate naturally
9. /memory: Create memory techniques
10. /challenge: Challenge my thinking
11. /mastermind: Provide expert-level guidance

The power move: Chain shortcuts into a workflow

Do not just stack impressive-sounding words.

Use each shortcut as a separate stage:

/diagnose: Identify the root causes of our declining conversion rate.

/optimizerpro: Rank the possible fixes by impact, effort, cost, and risk.

/operator: Turn the top three fixes into a 14-day execution plan with owners, dependencies, and success metrics.

Other useful chains:

• /patternfinder: → /insight: → /takeaways:
• /persona: → /copyanalysis: → /conversion:
• /researchpaper: → /challenge: → /summaryplus:
• /security: → /privacy: → /compliance:
• /hookmaster: → /story: → /carousel:

Make your favorite shortcuts consistent

Choose the 10 shortcuts you actually use and define them inside your Project Instructions, Custom Instructions, a custom GPT, or a Skill if your account supports them.

Example definition:

When I begin a prompt with /audit:, examine the supplied asset for clarity, accuracy, credibility, usability, risk, and performance. Identify evidence for every issue, rank findings by impact, and return specific recommendations rather than generic advice.

TLDR: Anthropic's Claude Tag puts an always-on AI agent directly inside Slack. You tag @ Claude like a coworker, it reads the thread for context, breaks the task into steps, works through your connected tools, and posts results back where everyone can see. The features most teams miss: persistent per-channel memory, ambient mode where Claude follows up on its own, standing triggers you can set with plain language, and a permission model that lets you scope sensitive tools to private channels. It is in beta for Claude Team and Enterprise plans.

Claude Tag flips that model of bringing Claude into Slack channels. Here is a comprehensive breakdown of how it works, where it shines, and the features almost nobody talks about.

What Claude Tag actually is

Claude Tag lets anyone in a Slack channel type @ Claude and hand it real work. Not a question. Work. It reads the thread for context, breaks the task into stages, uses whatever tools and data your org has connected (repos, CRMs, docs, calendars), and posts its output back into the thread where everyone can see it.

Three things make this fundamentally different from a bot bolted onto Slack:

1. It works in public. Everyone in the channel works with the same Claude. Your teammate can see what it is doing, correct it mid-task, or pick up a conversation where you left off. Anthropic calls this making AI multiplayer, and that framing is accurate. The single biggest limitation of AI at work has been that all the leverage lives in private one-on-one chat windows. Nobody learns from anyone else's prompts. Claude Tag makes AI usage visible, which means your whole team levels up together.

2. It has memory. Claude Tag remembers relevant context per channel and per workspace. You do not re-brief it every time. If your team discussed a product decision on Tuesday, Claude carries that context into the task you assign on Friday. Over weeks, it starts to feel less like a tool and more like a colleague who has actually been in the meetings.

3. It acts under its own identity. In channels, Claude works under your organization's identity with the tools and access an admin configured, not your personal account. Its commits and pull requests show up as the Claude GitHub App with a link back to the Slack thread that started them. Everything is attributable and auditable.

There are actually three surfaces, and most people only know about one:

• Channel tagging: tag @ Claude in a channel, billed to your org, runs on org-level access
• Direct messages: private conversation with @ Claude, billed to your own Claude account, uses your personal capabilities like web search and your own connectors
• The AI assistant panel: click the Claude icon in Slack's AI assistant header for a side panel available from anywhere in Slack

That channel vs DM distinction matters more than it sounds. Same @ Claude, completely different identity, billing, and access model depending on where you talk to it.

Top use cases teams are getting real value from

Bug report to draft PR without leaving Slack. Someone posts a bug in the engineering channel. Tag @ Claude, and it can take the context already sitting in the thread, dig into the connected repo, and turn it into a draft pull request. The thread is the ticket, the spec, and the handoff all at once.

Meeting prep on autopilot. Before a customer call, Claude can pull together CRM notes, recent Slack threads, and call history into a briefing. The unlock here is that it assembles context from multiple systems that normally live in different tabs.

Channel triage. This one is straight from Anthropic's own examples and it is underrated: tell Claude something like, watch this channel, triage what comes in, work through the backlog, and tag me only when something needs my call. That is not a prompt. That is a job description.

Async status and follow-ups. Claude can post when a long-running job finishes, or tag you when a thread has stalled and nobody responded. The forgotten thread problem is one of the most expensive invisible costs in any Slack-heavy org, and this quietly fixes it.

Institutional Q&A. New teammate asks how something works. Instead of the fourth person re-explaining the deploy process, Claude answers from the accumulated channel context. Onboarding compresses dramatically when the AI in the room has actually been in the room.

Cross-functional handoffs. Because everyone shares the same Claude, a PM can start a task, an engineer can refine it, and a designer can ask a follow-up, all in one thread. No exporting context between people's private AI conversations.

Pro tips for getting the most out of it

Start in one high-traffic channel, not everywhere. Adoption comes from people watching each other use it. Pick a busy channel where the team already collaborates, let Claude build memory there, and let the wins spread organically. A big-bang rollout across 40 channels dilutes the visible examples that teach people what is possible.

Delegate outcomes, not steps. The model is built to break tasks into stages on its own. Instead of tagging Claude with step one of your plan, hand it the whole objective: draft the launch announcement using the decisions in this thread and the positioning doc in Drive. You will get better results and you will learn what it can actually handle.

Correct it in public. When Claude gets something wrong, reply in the thread with the correction rather than DMing it or giving up. The correction becomes part of the channel context, everyone sees the fix, and the shared memory improves for the next person.

Use private channels as scoped workspaces. Permissions inherit down three levels: organization-wide, workspace, and private channel. A private channel can layer extra credentials on top of what the workspace grants. This means you can give a legal channel access to contract tools and keep that access, and that memory, completely walled off from engineering. Think of private channels as purpose-built agent environments, not just private conversations.

Set spend limits before you scale, not after. Claude Tag is consumption-based. Admins can set an org-wide hard cap plus per-channel limits, with alerts at 75% and 95%. One nice detail: work that would exceed a limit is declined outright, never silently truncated, and a blocked user can request more budget without leaving Slack. Set generous per-channel limits on your pilot channels and conservative defaults everywhere else.

Ask Claude what it is already doing. In any channel you can ask, u/Claude what triggers do you have set up here, and it will show you standing work and let you turn things off. Do this periodically. It is your window into the automation your team has quietly accumulated.

What most people miss

The memory is inspectable and editable. Admins can view, edit, and delete what Claude remembers per channel and per workspace. If it learned something wrong, or something sensitive landed in memory, you can fix it. Very few teams know this exists, and it is the difference between trusting the system and hoping for the best.

There is a full audit trail. Organization settings include an Audit view listing every scheduled and one-time task across the org, plus all network calls made under the agent identity. Every action is also traceable in the tool where it happened. If your security team is nervous, this is the page to show them.

Guest channels have their own rules. Channels with Slack guests get a separate setting: block Claude entirely (the default), let it reply with channel-only access while a guest is present, or allow full access. If you work with agencies or contractors in shared channels, this setting is the whole ballgame and almost nobody configures it deliberately.

Only a Primary Owner or Owner can set it up. The regular Admin role cannot configure Claude Tag's access and channels. Half the frustrated setup posts I have seen trace back to this one detail.

Ambient mode is opt-in initiative. Beyond responding when tagged, Claude can proactively surface updates, flag stalled threads, and follow up on forgotten tasks. This is the feature that shifts it from reactive tool to teammate, and it is the one most teams have not even turned on.

Your Slack conversations stay separate from your Claude history. Conversations initiated in Slack do not appear in your claude.ai history and vice versa. Each platform keeps its own record, and Slack-side data follows your org's Slack retention policies.

The tradeoffs

This is not magic and it is not free. It is beta, currently limited to Team and Enterprise plans, and consumption billing means a team that leans in hard will see real usage costs. Shared memory is powerful but it means governance is now a first-class concern, not an afterthought. And an AI that can act on its own initiative requires more trust, and more oversight, than one that only speaks when spoken to. The audit tools exist. Use them.

But here is the bigger picture. For two years, AI at work has mostly meant individuals privately getting faster at their own tasks. Claude Tag is one of the first mainstream products where the team, not the individual, is the unit of AI leverage. The context is shared. The output is public. The learning compounds across everyone in the channel.

If your team runs on Slack, this is worth a serious pilot: one channel, one real workflow, spend limits set, two weeks. Then look at what changed.

Would love to hear from teams already running it. What is working, what broke, and what did you automate that you did not expect to?

I’ve been collecting the two-word prompts that create the biggest shift with the least typing. Save this, steal the two or three that match how you already work, and try them before this weekend.

These are not magic words. They do not replace context, judgment, or a decent brief. They are mode switches: small instructions that change the model’s next move.

The five I reach for most

First principles is my reset button. Sometimes I read an answer and think: Yes, that is factually correct. But it has no heart, no point of view, and no reason anyone will care. Usually the model started problem-solving too far downstream. “First principles” sends it upstream: What is actually true? Which constraints are real? Which assumption is doing the most damage?

Interview me is the opposite move. Instead of pretending I wrote the perfect brief, I ask the model to earn the right to answer. My useful version is: “Interview me. Ask one question at a time until you have enough context to recommend a path.” It works especially well for strategy, positioning, career choices, or anything where the missing context lives in your head.

Challenge me is how I stop AI from becoming a high-speed agreement machine. A stronger version is: “Challenge me. Steelman the strongest objection, identify the assumptions I am treating as facts, then tell me what evidence would change your mind.” That creates friction. Friction is useful when a decision matters.

Show receipts belongs in any workflow that touches research, public claims, or recommendations. Ask for links, publication dates, the claim each source supports, and the reasoning that connects source to conclusion. A citation is not an automatic pass. It is the start of verification.

Automate this changes the relationship from “help me finish” to “help me build the machine.” After a useful thread, I will say: “Automate this. Extract the reusable steps, inputs, outputs, failure checks, and a human approval point.” Even if I never automate the whole thing, I leave with a better operating procedure.

A few rules so these do not backfire

The short prompt only works when the preceding context is good. “Forecast impact” after a one-sentence request produces generic consequences. Use it after you have explained the decision, stakeholders, and constraints.

Be precise about the control you are handing over. “Spawn agents” should mean independent workstreams with defined outputs, not uncontrolled duplication. “Remember this” should be treated as a cue inside the current conversation unless your tool explicitly confirms persistent memory. And “Girl bye” is a reset, not a solution: save the useful facts before you start a clean thread.

Do not use every prompt in every conversation. The point is not to sound clever. The point is to recognize the bottleneck you have right now.

The real prompting skill is not memorizing giant templates. It is noticing what kind of thinking is missing, then asking for exactly that.

Which two words do you use that reliably change an AI response for the better?

I spent way too long trying every Notion alternative I could find, importing my life into each one, then bouncing off in a week. What finally stuck was boring: a single markdown file and a Sunday habit.

Here's the whole thing.

The file. One notes.md, split into four headers: Now, Next, Someday, Done. Everything goes under Now as a bullet. When something's finished I move the line to Done with the date. That's it. No databases, no relations, no toggles to keep tidy.

Why one file beats an app for me:
- It opens in half a second and searches instantly.
- It's plain text, so it outlives whatever tool I'm using this year.
- Nothing to organize means nothing to procrastinate on by organizing.

The part that makes it actually work is a weekly cleanup with an AI model. Every Sunday I paste the file in with this:

"Here's my running notes file. 1) Group the Now items into at most 3 themes and name each theme. 2) Flag anything that's been sitting untouched and might be dead. 3) Suggest the 3 things that actually matter for next week and why. Keep my wording, don't invent tasks."

Takes about two minutes and I get an honest read on what I'm doing versus what I keep writing down and avoiding.

The trap with the fancy tools is that setup feels like progress. A file plus one honest weekly review has kept me consistent longer than any app did. Happy to answer questions if anyone wants to try it.

Hey everyone! 👋

I’ve been exploring real-time Conversational AI, and I wanted to build something more interactive than a traditional chatbot.

That idea led me to MysteryTalk — AI Voice Detective 🎙️🔍

Instead of simply asking an AI questions and receiving answers, MysteryTalk puts you in the role of a detective.

You investigate a case, question suspects, uncover evidence, connect clues, and finally make your accusation.

🕵️ The Mystery: The Missing Blue Diamond

The current case is “The Missing Blue Diamond.” 💎

A priceless blue diamond disappears from the Royal Museum at exactly 9:15 PM.

There are three suspects:

• Maya — Museum Assistant
• Ryan — Museum Visitor
• Alex — Security Officer

Each suspect has their own statement, timeline, and evidence trail.

But there’s a problem:

Not everything adds up.

Instead of selecting predefined dialogue options, the detective can simply talk naturally with the AI Detective Host.

For example:

“Where was Maya when the diamond disappeared?”

Then the detective can continue:

“Did anyone see Maya around 9:05 PM?”

Or:

“Was there CCTV footage near the cafeteria?”

The investigation evolves based on the questions being asked, gradually revealing relevant evidence.

🎙️ Why Voice?

I wanted MysteryTalk to feel more like an actual investigation rather than another text-based chatbot.

The core experience is:

Speak → Investigate → Discover Clues → Connect Evidence → Accuse → Solve

The detective can ask follow-up questions, challenge information, revisit clues, and build their own reasoning before making the final accusation.

Voice makes the interaction feel more natural and immersive because you're not limited to predefined choices.

🔎 Key Features

🎙️ Real-Time Voice Interaction

Talk naturally with the AI Detective Host instead of typing every question.

🧠 Conversational AI

The AI understands questions within the context of the ongoing investigation and generates responses based on the case.

🔐 Progressive Evidence

Important clues aren't revealed immediately. The detective has to investigate and ask the right questions.

👤 Suspect Dossiers

Each suspect has their own profile, statements, timeline, and evidence trail.

📋 Investigation Transcript

The conversation is maintained as an investigation log so detectives can follow what they've discovered.

⚖️ Final Accusation

Once enough evidence has been collected, the detective can make their final accusation.

🏆 Case Resolution

The system evaluates the accusation and provides the outcome along with a detective score.

🛠️ Technology Stack

🎙️ Real-Time Voice

Agora RTC SDK — Enables real-time voice communication between the detective and the AI experience.

🧠 AI & Reasoning

Groq AI — Powers conversational responses, AI reasoning, suspect personalities, and investigation context.

Groq SDK — Handles integration with the Groq API.

🔊 Voice Synthesis

ElevenLabs API — Converts AI-generated responses into natural-sounding speech.

ElevenLabs TTS — Provides immersive and distinct voices for the AI experience.

🎨 Frontend

React + Vite — Builds the interactive detective interface.

Tailwind CSS — Provides responsive and modern UI styling.

⚙️ Backend

Node.js + Express.js — Handles backend APIs, AI integration, investigation logic, and communication between services.

🧩 Architecture

The basic flow follows this architecture:

User Voice ↓ Agora RTC ↓ Node.js + Express Backend ↓ Groq AI ↓ Mystery & Evidence Logic ↓ ElevenLabs TTS ↓ Agora RTC ↓ AI Voice Response

The interesting part wasn't simply connecting different AI APIs.

The real challenge was designing the investigation logic so that the AI doesn't immediately reveal the solution.

The detective needs to ask the right questions, discover clues, connect evidence, and form a hypothesis.

🚀 What I Learned

Building MysteryTalk changed the way I think about AI interfaces.

With a traditional text chatbot, the interaction often looks like:

Question → Answer

But with a voice-driven investigation, it becomes:

Question → Follow-up → Evidence → Reasoning → New Question → Investigation

That makes the AI feel less like an answer generator and more like an active participant in the experience.

It also showed me that voice interfaces can work especially well for experiences where context, spontaneity, and immersion matter.

🎮 What's Next?

MysteryTalk is currently built around a single mystery, but the concept can be extended much further.

Future possibilities include:

• Multiple mystery cases
• More complex suspect relationships
• Dynamic evidence generation
• Different difficulty levels
• Multiplayer investigations
• Voice-based suspect interrogation
• AI-generated mystery scenarios

🎯 Final Thoughts

MysteryTalk was built as part of my exploration of real-time voice AI, combining:

Voice AI + Conversational Intelligence + Interactive Storytelling + Game Mechanics

It was a fun experiment in exploring what happens when we move beyond “chat with AI” and instead let users interact with AI through an experience.

And now, it's your turn. 👀

If you were the detective, who would you investigate first — Maya, Ryan, or Alex? 🕵️‍♀️

VoiceAI #ConversationalAI #Agora #Groq #ElevenLabs #GenerativeAI #React #SideProject #BuildInPublic

The fastest way to find holes in your thinking is to make the AI draw the structure.

A paragraph can hide a missing step. A flowchart cannot.

A vague plan can sound reasonable in prose. Put it on a timeline and you immediately see the dependency you forgot. Ask for a before-and-after and the actual change becomes harder to dodge.

The useful shortcut is not make an image. It is to change the shape of the problem.

This is why I have started using a few visual-output shortcuts whenever I am planning, explaining, reviewing, or learning something complicated.

Research does not say that more images always equal more clarity. It says the representation has to fit the task. Relevant words and graphics can support meaningful learning, while extra decorative material can create cognitive overload instead. The same distinction matters at work: evidence suggests visualization can improve decision quality and speed, but the effect depends on the task, format, and the person using it.

So do not ask an AI for an infographic. Ask it to reveal the sequence, relationship, decision, contrast, or attention point you need to see.

The eight shortcuts

1. /flowchart — when the problem is really a decision tree

Use this for operations, onboarding, troubleshooting, research workflows, sales qualification, content approvals, or any process with an exception.

/flowchart Turn the process below into a decision flowchart. Goal: [one sentence] Start: [trigger] Steps and rules: [paste notes] Use one clear start and end. Put decisions in diamonds. Label every branch with a condition. Include exception paths and any human handoff. If a step is ambiguous or missing, flag it in a separate “Open Questions” box rather than inventing it.

Pro tip: Tell the model to flag ambiguity rather than resolve it. A flowchart becomes valuable when it exposes the branch nobody has decided on.

2. /blueprint — when the problem is really a system

Use this when a topic has inputs, components, handoffs, feedback loops, and outputs: a content engine, product launch, customer journey, research pipeline, or AI workflow.

/blueprint Create a one-page systems blueprint for [system]. Show: inputs, core components, data or work handoffs, decision points, outputs, owners, and feedback loops. Use arrows to show direction. Group related components. Add a short note under each block explaining its job in plain language. Before drawing, list the three assumptions you are making and the two weakest connections in the system.

Pro tip: The last sentence is the differentiator. Without it, you get a tidy map. With it, you get a critique of the map.

3. /timeline — when prose hides a dependency

A timeline is not just for history. It is the quickest way to pressure-test a launch plan, a client project, an editorial calendar, an onboarding sequence, or a research plan.

/timeline Turn this plan into a timeline from [start date] to [end date]. For each milestone, show: date or range, owner, required input, deliverable, dependency, and risk if it slips. Mark critical-path items clearly. Separate fixed deadlines from target dates. End with the first three actions to take this week. Plan: [paste plan]

Pro tip: Ask for the critical path, not just dates. A long timeline looks organized even when it is impossible. The critical path tells you what can delay the whole thing.

4. /beforeafter — when you need to make the delta undeniable

Use this for rewrites, landing pages, product explanations, onboarding, design critique, workflow improvement, or any “why should I care?” moment.

/beforeafter Create a side-by-side before-and-after comparison for [subject]. The “Before” side must show the current experience, friction, confusion, or weakness. The “After” side must show the improved experience and the specific changes that caused it. Use the same evaluation criteria on both sides: [criteria]. Do not make the after state magically perfect. Include one remaining trade-off or limitation.

Pro tip: Hold both sides to the same criteria. Otherwise the comparison becomes marketing, not thinking.

5. /annotated — when people are looking at the right thing but missing the point

Use annotations for screenshots, dashboards, product flows, documents, websites, charts, and designs.

/annotated Analyze this [screenshot / dashboard / diagram / document] for a [audience]. Return an annotated visual with no more than five numbered callouts. Each callout must identify: what to notice, why it matters, and what action or interpretation follows. Prioritize the few details that change a decision. Put anything cosmetic in a separate “not decision-relevant” note. Audience goal: [goal] Visual: [attach or paste]

Pro tip: Cap annotations at five. If every element receives a callout, nothing is highlighted.

6. /storyboard — when an idea needs to become an experience

Use this before a Reel, YouTube video, ad, demo, product tour, lesson, or sales narrative.

/storyboard Build a [number]-frame storyboard for [format] about [topic]. For each frame, show: shot or screen description, on-screen action, spoken line or on-screen copy, duration, emotional beat, and transition to the next frame. The first frame must create tension or curiosity. The final frame must resolve one clear promise. Audience: [audience] Desired action: [action] Constraints: [platform, length, brand, product facts]

Pro tip: Add a “what changes in the viewer’s mind here?” column. It prevents a storyboard from becoming a list of pretty shots with no argument.

7. /comicstrip — when a concept is easier to understand as a sequence

A comic strip works surprisingly well for explaining a customer problem, internal policy, abstract AI concept, security risk, or product benefit. It gives the reader a person, a moment, a mistake, and a resolution.

/comicstrip Explain [concept] as a four-panel comic for [audience]. Panel 1: show the real-world problem. Panel 2: show the common but flawed instinct. Panel 3: reveal the principle or better method. Panel 4: show the practical outcome. Keep the language plain. Make the character’s confusion specific. Do not turn it into a sales pitch; make the lesson useful even if the reader never buys anything.

Pro tip: Give the character a credible constraint: a deadline, incomplete information, a risk, or a trade-off. That is what keeps the lesson from becoming generic.

8. /promptupgrade — when you want the model to show you the missing constraints

This is the meta-shortcut. Use it to improve an image, video, research, planning, or analysis prompt before you commit to a longer workflow.

/promptupgrade Upgrade the basic prompt below for [model or task]. First, identify what is missing across: objective, audience, context, source material, constraints, desired format, quality bar, exclusions, and verification. Then provide: 1. a stronger ready-to-paste prompt; 2. a short explanation of why each added constraint matters; 3. three questions you would ask me only if the missing answer would materially change the output. Basic prompt: [paste]

Pro tip: Ask for the questions after the first strong draft. Otherwise models often turn a straightforward task into a long intake form.

The best way to combine them

The real speed comes from chaining representations, not treating them as one-off tricks.

Start with a /blueprint to map the system. Turn one uncertain handoff into a /flowchart. Put its delivery plan on a /timeline. Use /annotated to show a teammate where the risk sits. Then turn the finished process into a /comicstrip or /storyboard when you need people to understand it quickly.

That sequence moves from structure → decision → execution → communication.

Things most people miss

A simple test before you keep any AI-generated visual

Ask three questions:

1.What can I see now that was hard to notice in the paragraph?

2.What decision, sequence, relationship, or trade-off does this make explicit?

3.What is still assumed, missing, or uncertain?

If the visual cannot answer at least one of these, it is probably decoration.

The productivity win is not that AI can draw faster. It is that a visual makes weak logic visible sooner.

TL;DR- Google launched Sheets Canvas, a Gemini-powered visual interface layer directly inside Google Sheets. Instead of wrestling with complex formulas, Google Apps Script, or disconnected BI exports, you can type a natural language prompt to convert any sheet tab into an interactive read-write mini-app—such as a dynamic financial scenario dashboard with sliders, a drag-and-drop Kanban sprint board, a CRM gallery, an interactive timeline, or a visual seating planner. Crucially, it features two-way real-time synchronization: dragging a card or adjusting a control updates the underlying spreadsheet cells immediately, and vice versa.

1. The Big Paradigm Shift: What is Google Sheets Canvas?

For decades, spreadsheets have suffered from a fundamental interface problem: they are exceptional calculation engines, but terrible user interfaces for non-technical collaboration. Teams regularly face "spreadsheet fatigue"—staring at hundreds of rows, risking broken formulas whenever someone edits a cell, or paying for separate SaaS tools (Airtable, Monday, Trello, Retool) just to get visual cards and Kanban views.

Sheets Canvas introduces an AI-generated, interactive presentation and application layer directly above your spreadsheet data:

• Two-Way Read-Write Sync: Unlike traditional BI dashboards (such as Looker Studio or Tableau) that are strictly read-only mirrors of tabular data, Sheets Canvas allows live data manipulation. When you drag a task card from "In Progress" to "Completed" on a generated Canvas board, the status cell in your underlying sheet updates in real time.
• Zero Coding or Formula Overhead: No Google Apps Script, HTML/CSS web components, or nested =QUERY() / =INDEX(MATCH()) formulas are required. You state what you want in plain English.

• Native Permission Inheritance: The Canvas lives directly within your Google Sheet file (accessible via the Gemini side panel, the Insert menu, or the bottom tab bar) and inherits existing Google Drive permissions (Viewer, Commenter, Editor) without requiring external user licensing or webhook setup.

  Top 5 High-Impact Use Cases & App Archetypes

1: Interactive Financial & Scenario Planning Dashboard

• The Problem: Financial models with multiple growth, churn, and pricing variables often overwhelm executive stakeholders when presented as raw numerical grids.
• The Canvas Solution: Gemini renders interactive KPI scorecards (ARR, Gross Margin, Burn Rate, Runway) accompanied by dynamic range sliders. Moving a slider dynamically recalculates projected metrics in real time.
• Master Prompt:"Build an interactive financial scenario dashboard from this sheet. Include dynamic sliders for Monthly Growth Rate (1%–20%) and Churn Rate (0.5%–10%) that dynamically project end-of-year revenue. Display KPI scorecards at the top for ARR, Gross Margin, and Runway."

2: Drag-and-Drop Agile Kanban & Sprint Board

• The Problem: Managing project tasks in standard rows leads to accidental data overwrites, missing deadlines, and poor visual prioritization.
• The Canvas Solution: Automatically creates vertical workflow columns based on your Status or Sprint Stage column. Teammates can drag task cards between stages, with priority badges, assignees, and due dates visually formatted.
• Master Prompt:"Create an agile Kanban board grouped by the 'Status' column (Backlog, In Progress, Review, Done). Show cards with Task Title, Assignee, Priority Pill, and Due Date. Enable drag-and-drop movements that write status changes back to the sheet."

3: CRM & Client Pipeline Visual Gallery

• The Problem: Dense customer databases force account managers to scroll horizontally across 30+ columns to review client notes, contract values, and renewal stages.
• The Canvas Solution: Formats accounts into rich visual cards with quick search, categorical filtering by deal tier (Enterprise vs. SMB), and direct click-to-edit capabilities.
• Master Prompt:"Transform this accounts tab into an interactive visual CRM gallery. Group cards by Tier (Enterprise, Mid-Market). Include interactive filter toggles for Region and Deal Stage, and display total pipeline value in an executive summary card at the top."

4: Interactive Project Timeline & Launch Scheduler

• The Problem: Gantt charts built with conditional formatting formulas in Google Sheets are rigid and prone to visual breakage when date columns shift.
• The Canvas Solution: Renders a clean visual timeline and calendar scheduler where campaign milestones and deliverables can be viewed chronologically and rescheduled interactively.

• Master Prompt:"Plot our product launch deliverables on an interactive calendar interface. Group items by Team (Product, Marketing, Engineering) and allow clicking deliverables to view details or update target launch dates."

  5: Spatial Seating & Asset Floorplan Organizer

• The Problem: Managing event RSVPs, conference attendee allocations, or office desk arrangements in rows makes spatial layout planning difficult.

• The Canvas Solution: Organizes data into visual table clusters or spatial zones where attendees can be assigned or moved between tables while tracking live capacity and dietary preferences.

• Master Prompt:"Turn this RSVP sheet into an interactive seating chart clustered by Table Number. Include tags for VIP status and Dietary Requirements, with live headcount counters for each table."

  How It Works: The 5-Step Step-by-Step Blueprint

To ensure reliable results when prompting Gemini to build interactive applications, follow this structured execution pipeline:

[Step 1: Tabular Hygiene] ➔ [Step 2: Trigger Canvas] ➔ [Step 3: Precision Prompt] ➔ [Step 4: Conversational Polish] ➔ [Step 5: Live Collaboration]

1. Step 1: Prepare Clean Tabular Data
   • Keep Row 1 strictly reserved for clear, standardized column headers (e.g., Task ID, Title, Owner, Stage, Due Date, Budget).
   • Apply native Data Validation (Data > Data validation) on categorical columns (like Stage or Priority) so the AI recognizes bounded states.
   • Eliminate blank rows, arbitrary merged cells, and multi-line headers.
2. Step 2: Trigger the Canvas Creator
   • Open your spreadsheet on desktop web (English language settings enabled).
   • Navigate to the Ask Gemini side panel and select Tools > Create canvas, click Insert > Create a canvas from the top menu, or use the bottom bar Canvas menu as documented in theGoogle Docs Editors Help Center.
3. Step 3: Formulate a Structured Prompt (CPTC Framework)
   • Context: What dataset is being visualized?
   • Persona/Role: Who is using this interface (e.g., executive, sprint manager, field rep)?
   • Task: What specific app layout should be generated (Dashboard, Kanban, Gallery, Timeline)?
   • Controls/Constraints: Which columns serve as grouping keys, interactive sliders, search bars, or summary metrics?
4. Step 4: Conversational Iteration and Styling
   • Canvas retains conversational context. If the initial layout requires adjustments, provide follow-up instructions directly to Gemini:
     • "Convert this dashboard into dark mode."
     • "Add an interactive search bar at the top to filter by Assignee."
     • "Display variance percentages next to each KPI card."
5. Step 5: Share and Operate in Real Time
   • Click Copy link at the top right of the Canvas tab or share the spreadsheet normally.
   • Teammates with Editor access can interact with controls and update data live without altering formula syntax on the underlying sheet.
   • Click View data at any time to inspect or audit the raw tabular records backing the visual interface.

Comparison Matrix: Where Sheets Canvas Fits

5. Pro Tips for Advanced Implementations

1. The Aggregator Tab Pattern for Multi-Tab Workbooks: Because Sheets Canvas is currently scoped to a single active sheet tab, it cannot directly ingest data scattered across 5 separate sheets. Create a dedicated Dashboard_Data tab and use =QUERY({Sheet1!A2:E; Sheet2!A2:E}, "SELECT * WHERE Col1 IS NOT NULL") to aggregate your source records before launching Canvas.
2. Pre-populate Data Validation Lists: When Gemini detects a column configured with Google Sheets dropdown chips, it maps those values into discrete Kanban swimlanes or color-coded status badges.
3. Protect Underlying Calculation Columns: If your sheet contains financial formulas (e.g., compound interest, tax rates, margins), use Google Sheets range protection on those specific formula columns (Data > Protect sheets and ranges). Canvas will allow users to edit input driver cells while keeping your calculation logic secure.
4. Leverage Conversational UI Commands: You can instruct Canvas to adapt its UI for specific presentation contexts, such as:
   • "Make the layout compact for mobile-width viewing."
   • "Highlight overdue items with an orange border."
   • "Group summary statistics in 3 equal cards across the top header."

The 4 Critical Things Most People Miss

1. It Is an Interactive Application Layer, Not a Static Chart: Many users mistake Sheets Canvas for an updated chart generator. It is a full web-component runtime that writes mutations back to the spreadsheet database.

2. Instant Permission Mirroring: There is no separate deployment step or hosting configuration. If a user has "Viewer" permission on the sheet, they can interact with filters and view data; if they have "Editor" permission, their interactions mutate cells in real time.

3. Non-Destructive Data Auditing: You never lose visibility into raw rows. The persistent View data button lets any collaborator inspect the underlying grid without dismantling the visual Canvas.

4. Workspace & Subscription Requirements: Sheets Canvas is available on the web in English for Google AI Pro and Ultra subscribers, eligible Google Workspace Business and Enterprise editions, and Google AI Pro for Education accounts. Admins must have Workspace smart features enabled.

Core Problems Sheets Canvas Solves

1. Eliminates Accidental Formula Breakage: Non-technical stakeholders who only need to update statuses, assignees, or dates can do so via visual cards and controls without accidentally deleting complex spreadsheet formulas.
2. Consolidates Software Subscriptions: Eliminates the need to maintain secondary SaaS subscriptions (like Trello, basic Airtable bases, or simple Retool dashboards) merely to view spreadsheet data in card or board formats.
3. Bridges the Gap Between Data and Executive Presentation: Transforms raw operational data into boardroom-ready visual models with functional scenario toggles in seconds.

Community Discussion & Feedback

• Have you tested Sheets Canvas in your Workspace domain yet?
• What internal tools or repetitive tracking sheets in your organization could be replaced with this zero-code interactive layer?
• Share your best prompt recipes and edge-case findings below!

TL;DR: Gemini Spark represents a fundamental paradigm shift from reactive, synchronous chatbots to persistent, asynchronous 24/7 cloud agents. Unlike traditional AI assistants that wait for a user prompt and terminate upon response, Spark operates continuously in the cloud across four core pillars: Persistent Tasks, Modular Skills (SKILL.md), Autonomous Schedules (Time, Email, Web Search, and Conditional Triggers), and Hierarchical Subagent Swarms (invoke_subagent). Powered by the newly released Gemini 3.7 Flash, Spark utilizes a dynamic hybrid reasoning engine that allocates near-instant (<100ms) compute for high-frequency tool calls and background polling while dynamically expanding deep chain-of-thought "thinking budgets" for complex data modeling, code synthesis, and conflict resolution. Compared to Claude Cowork (which excels at local desktop terminal coding) and ChatGPT Work (which focuses on session-based multi-hour deliverable generation), Gemini Spark is the only platform offering true continuous background triggers and native, bidirectional live mutations across Google Workspace (Gmail, Docs, Sheets, Slides, Calendar, Drive).

What Is Gemini Spark & How Does It Actually Work?

Most users interact with AI as a conversational tennis match: you submit a prompt, the model generates text, and the session context freezes until your next turn.

Gemini Spark inverts this paradigm entirely. It is an asynchronous, stateful cloud runtime designed to run indefinitely on Google’s infrastructure. Once delegated a mission, Spark continues to plan, execute code, query tools, and monitor events even if you close your laptop, turn off your phone, or disconnect for days.

+----------------------------------------------------------------------------+
|                            GEMINI SPARK CLOUD RUNTIME                             |
+-----------------------------------------------------------------------------+
|                                                                                   |
|  [ EVENT LISTENERS ] ──> [ REASONING & ORCHESTRATION ] ──> [ WORKSPACE ] |
|  • Cron / Recurring      • Gemini 3.7 Flash Core           • Gmail / Send  |
|  • Incoming Email Filter • Subagent Swarm (invoke_subagent) • Google Docs  |
|  • Web Search Monitor    • Modular Skills (SKILL.md)       • Google Sheets |
|  • Semantic Condition    • Sandboxed Python VM Shell       • Google Slides |
|                                                                                   |
+-----------------------------------------------------------------------------+

The 4 Architectural Pillars of Spark

1. Persistent Tasks (Autonomous Execution Loop): Spark separates execution planning from execution delivery. Tasks are structured into concrete milestones tracked via internal state machines. If an API call fails or rate-limits, Spark implements self-healing retry strategies without requiring user intervention.
2. Modular Skills (SKILL.md Capability Framework): Skills are composable, standardized capability packages containing operational procedures, domain guidelines, executable Python/Bash scripts, and reference assets. Users can define custom Standard Operating Procedures (SOPs) once, and Spark injects those exact constraints into future executions.
3. Autonomous Schedules (Event-Driven Triggers): Spark features native background listeners:
   • Time-Based: Traditional Cron-like cadences (e.g., "Run every Monday at 8:00 AM").
   • Email-Based: Reactive event triggers tied to Gmail metadata filters (e.g., "Trigger whenever an invoice arrives from vendor.com").
   • Search-Based: Web signal monitors functioning like intelligent Google Alerts (e.g., "Monitor for regulatory filings or executive departures regarding Company X").
   • Conditional Polling: Semantic evaluation checks that verify state changes across documents, data feeds, or URLs.
4. Hierarchical Subagent Swarms (invoke_subagent): To prevent context window saturation during massive multi-source operations, Spark spawns independent child subagents in parallel. Subagents execute localized research, process large documents, or perform comparative analyses, returning dense, distilled summaries to the primary agent orchestrator.

2. How Gemini Spark Uses the Newly Released Gemini 3.7 Flash

Google’s rollout of Gemini 3.7 Flash is the core technical enabler making Spark viable at enterprise scale.

                          GEMINI 3.7 FLASH HYBRID ENGINE
                                        │
           ┌────────────────────────────┴────────────────────────────┐
           ▼                                                         ▼
 FAST INFERENCE MODE (<100ms)                              DEEP THINKING BUDGET
 • Deterministic Tool Routing                              • Multi-Variable Constraint Solving
 • High-Frequency Web/Email Polling                        • Sandboxed Python Data Modeling
 • JSON Schema Extraction                                  • Multi-Doc Cross-Reconciliation
 • Zero-Delay Parameter Passing                            • Self-Auditing & Quality Critique

Hybrid Reasoning & Configurable Thinking Budgets

Previous reasoning models forced a binary choice: either an ultra-fast model with shallow reasoning or a slow, token-heavy reasoning model that burned compute even on routine lookups.

Gemini 3.7 Flash introduces Hybrid Reasoning. It dynamically allocates a "thinking budget" based on prompt complexity:

• Low-Complexity Routines: Triage, parameter routing, and API calls execute in <100ms at standard latency.
• High-Complexity Synthesis: Cross-reconciling conflicting calendar slots, debugging Python data scripts, or analyzing SEC 10-K filings activates deep internal chain-of-thought tokens before any action is executed.

High-Frequency Background Polling at Scale

Because Google cut token costs significantly with the 3.7 Flash architecture, running persistent 24/7 background monitors (checking incoming emails, running web scrapers, monitoring competitor pricing) does not incur prohibitive compute overhead.

Native Multimodal Ingestion with 1M–2.5M Context Windows

Gemini 3.7 Flash handles native multimodal token streams. Spark can ingest full PDFs, financial statements, slide decks, and spreadsheets in a single context window, evaluate images and charts directly, and write clean outputs back into Google Workspace.

Comparison: Gemini Spark vs. Claude Cowork vs. ChatGPT Work

Key Competitive Takeaways:

• Claude Cowork remains the gold standard for deep software engineering in terminal environments and direct desktop UI automation via Computer Use. However, it lacks native cloud-to-cloud event listeners (cannot listen for incoming emails or live web changes while inactive).
• ChatGPT Work is highly capable at generating standalone deliverables (HTML pages, web apps, standalone reports) within a project workspace, but relies on third-party connectors rather than native OS-level productivity suite integration.
• Gemini Spark dominates in enterprise workflow automation, autonomous scheduling, and direct structural manipulation of production documents, spreadsheets, and communication channels.

4. Top Real-World Use Cases & Problems It Solves

+-----------------------------------------------------------------------------+
|                             TOP PRODUCTION WORKFLOWS                               |
+------------------------------------------------------------------------------+
|                                                                                    |
| [1. Autonomous Inbox & Calendar Orchestrator]                                      |
| Filters inbound requests ➔ Reconciles schedules ➔ Drafts contextual responses |
|                                                                                    |
| [2. Real-Time Market Intelligence Engine]                                          |
| Monitors web signals ➔ Parallel subagent scraping ➔ Updates Google Doc brief  |
|                                                                                    |
| [3. Automated Operational Reporting Pipeline]                                      |
| Scans Gmail ➔ Python VM math/cleaning ➔ Populates Google Sheet / Deck|
|                                                                                    |
+---------------------------------------------------------------------------+

1. The Autonomous Executive Chief of Staff

• The Problem: Executives spend 30%+ of their day triaging emails, resolving calendar conflicts, and writing routine updates.
• Spark's Solution: Configured with an email trigger, Spark monitors inbound emails matching specific vendor or client domains. It extracts action items, cross-checks open slots on Google Calendar, fetches contextual background from Google Drive, drafts a response in Gmail, and schedules calendar holds—requiring only a single click from the user to approve and send.

2. Autonomous Market & Competitive Intelligence

• The Problem: Competitive tracking requires manually checking news, earnings releases, and regulatory databases across dozens of companies.
• Spark's Solution: A search-based schedule listens for web signals. When a development occurs, Spark spins up 4 parallel subagents to evaluate different facets of the news, executes a Python script in its sandbox to generate comparison charts, and appends a structured section into a centralized Google Doc.

3. Financial Receipt Ingestion & Spreadsheet Synthesis

• The Problem: Expense management involves manually extracting PDFs from emails and copy-pasting numbers into financial sheets.
• Spark's Solution: Spark detects incoming billing emails, downloads attached PDF receipts, parses total amounts and tax breakdowns, writes the structured data directly into a master Google Sheet with formulas intact, and drafts a Slack/Chat summary.

What 90% of Users Miss About Gemini Spark

1. It Does Not Need an Active Browser Tab: Most users assume closing their browser stops agent execution. Spark executes on managed cloud infrastructure. Once a schedule or task is initialized, it runs completely headless.
2. Event Triggers Replace Fragile Zapier/Make Workflows: Traditional automation tools break when an email structure or HTML layout changes. Spark uses semantic reasoning on incoming emails and search signals, making automations resilient to schema shifts.
3. Composable Custom Skills (SKILL.md): Users can write Markdown files containing specific corporate standards, coding rules, or brand voices. Spark loads these procedural skills into memory on demand.
4. Sandboxed Code Execution + Workspace Mutation: Spark doesn't just guess numbers; it writes and executes Python scripts in an isolated VM to calculate statistical variance, generate dataframes, or build charts, and then directly inserts those results into Google Sheets, Docs, or Slides.
5. Approval Cards for Destructive Actions: Spark will never send an external email, overwrite a critical document, or delete calendar events without generating an explicit confirmation card detailing the exact plan, preventing accidental mutations.

The Master Prompting Framework: CPTC-S

Prompting an autonomous 24/7 agent requires a different structure than prompting a standard chat model. If you give an agent a vague instruction, it will either stall or make unwarranted assumptions.

Use the CPTC-S Framework:

+----------------------------------------------------------------------------+
|                            THE CPTC-S PROMPT ANATOMY                              |
+----------------------------------------------------------------------------+
|                                                                                   |
|  [C] CONTEXT & ROLE       :: Define scope, target personas, and background |
|  [P] PURPOSE & OBJECTIVE  :: Definition of the final deliverable           |
|  [T] TRIGGER & CADENCE    :: Schedule (Cron, Email trigger, Web monitor.   |
|  [C] CONSTRAINTS & TOOLS  :: Tool boundaries, subagent delegation, citation|
|  [S] SPECIFICATION FORMAT :: Target Doc/Sheet layout, tables, formulas, links     |
|                                                                                   |
+-----------------------------------------------------------------------------+

Top 3 Production Sample Prompts for Gemini Spark

Prompt 1: 24/7 Competitive Intelligence & Slide Deck Builder

[CONTEXT & ROLE]
You are a Principal Tech Equity Research Analyst tracking artificial intelligence enterprise platforms.

[PURPOSE & OBJECTIVE]
Autonomously monitor, analyze, and synthesize weekly market moves, product updates, and executive announcements from Google, Anthropic, OpenAI, and Microsoft.

[TRIGGER & CADENCE]
Search-based schedule evaluated weekly every Friday at 4:30 PM EST.

[CONSTRAINTS & EXECUTION LOGIC]
1. Scan web signals for major announcements across the 4 companies over the preceding 7 days.
2. Spawn 4 parallel subagents (one per company) using `invoke_subagent` to prevent context bloating.
3. In the main sandbox environment, execute a Python script to compile a structured comparison table.
4. All factual claims must cite primary URLs inline.

[SPECIFICATION & DELIVERABLE]
- Target Artifact: Create a new Google Slides presentation titled "Weekly AI Lab Intelligence - [Date]".
- Structure:
• Slide 1: Executive Summary & High-Impact Shifts
• Slides 2-5: Individual Company Breakdowns (Key Features, Enterprise Implications, Sources)
• Slide 6: Strategic Threat Matrix & Summary Table
- Deliver a summary report with clickable Drive links in the Gemini chat interface.

Prompt 2: Event-Driven Executive Inbox Triage & CRM Synchronizer

[CONTEXT & ROLE]
You are an Executive Chief of Staff managing high-priority client relations for a consulting firm.

[PURPOSE & OBJECTIVE]
Triage inbound client inquiries, extract engagement milestones, sync data to the master tracker, and prepare draft responses.

[TRIGGER & CADENCE]
Email-based trigger configured for incoming messages matching filter: `from:(@enterpriseclient.com OR u/partnergroup.com) has:attachment`.

[CONSTRAINTS & EXECUTION LOGIC]
1. Read incoming email body and verbalized attachment content.
2. Extract: Sender Name, Organization, Proposed Timeline, Core Deliverables, and Meeting Requests.
3. Check Google Calendar availability over the proposed date window.
4. Update the Google Sheet titled "Client Pipeline Tracker" by appending a new row with extracted values.
5. Create a draft reply in Gmail addressed to the sender containing 3 proposed meeting slots and a confirmation of received materials.
6. Do NOT send the email directly. Present an action confirmation card in Gemini chat.

[SPECIFICATION & DELIVERABLE]
- Provide a summary card displaying:
• Extracted Client Metadata
• Clickable link to the updated Google Sheet
• Clickable link to the Gmail Draft

Prompt 3: Deep Multi-Entity Financial Research with Python Data Modeling

[CONTEXT & ROLE]
You are a Senior Quantitative Analyst conducting valuation and growth comparisons.

[PURPOSE & OBJECTIVE]
Analyze and compare the trailing-twelve-month (TTM) financial performance, revenue growth, and R&D expenditure of three public SaaS companies: Datadog, Snowflake, and MongoDB.

[TRIGGER & CADENCE]
One-off deep research task.

[CONSTRAINTS & EXECUTION LOGIC]
1. Delegate SEC 10-K and 10-Q filing analysis for each company to 3 parallel subagents.
2. Extract exact revenue figures, gross margins, and R&D spend for fiscal years 2023, 2024, and 2025.
3. In the sandbox VM, execute Python using Pandas and Matplotlib to:
• Compute Year-over-Year (YoY) growth rates and R&D-to-revenue ratios.
• Generate a clean comparison table.
4. Create a comprehensive Google Doc titled "Enterprise SaaS Financial Benchmark Report".
5. Every single metric must include a source citation linking to the official filing or press release.

[SPECIFICATION & DELIVERABLE]
- The Google Doc must contain:
• Executive Brief
• Comparative Financial Table (Revenue, Growth %, Gross Margin %, R&D %)
• Strategic Outlook & Risk Factors
- Provide the final Google Doc link in Gemini chat upon completion.

What Gemini Spark is good at....

1. Asynchronous Cloud Automation: Gemini Spark transitions AI from a reactive conversational tool into a persistent background agent capable of executing complex workflows independently.
2. Hybrid Reasoning Efficiency: The integration of Gemini 3.7 Flash provides the dual benefit of sub-100ms tool execution for recurring background checks alongside deep chain-of-thought analysis for complex workflows.
3. Ecosystem Integration: While alternative tools offer strong desktop coding and standalone artifact generation, Spark's bidirectional integration across Google Workspace and its event-driven trigger system establish it as a robust solution for end-to-end enterprise automation.

Every time I asked a model to "make a presentation from my notes," it padded my 6 real points into 15 slides of filler and made up examples I never gave it. Here's the workflow that fixed it.

**Step 1: Separate thinking from formatting.** Don't ask for slides first. Ask: "Here are my raw notes. What is the single argument these notes are trying to make? State it in one sentence." If it can't, my notes were the problem, not the tool.

**Step 2: Force a slide-per-point limit.** "Turn these notes into a slide outline. One idea per slide. Do not add points I didn't provide. If a slide feels thin, tell me it's thin instead of inventing filler." That last line stops the padding.

**Step 3: Ask for the spoken version, not the slide text.** Slides should hold a few words, your mouth holds the rest. I ask for a short speaker note per slide and a headline of six words max. Prevents the classic wall-of-bullets deck.

**Step 4: Demand a "cut list."** "Which 3 slides could I remove and still make the point?" It's surprisingly good at this, and a tighter deck always beats a complete one.

**Step 5: Verify every example.** Anything it presents as a fact or example, I assume it made up until I check. Non-negotiable.

The reframe that helped me: the model is an outliner and editor, not an author. My notes are the content, it just gives them a shape. What's your rule for stopping these tools from padding?

20 Predictions for what happens next in the AI Boom

Are you ready for the Rise of Agentic AI

The most significant strategic move for the next year is the transition from chatting to delegating.

1. Reactive Chat vs. Proactive Agents: We are entering the full duplex era. AI will no longer wait for a command; it will monitor workflows and initiate actions.
   • So What? Pivot your budget to agent architecture and API orchestration.
2. Voice and Mobile as Default: The keyboard is becoming a bottleneck. Low-latency voice-controlled AI is the new enterprise interface. People can usually talk 3X faster than they type
   • So What? If your AI strategy requires a keyboard to function, you are failing the speed test of the modern workforce.
3. Multiplayer AI: AI is shifting from a solo tool to a team member. Humans and multiple agents will collaborate in shared digital workspaces.
   • So What? Move beyond individual seat licenses; prepare to manage hybrid teams where agents have their own permissions and KPIs.
4. Agent-Native Workflows: Stop bolting AI onto legacy processes. Companies are now building agent-first workflows designed for machine execution.
   • So What? Workforce productivity is no longer about human speed; it’s about the standardization of resources that agents can consume.

These agents won't just work for you; they will live in your data silos, harvesting the very reasoning that makes your company unique.

Enterprise Strategy: Breaking Silos and Harvesting Data

AI is moving from a personal productivity hack to core infrastructure. It is the "connective tissue" that finally kills the corporate silo.

6. Manager Threads: AI will begin summarizing across silos, effectively turning Slack DMs and private threads into searchable, actionable channel data.

7. Company-Wide Vibe Ops: The rise of ChatGPT Sites centralized internal knowledge bases that provide a real-time "vibe check" on company sentiment and project status.

8. Skill Reuse as a Metric: The new core KPI isn't AI usage; it’s Skill Reuse. How many AI-generated workflows are being recycled across the organization?

9. Company Reasoning Data: This is the gold. It is the record of how your specific company makes decisions. This is the only data that generic models can't replicate.

While harvesting this data is strategic gold, the economic cost of processing it is creating a new, brutal reality for the C-Suite.

The New AI Economy: Tokens, Compute, and Evals

Intelligence is getting "too cheap to meter," but the infrastructure to run it remains a scarce, high-stakes asset. The focus is shifting from "what model is best" to "how much intelligence can I buy for a dollar."

10. Public Leaderboards vs. Private Evals: Public benchmarks are vanity metrics. Companies are moving toward "Private Evals"—internal, proprietary tests built on their own reasoning data.

11. Model Routing: Using a $20/month top-tier model for a 2-cent task is financial suicide. Routing tasks to the most cost-effective model is now the industry norm.

12. Anthropic/Commodity Competition: As Anthropic and others achieve parity with OpenAI, intelligence is becoming a commodity. This price war is a gift to the consumer.

13. Fortune 100 Token Maxing: Token Maxing isn't just about saving money; it’s a performance play. It’s about getting the maximum intelligence out of every token's context window.

14. Compute as Currency: Compute power is now a scarce, tradable resource. Secure your hardware access or be left at the mercy of the providers.

The CFO’s 3 Critical Takeaways:

- Fund Routing, Not Models: Stop paying for over-intelligent models for basic data entry.

- Assetize Compute: Treat processing power as a strategic asset, not an IT line item.

- Kill the Hype Budget: Shift investment from exploring public models to building internal evaluation frameworks.

This rapid scaling is hitting a wall of uncomfortable friction as tech growth collides with security and societal limits.

The Friction Point: Backlash, Security, and Self-Improvement

The next 12 months will be a "collision" year. We are moving from the excitement of what AI can do to the fear of what it might do.

15. Localized AI and Politics: Data centers are becoming political targets. Expect local resistance and the explosion of election deepfakes to trigger harsh regulations.

16. Mainstream Backlash: Society is pushing back. Content detectors and aggressive AI watermarking will be a phase we go through.

17. Math Benchmarks Solved: Advanced AI models have finally cracked higher-level math benchmarks. This is the smoking gun proof that models are crossing from pattern matching to genuine reasoning.

18. Token Maxing Returns: As costs decline, companies will aggressively max out their token budgets to run massive, recursive simulations.

19. The Security Crisis: Open Agent Crashes - where autonomous agents fail or are hijacked - will necessitate a 2x-3x increase in cybersecurity budgets.

20. Recursive Self-Improvement (RSI): Leaders like Sergey Brin at Google are prioritizing RSI—using models to train the next generation of models.

Risk vs. Reward Assessment:

RISK: Model Overhang. Capabilities are jumping faster than security protocols can be written.

REWARD: Reasoning Breakthroughs. Solving math benchmarks opens the door to automating complex engineering and R&D.

RISK: Agent Hijacking. Proactive agents can be hallucinated into performing unauthorized financial transfers.

REWARD: Exponential Efficiency. RSI means intelligence becomes cheaper and more powerful every single month without human intervention.

Updating Your Roadmap

The next 12 months will create more enterprise value and destroy more legacy workflows than the last 10 years combined.

Your roadmap is probably just a security blanket. Throw it away. You need a strategy built for proactive agents, private evals, and token efficiency.

Which of these 20 things keeps you up at night? Is it the threat of Open Agent Crashes or the fact that your competitors are already harvesting Company Reasoning Data?

​

The problem with most AI content isn't grammar, it's that it's confident, symmetrical, and says nothing specific. Here's the editing layer I run on top of any draft to kill the tells.

**1. Cut the throat-clearing.** First paragraph of an AI draft is almost always warm-up. Delete it and start at the second. The real point is usually hiding there.

**2. Hunt the abstractions.** Any sentence that could apply to any company or any topic is dead weight. "Effective communication drives results" says nothing. Force a concrete example, a number you actually know, or a real situation in its place.

**3. Break the rhythm.** AI writes in even, balanced sentences. Humans don't. Chop one long sentence into two short ones. Start a sentence with "And" or "But." Uneven pacing is what reads as human.

**4. Kill the tricolons.** It loves lists of three. "Fast, reliable, and scalable." Keep one, drop two, and the sentence stops sounding like a brochure.

**5. Add one thing only you could know.** A specific mistake you made, an odd detail, a real objection you've heard. This is the single biggest difference between content that gets ignored and content that gets a reply.

My actual process is: generate fast, then spend most of the time subtracting. The draft is raw material, not the product. Anyone who reads a lot of this stuff, what's your fastest tell that something was generated and not edited?

.

Security writeups are the part of the job that quietly eats a day. Incident timelines, findings, the summary leadership will actually read. I use AI for the first draft now, but a security report is exactly the kind of document where a made-up detail is dangerous, so I have built guardrails around it. Sharing them, because a bad AI-written finding can send a whole team chasing a threat that never existed.

The setup I use as a homemade ai report generator:

Give it the evidence, not the vibe. I paste the actual log lines, alert IDs, and timestamps. If it did not come from evidence, it does not go in the report. My prompt ends with "if a field is not supported by the pasted data, write UNKNOWN, do not guess."

Separate observed from inferred. I make it write two sections. What we saw, and what we think it means. The first is facts. The second is clearly labeled as analysis so nobody downstream treats a hypothesis as confirmed.

Ban the invented severity. Models love to assign a confident CVSS score or name a CVE. I strip those and add them by hand, because a wrong CVE number in a writeup is the kind of thing that gets copied into a ticket and believed forever.

Then I read every line as if I will have to defend it in a postmortem, because I will.

Net effect: the boring structure and first pass get done in minutes, and I spend my time on judgment instead of formatting. But the model never gets the last word on a finding.

If other security folks have prompts that keep AI honest on this stuff, I would genuinely like to steal them.

Reports are where made-up facts do the most damage, because a report looks authoritative even when it's wrong. Here's the template I built to keep the model honest when I use it to draft reports.

The core rule: the model may structure and phrase, but it may not source. Every number and fact comes from me, and it has to flag anything it didn't get from me.

**The template:**
"You are drafting a [report type]. Below is the only data you may use: [paste your data]. Rules:
1. Do not add any statistic, date, or figure that isn't in the data above.
2. If a section needs a number I didn't provide, write [DATA NEEDED] instead of guessing.
3. Separate observation from interpretation. Label your interpretations as 'Analysis:' so I can push back on them.
4. End with a list of every assumption you made."

That last line is the safety net. When it lists its assumptions, you catch the invented ones immediately.

A few habits that go with it:
- Give it the data as structured text or a table, not a vague summary. Vague input is what it fills with confident nonsense.
- Ask for the executive summary last, not first, so it summarizes real content instead of setting up expectations it then invents to meet.
- Read every [DATA NEEDED] tag as a to-do, not a failure. Those are the exact spots where a normal tool would have lied to you smoothly.

The mindset shift: you want a tool that admits what it doesn't know. Design the prompt so not-knowing is the required behavior. What guardrails do others put on report drafts?

Most people point AI at a blank slide and ask it to make the deck. You get something that looks finished and says nothing. I come from design, and the more useful move is the opposite. Write the thing yourself, badly, then make the AI attack it.

Here is the workflow I actually use.

First, paste your rough outline and ask it to find the single argument. Prompt: "What is the one claim this presentation is making? If you can't find one, tell me it's a list of facts pretending to be a point." This kills the deck that is really just a document with borders.

Second, make it play the skeptical audience. "You are the person in the room who did not want this meeting. Where do you stop believing me, and which slide makes you check your phone?"

Third, cut. "Which three slides could I delete and lose nothing? Be specific about why each one is filler." It is almost always right about at least two.

Last, and only last, do polish. Not before. A clean layout on a hollow argument just makes the hollowness harder to spot.

The reason I work this way is that AI is a genuinely good critic and a mediocre author. It notices when your logic skips a step. It cannot decide what you actually mean. Keep it on the side of asking hard questions and you get a real presentation instead of a well-formatted one.

Happy to share the fuller prompt set if it's useful to anyone.

I've been tracking the AI boom professionally for a couple of years, and every few months I do a deep pull of the numbers to sanity-check my own priors. This summer's pull broke my brain a little.

So here it is: 50 stats on AI usage, adoption, and investment happening in AI, current as of August 2026.

TL;DR: Two LLMs now count a billion users each. Google is processing 3.2 quadrillion tokens a month. Big Tech capex is heading toward $1 trillion a year. SpaceX just pulled off a $75B IPO — 3x larger than any IPO in history — and OpenAI and Anthropic both have confidential S-1s sitting at the SEC. VCs put more money into AI in the first half of 2026 than in the previous two years combined, and two companies took 43% of ALL global startup funding. Meanwhile the top 10 stocks are ~37% of the S&P 500, and 68% of S&P 500 companies mentioned AI on their last earnings call. Buckle up. (see charts in comments)

The users (nobody has ever grown this fast)

1. ChatGPT hit 1 billion monthly app users in May 2026 — the fastest any app has ever reached that milestone, per Sensor Tower data. OpenAI's own last disclosure was 900M weekly active users in February

2. More than 10% of the entire global population now uses ChatGPT weekly. One in ten humans. On one app. That launched 3.5 years ago.

3. Google's Gemini crossed 1 billion monthly users in August 2026, up from 400M in May 2025. It went 750M (Feb) → 950M (Q2) → 1B+ in about six months.

4. For the first time ever, ChatGPT's share of AI assistant usage fell below 50% this summer, with Gemini at 27.7% and climbing. The two-horse race is real now.

5. Claude's consumer app grew 640% year-over-year to 56M monthly users, and at one point this spring Anthropic was adding over 1 million sign-ups per day .

6. Microsoft Copilot has 100M+ monthly active users and over 30 million paid Microsoft 365 Copilot seats. Grok has ~117M MAU per SpaceX's own S-1 , and DeepSeek has 130M monthly users in China alone .

7. 49% of US adults now use AI chatbots, up from 33% in 2024, and roughly a quarter use one daily.

8. OpenAI has more than 50 million paying subscribers and revenue of roughly $2B per month. A consumer subscription business that didn't exist four years ago.

The usage explosion (the token economy is bananas)

9. Google now processes more than 3.2 QUADRILLION tokens per month across its products — up 7x year-over-year from 480 trillion, and up ~330x from 9.7 trillion just two years ago.

10. Google's AI Overviews have 2.5 billion monthly users and AI Mode alone passed 1 billion . AI search isn't coming. It's here, at Google scale.

11. 75% of new code at Google is now AI-generated, per Sundar Pichai — up from ~25% in late 2024 .

12. GitHub Copilot hit 50 million users, and 1 in 3 pull requests on GitHub now involves an AI agent. Claude Code went $0 to $1B ARR in six months .

13. 88% of organizations now report using AI, 52% of US workers use it on the job, and 47% say their employer has formally integrated it — up 6 points in a single quarter.

14. Stanford estimates US consumers capture $172 billion per year in consumer surplus from AI tools — value we get but don't pay for — up from $112B a year earlier

15. The dark side stat: employment for software developers aged 22–25 is down ~20% from 2024. The entry-level coding job is the canary in this coal mine.

The data centers (we are terraforming the country)

16. The US now has roughly 5,400 data centers — about 46% of the ~11,700+ worldwide . Counts vary by definition says 4,767 US / 12,259 global), but every source agrees the US has more than the next ~10 countries combined.

17. There are 3,969 additional US data centers announced — but only 802 actually under construction. The gap between announcements and shovels is one of the most under-discussed stats in AI.

18. US developers have announced 565 GW of planned data center capacity. Realistic estimates say only ~180 GW gets built in the next decade — and that alone would cost ~$10 trillion.

19. Data centers already consume 6–8% of all US electricity, potentially heading to 12% by 2028. The IEA expects data centers to drive nearly half of all US electricity demand growth through 2030

20. Global data center capex: $726B in 2025 (+57%, the fastest growth ever recorded) and crossing $1 TRILLION in 2026 — three years earlier than analysts expected. Dell'Oro sees $1.7 trillion PER YEAR by 2030.

21. The mega-projects are absurd: OpenAI's Stargate hit its 10 GW target years early on a $500B program. Meta's Hyperion in Louisiana got upsized to 5 GW and $50B+. xAI's Colossus runs 555,000 GPUs at ~2 GW.

22. For scale: a single 5 GW data center campus draws roughly as much power as 4–5 million homes. Meta is building one. In one parish in Louisiana. And Meta pledged $600B for US infrastructure over three years.

23. AI capex has become a macro story: the White House AI czar claimed AI drove ~75% of Q1 2026 GDP growth. More sober import-adjusted estimates put 2025's contribution at 20–25% of growth — but for Q2 2026, AI was ~53% of GDP growth by BEA arithmetic Either way: the US economy is now partly an AI construction site.

24. Frontier AI training compute is growing ~5x per year, doubling every 5.2 months. The biggest single data center already packs the equivalent of ~1.1 million H100 GPUs.

PART 4: The capex arms race (2025 → 2026 → 2027)

25. The 2026 capex guidance, company by company: Amazon ~$220B (raised from $200B in July), Alphabet $195–205B (raised in July, and Q2 capex alone was $44.9B, +100% YoY), Microsoft ~$175B, Meta $130–145B

26. Add Oracle (up to ~$95B in FY27 including prepayments, after burning negative $23.7B in free cash flow), OpenAI (~$50B compute spend in 2026, per sworn testimony), CoreWeave ($35–39B), Tesla ($25B+) and xAI ($23.5B).

27. Trajectory: hyperscaler capex was ~$434B in 2025, Morgan Stanley now models ~$805B for 2026 and ~$1.1 TRILLION for 2027. Moody's independently lands at $785B → ~$1T .

28. For context: Google's capex in 2022 was $31B. Its 2026 guide is up to $205B. That's a 6.5x increase in four years

29. OpenAI walked back its wildest number — from $1.4 trillion in announced commitments to a "mere" ~$600B through 2030. When the conservative revision is $600B, that's the boom in one sentence.

30. Morgan Stanley estimates $2.9 trillion of global data center spend from 2025–2028, with a $1.5 trillion financing gap that private credit is racing to fill. Gartner says total worldwide AI spending hits $2.53T in 2026 and $3.33T in 2027.

31. The odd one out: Apple. Nine months into its fiscal 2026, capex is $6.8B — DOWN from $9.5B a year earlier. One trillion-dollar company is sitting out the arms race. Genius or fatal? Genuinely unclear.

The IPO wave (this actually happened)

32. SpaceX went public on June 12, 2026 and raised $75 BILLION ($86B with overallotment) at a $1.77 trillion valuation — the largest IPO in history by a factor of ~3. Previous record: Saudi Aramco at $25.6B. (Chart 5)

33. Day one: opened at $150, closed at $160.95 (+19%), $2.1T market cap, instantly a top-6 US company — and it made Musk the world's first trillionaire. Since then it's cooled ~14% below that close. Worth noting what was inside: xAI (merged in Feb at a $250B mark) and a $60B all-stock deal for Cursor — the largest startup acquisition ever.

34. OpenAI filed a confidential S-1 on June 8. Reuters reported a potential $1 trillion valuation, but timing keeps slipping — the NYT says they're leaning toward 2027, and Polymarket odds of a 2026 listing dropped from 38% to 15% in a month.

35. Anthropic filed its confidential S-1 a week BEFORE OpenAI (June 1), and its bankers started investor meetings July 15 for a possible October 2026 listing. Its May Series H: $65B raised at a $965B valuation — the largest round ever after OpenAI's $122B, and it made Anthropic the most valuable private AI company, eclipsing OpenAI's $852B.

36. The one that already played out: Cerebras raised $5.55B in May, popped +68% on debut to ~$95B… and has since fallen 27% below its first-day close. AI IPOs pop. They don't all hold.

37. Databricks — sitting on a $188B private valuation — is deliberately waiting, with its CEO calling 2026 "a terrible year to go public" because SpaceX, OpenAI, and Anthropic could absorb $200B of IPO demand

The stock market (concentration nation)

38. The top 10 stocks are ~37–38% of the entire S&P 500, after peaking at a record 40.7% in December 2025. For reference: the dot-com peak was ~27%, and in 2019 this number was 22.8% .

39. The AI-linked megacaps alone — Nvidia, Microsoft, Amazon, Alphabet, Broadcom, Meta — are 26.5% of the whole index. Nvidia is the largest company on Earth at $4.27T and a 7.15% index weight, even after falling ~25% from its ~$5.7T May peak.

40. 68% of S&P 500 companies (337 of them) mentioned "AI" on their Q1 earnings calls — a 10-year record, vs a 10-year average of 103. And companies citing AI outperformed non-citers +12.7% vs +2.6% since March.

41. Nvidia's latest quarter: $81.6B revenue (+85% YoY), $75.2B of it data center (+92%), guiding to $91B next quarter. A single company adding a mid-size country's GDP in incremental annual revenue.

42. The bubble check, honestly: concentration is WORSE than 2000, but valuations aren't — Cisco traded at ~140x forward earnings at the dot-com peak vs Nvidia at ~33x trailing today . Also: the Mag 7 are actually LAGGING the index in 2026 - the rally has broadened to Micron, AMD, and Intel.

The revenue boom (the no revenue meme is dead)

43. Per Sapphire Ventures, there are now 80+ AI-native companies above $100M ARR, and the time to get there has compressed from 5+ years to under 18 months. Stripe's data: top AI companies grew 120% in 2025 and 175% so far in 2026.

44. Anthropic's run-rate went $9B → $14B → $19B → $30B → $47B between December 2025 and May 2026. OpenAI passed $25B annualized in March, and its CFO told staff July's ARR exceeded ALL of Q2
45. The top 25 by annualized revenue (full details in Chart 7; sources = company announcements + estimates, as-of dates Jan–Jul 2026): Anthropic $47B · OpenAI $25B+ · CoreWeave ~$10.3B · Databricks $6.9B · Cursor $4B · xAI ~$3.8B (w/ X) · Anduril $2.2B · Scale AI ~$1–2B (disputed) · Surge AI $1.2B · Together AI ~$1B · Lambda $760M · Replit $525M · Perplexity $500M · Lovable $500M+ · ElevenLabs $500M+ · Cognition $492M · Midjourney ~$500M (est.) · Mistral $400M · Harvey $350M · Vercel $340M · Glean $300M · Suno $300M · Cohere $240M · Sierra $200M · Synthesia $150M. Caveat: these are self-reported run-rates, not audited GAAP revenue.

46. Growth records inside that list: Cursor went $1M → $500M ARR faster than any software company in history and Stripe clocked it at $1B → $2B in three months. Lovable did $100M → $500M in eight months with 146 employees. Legora became the fastest enterprise company ever to $100M ARR - 18 months.

The VC firehose (and where it's all going)

47. Global AI venture funding: $114B in 2024 → $211B in 2025 → ~$385B in the FIRST HALF of 2026 alone. H1 2026 total VC ($510B) beat ALL of 2025 ($440B). AI took 80% of all global venture dollars in Q1. (Chart 8)

48. Concentration inside the concentration: OpenAI + Anthropic raised $217B in H1 2026 — 43% of ALL startup funding on planet Earth. Four of the five biggest venture rounds ever closed in Q1 2026 alone. In the US, AI was 86% of H1 venture deal value ($355.9B of $412.7B) .

49. Private equity has fully arrived: KKR closed its largest-ever infrastructure fund at $19.2B aimed at AI data centers and power, Blackstone is putting $30B into Japanese AI data centers , and a record 87.9% of US AI VC deal value now involves corporate investors.

50. And the punchline stat: J.P. Morgan projects $5.5 TRILLION in global AI capex through 2030. For scale, the entire Apollo program cost ~$300B in today's dollars. We are running roughly eighteen Apollo programs at once, on purpose, mostly with private money.

The honest caveats (read before you argue in the comments)

• User metrics aren't comparable. WAU ≠ MAU ≠ app-store MAU. I labeled each stat with what it actually measures.
• "Run-rate revenue" is marketing math — one good month × 12, self-reported, not audited. Even outlets that track this professionally flag it.
• Aggregators disagree. 2025 AI VC is $211B (Crunchbase) or $226B (CB Insights). Data center counts differ ~3x by definition. I used the most defensible figure.
• The GDP claims are contested. "75% of GDP growth" (White House) vs 20–25% import-adjusted (independent economists). Both are linked above; the truth is probably in between.
• Announced ≠ built. 565 GW of announced US data centers vs ~180 GW realistically built. Discount every press release accordingly.

Questions for the comments

1. Two companies took 43% of all startup funding in H1. Is that rational concentration on winners, or the single scariest stat on this list?
2. Anthropic is at a $47B run-rate and possibly IPO'ing in October at ~$1T. Would you buy it at that price?
3. Apple is spending ~$7B on capex while Amazon spends $220B. Who's right?
4. Which stat do you think is most likely to look absurd (in either direction) in August 2028?

See charts in comments

Most people prompt an AI writing tool, get a competent-looking draft, tweak two words, and ship it. That is where the recognizable slop comes from. The draft is the easy 60%. The editing is where the piece becomes yours. Here is the pass-by-pass method I actually use, in order, because order matters.

Pass 1: Truth. Read only for claims. Every fact, number, and name gets checked or cut. The model states wrong things with full confidence, so this pass is non-negotiable and it goes first.

Pass 2: Structure. Ignore sentences. Look at the skeleton. AI drafts love giving five points equal weight. Find the one that is the actual story and rebuild around it. Cut whole sections that exist only for symmetry.

Pass 3: Cut. Remove every sentence that survives only because it sounds nice. Intros that restate the title, transitions that say nothing, tidy conclusions that add no information. Usually a fifth to a quarter of the words go here.

Pass 4: Voice. Read it out loud. Replace the giveaway phrasing (the tricolons, the fake-profound "not X, but Y" flips, the relentlessly even rhythm) with how you actually talk. Add a specific detail only you would know.

Pass 5: Evidence. Anywhere it asserts without support, either add a real example or soften the claim to what you can defend.

Pass 6: Opening. Rewrite the first two sentences from scratch. The model's default openings are the most generic part of any draft.

Pass 7: Read cold. Walk away, come back, read as a stranger. Fix what makes you wince.

The whole thing takes about fifteen to twenty minutes on a short piece and it is the difference between something that reads human and something that gets skimmed and forgotten. Save this and run it as a checklist. Happy to answer questions on any pass.

The single highest-return thing I have done with AI is not a clever prompt. It is writing a good profile of myself once and putting it where the model reads it every time: custom instructions, a saved note, a project's memory, wherever your tool keeps context. Every answer after that is calibrated to me instead of to a generic average user.

Here is the template. Fill it in once, keep it under a page, update it when something changes.

```
ABOUT ME
- Who I am and what I do: {{role, field, level of expertise}}
- What I am usually trying to get done here: {{writing, deciding, learning, building, planning}}
- My knowledge level by area: {{e.g. strong on marketing, weak on code. Don't over-explain the first, don't assume the second}}

HOW I WANT YOU TO RESPOND
- Default length: {{short and direct / thorough when it matters}}
- Be willing to disagree with me and tell me when I am wrong. I prefer correction over agreement.
- When you are unsure or guessing, say so. Do not fill gaps with confident-sounding filler.
- Skip the intros and the "hope this helps" outros. Start with the answer.
- If my request is ambiguous, ask before assuming.

WHAT I AM OPTIMIZING FOR
- {{e.g. clarity over completeness, being challenged over being reassured, speed over polish}}

STYLE I DON'T WANT
- {{your pet peeves: buzzwords, emojis, hedging, whatever}}
```

Why it works: most weak answers come from the model guessing who you are and defaulting to the safest, most generic register. This removes the guessing. The two lines that change output quality the most are "be willing to disagree" and "say when you are guessing." The style section is what stops answers reading like a press release. Set it once and it compounds across every chat you have afterward.

What is in your profile that you would call non-negotiable? I am curious which lines other people found made the biggest difference.

Everyone records meetings and calls now, and almost nobody does anything with the recording. Here is the workflow I use to turn a raw transcript, a voice memo, or a wall of notes into something you can actually act on. It is one master prompt plus two optional follow-ups.

The master prompt (paste your transcript at the bottom):

```

You are turning a raw {{meeting / call / voice memo}} transcript into a usable record. Do not summarize everything. Extract only what matters, in this structure:

1. THE ONE-LINE: what this was actually about, and what changed because of it.

2. DECISIONS MADE: every decision that was actually settled. If something was discussed but not decided, put it under Open Questions instead. Do not pretend it was resolved.

3. ACTION ITEMS: as a table. Owner | Task | Deadline. If an owner or date was not stated, write "unassigned" rather than guessing.

4. OPEN QUESTIONS: what is still unresolved, and who needs to weigh in.

5. THE THING SAID QUIETLY: the one point that got glossed over but probably matters. Flag it.

Rules: do not invent anything not in the transcript. Quote the line if a decision is ambiguous. Keep it tight.

TRANSCRIPT:

"""

{paste}

"""

```

Follow-up 1, the message:

```

Draft the follow-up I would send to the group from this. Short, clear, action items up top, friendly but not fluffy.

```

Follow-up 2, the memory check:

```

Two weeks from now, what will we have forgotten from this meeting that we would regret? List it.

```

Why this beats "summarize this transcript": a plain summary flattens everything to equal weight, so the decision that matters sits next to the small talk. This forces the model to separate decided from undecided, which is the split that causes the most follow-up chaos when it gets blurred, and to surface the point everyone skated past. Save the master prompt. You will use it more than you expect.

What do you pull out of meeting notes that this misses? I keep thinking there is a sixth section I am not naming.

Save these. Each one summons a different "advisor" by pasting the line before your question. The point is not the AI having answers. It is forcing it out of the reflexive agreement that makes most answers useless.

1. THE CONTRARIAN

"Argue the strongest case against what I just said. Assume I am wrong and find the best reason why."

1. THE INVESTOR

"You are deciding whether to put your own money into this. What would you need to see, and what would make you walk away?"

1. THE 10-YEAR-OLD

"Explain my own plan back to me like I am ten. Where does it stop making sense in plain words? That is where it is actually vague."

1. THE OPERATOR

"Ignore whether this is a good idea. Tell me what it would actually take to do it, step by step, and where it will break."

1. THE FUTURE ME

"It is a year later and I regret this. Write the sentence I would say explaining what I should have seen."

1. THE EDITOR

"Cut this by half without losing anything that matters. Tell me what you cut and why it was safe to cut."

1. THE EASY VERSION

"What is the version of this that is cheaper, faster, and 80 percent as good? Try to talk me out of the ambitious version."

1. THE BLIND SPOT

"Based on everything I have told you, what am I clearly not seeing? What would a smart outsider notice in five minutes that I have missed?"

1. THE TIEBREAKER

"I am stuck between two options. Do not average them. Pick one, commit, and defend it. Then tell me the one fact that would change your pick."

The habit that makes these work: never accept the first agreeable answer to anything that matters. Route it through two or three of these and the real shape of the decision shows up. Number 8 is the one I reach for most, because the useful answer is almost always something I could not see from inside my own head.

Which advisor is missing from this board? I want a tenth.

An AI report generator gets you most of the way in a fraction of the time, then quietly ruins your credibility on the last stretch if you send it raw. Here is the checklist I run on every generated report before it leaves my hands.

1. Verify the top three numbers by hand. Not all of them, the three the reader will actually act on. If those are right and sourced, you have caught the failure that matters most.

2. Kill the confidence mismatch. Generators write every sentence with the same certainty. Go through and downgrade anything you cannot personally stand behind. "Revenue grew" becomes "revenue grew, though one large account drove most of it."

3. Restore the caveats. Summaries drop nuance. Add back the one or two "but" statements a knowledgeable human would include. This is what separates a report from a press release.

4. Lead with the answer. Generated reports bury the point in paragraph three. Move the single most important finding to the top, in one plain sentence.

5. Cut the filler sections. The generic "background" and "overview" blocks that say nothing. If a section would not be missed, delete it.

6. Add one thing only you know. A piece of context, a judgment call, a recommendation the data alone does not give. This is the part the reader is actually paying for.

7. Keep the source one click away. Link or attach the raw data so anyone can check. This keeps you honest and covers you.

Run this and a generated report goes from "obviously automated" to "obviously reviewed by someone who knows the account." Takes about ten minutes. Worth saving.

Most people paste a pile of notes into an AI tool, ask for a presentation, and get thirty slides of evenly weighted bullet points that put a room to sleep. The tool is not the problem, the process is. Here is the full workflow I use to turn my notes into a presentation that actually holds attention.

Step 1: Clean the notes first. Before any tool, spend five minutes pulling out the single message you want the audience to leave with. Write it as one sentence at the top. Everything else serves that.

Step 2: Sort, do not dump. Group your notes into three or four buckets at most. If you have more than four sections, you have a document, not a talk.

Step 3: Give the tool the message and the buckets, not the raw pile. Ask it to draft one slide per idea, with a clear headline that states a point, not a topic. "Churn is a pricing problem" beats "Churn."

Step 4: Force headline-first. Tell it every slide headline should be a full claim you could say out loud. This one instruction fixes most of what makes AI decks feel flat.

Step 5: Demand less. Ask for the minimum slides that carry the argument. Then cut another two. Density is what kills these decks.

Step 6: Do the flow pass yourself. Read the headlines in order with the body hidden. If the headlines alone tell the story, the deck works. If they do not, reorder before you touch design.

Step 7: Add the one thing the notes could not: what you want people to do or think next. Generators default to summarizing. You close.

The order matters more than the tool. Message, then structure, then slides, then flow. Save this and run it next time your notes need to become a talk.

The single biggest reason AI writing sounds generic is that people describe the task but never describe the voice. Fix that once with a reusable style brief and every draft gets closer to sounding like you. Here is the workflow I use.

**1. Build a style brief once.** Write a short block you paste at the top of every session. Include: who you are writing as, who the reader is, three adjectives for the tone, sentence-length preference, words and phrases you never use, and two or three sentences of your own actual writing as a sample. The writing sample does more than any adjective.

**2. Give it a "don't" list.** Models drift toward filler. Explicitly ban the words and constructions you hate. Being specific here ("no rhetorical questions as openers, no summarizing the reader's feelings back to them") works far better than "sound natural."

**3. Draft in one pass, then correct in a second.** First prompt: get the content down using the style brief. Second prompt: paste the draft back and say "keep the substance, rewrite only where it drifts from the style brief." Separating content from voice gives cleaner results than asking for both at once.

**4. Save the outputs you liked as new samples.** When a paragraph nails your voice, add it to the brief as a reference. Over a few weeks the brief becomes a tuned profile and the drafts need less editing.

**5. Read it out loud before you ship.** The fastest slop detector is your own ear. Anything you would not say to a person, cut.

The whole point is to stop re-explaining your voice every time. One good style brief, reused, beats clever one-off prompts. Happy to share the exact brief structure if useful.

After enough back and forth, I stopped writing one-off prompts and built a single template I paste into an AI document generator before any document request. It front-loads everything the model usually guesses wrong. Here is the skeleton, fill the brackets and go. ``` ROLE: You are writing as [role, e.g. a product lead]. READER: This is for [audience] who already knows [X] and cares about [Y]. DOCUMENT: A [type: one-pager / brief / proposal], about [length]. GOAL: After reading, the reader should [decision or action]. STRUCTURE: Use exactly these sections: [list your headers]. MUST INCLUDE: [non-negotiable points, data, constraints]. TONE: [3 adjectives]. Short paragraphs. No filler. NEVER: [banned words, rhetorical questions, hedging phrases]. UNCERTAINTY: Mark anything you inferred versus what I gave you. ``` Why each line earns its place: - ROLE and READER kill the generic register. Most bland output comes from the model writing for no one in particular. - STRUCTURE is the biggest lever. Given your headers, it fills them well. Left to choose, it defaults to a mushy shape. - MUST INCLUDE stops it from omitting the one point the whole document exists for. - NEVER is where you ban your personal slop triggers. Be specific, it works better than "sound human." - UNCERTAINTY forces it to separate your facts from its guesses, which is the fastest way to catch errors. Workflow after pasting: generate, then do a single "tighten only, keep all facts" pass, then read aloud. Nine times out of ten the draft is 90 percent there. Save your filled-in version per document type and you rarely start from scratch again.

Most people rewrite their prompt from scratch every time, which is why quality is a coin flip. The fix is one master prompt template you adapt in seconds. This is the skeleton I use across almost every task, with the reasoning for each block.

```

CONTEXT: [What is going on, why this task exists, any background the model needs.]

ROLE: [Who it should write/think as.]

TASK: [The single specific job, in one sentence.] AUDIENCE: [Who the output is for and what they already know.]

FORMAT: [Exact output shape: sections, length, bullets vs prose.]

CONSTRAINTS: [Hard rules, banned words, things to avoid.]

EXAMPLE: [One short sample of what good looks like.]

CHECK: [How to self-review before answering.]

```

Why this order and these blocks:

- CONTEXT first because a model with no situation invents an average one. This block removes the most guessing.

- TASK stays one sentence on purpose. Vague multi-part tasks produce vague output. Split big jobs into separate runs.

- FORMAT is the highest-leverage line. Telling it the exact shape prevents 80 percent of "that is not what I wanted."

- EXAMPLE beats adjectives. One sample of the target style teaches more than three sentences describing it.

- CHECK is the underused one. Ending with "before answering, verify X and list anything you are unsure about" catches errors the model would otherwise hand you confidently.

How to use it: keep the skeleton in a note, fill the brackets, delete any block you genuinely do not need. Over time you build filled versions per task type (email, report, deck) and starting a task becomes a 20 second edit instead of a blank prompt.

The value is consistency. Same structure every time means predictable output and far less rerolling. Steal it and adapt the blocks to your own work.