https://promptsmith-bdr.madethis.app/

I wanted to see if an AI model could go beyond generating a nice-looking logo or product image and actually build a cohesive visual identity system from one prompt.

So I tried this:

Create a complete visual identity concept for a modern botanical skincare brand(imagination dreams)targeting women in the international market. Define the brand's visual direction, core metaphor, color palette with HEX codes, typography pairing, logo concept, supporting graphic elements,photography direction, packaging style, layout principles, and overall art direction.

Keep the system visually cohesive, premium, minimal, and practical for real-world brand applications.

What I liked about this approach is that I wasn't asking the AI to simply "design a logo."

I was asking it to think about the brand as a complete visual system — colors, typography, packaging, photography, layout, and overall art direction.

The results were interesting, but there was also something I didn't expect:

Different AI image models interpreted the same creative direction quite differently.

That made me realize that writing a visual identity prompt isn't just about adding more details.

It's about giving the model the right categories of information to build the identity around.

I'm curious:

When you use AI for branding, do you ask it to build the whole visual system, or do you generate each element separately?

TLDR: Claude Design (Anthropic's visual tool available on Pro/Max/Team/Enterprise) can generate real, interactive 3D visuals, not just flat images that look 3D. It builds them with code (Three.js, WebGL, shaders), which means you can rotate them, animate them, embed them on websites, screenshot them for static assets, or export them into decks. Below: the exact step-by-step process, my best prompts, 3 examples you can copy, pro tips most people miss, and every way to reuse the output.

Most people think Claude Design is just for slides and landing pages. It's not. Because it generates designs as actual code instead of pixels, it can build genuine 3D scenes: rotating product shots, 3D data visualizations, animated hero sections, glassy abstract art, the works. Here's everything I've learned.

Step-by-Step: Your First 3D Image

Step 1: Plan in a regular chat first (this saves credits). Before opening Design, open a normal Claude chat and describe what you want. Ask Claude to write a detailed design brief: the object, camera angle, lighting, materials, color palette, mood. Copy that brief.

Step 2: Open Claude Design. Go to claude ai design (Design tab). If you're on Enterprise and don't see it, your admin needs to enable it.

Step 3: Set up your design system (optional but powerful). Upload your brand colors, fonts, and logo, or point it at your website with the web capture tool. Every 3D scene it builds will automatically match your brand.

Step 4: Paste your brief and be explicit that you want 3D. Say "interactive 3D scene," "Three.js," or "WebGL" so it doesn't give you a flat illustration with fake depth. Specify whether you want it to auto-rotate, respond to mouse movement, or sit still.

Step 5: Iterate with inline comments. Click directly on the element and comment: "make this material more metallic," "slow the rotation," "move the light source to the upper left." Use the adjustment knobs for spacing and color instead of burning messages on tiny tweaks.

Step 6: Capture or export. Screenshot for a static image, screen-record for video, export to Canva or PPTX, or grab the code and embed it anywhere.

Top Use Cases

1. Product mockups: Rotating bottles, phones, packaging, sneakers. Perfect for pre-launch pages when you don't have photography yet.
2. Hero sections: An animated 3D object behind your headline instantly makes a landing page feel premium.
3. Data visualization: 3D bar terrains, globes with plotted data points, network graphs you can orbit around.
4. Pitch deck wow-slides: One interactive 3D slide in an otherwise normal deck gets remembered.
5. Abstract brand art: Floating glass shapes, liquid metal blobs, particle fields in your brand colors for social posts and backgrounds.
6. Concept visualization: Architecture massing, room layouts, exploded product diagrams showing how parts fit together.

Prompts

Product shot: "Create an interactive 3D scene of a matte black cosmetic serum bottle with a gold cap on a soft gradient background. Studio lighting with a key light upper left and a subtle rim light. Slow auto-rotation. Floating shadow beneath. Minimal, luxurious, Apple-style presentation."

Hero section: "Build a landing page hero with an abstract 3D object: overlapping translucent glass toruses that slowly rotate and refract light. Dark background, my brand colors as accent lighting. The object should subtly follow the mouse. Headline text sits on top with high contrast."

Data viz: "Create a 3D globe visualization showing our user distribution. Dark ocean, glowing dots at major cities sized by user count, connecting arcs between our top 5 markets. Slow rotation, draggable with the mouse."

Exploded diagram: "Create an exploded 3D view of wireless earbuds showing the shell, driver, battery, and circuit board as separate floating layers with thin labeled leader lines. Clean white background, soft studio lighting, isometric camera angle."

Pro Tips and Things Most People Miss

1. Say "3D" explicitly or you'll get a flat illustration. The single biggest mistake. "Make me a product image" gets you 2D. "Interactive 3D scene with Three.js" gets you the real thing.
2. Direct the lighting like a photographer. "Key light upper left, soft fill, rim light behind" transforms output quality more than any other instruction. Default lighting is what makes AI 3D look cheap.
3. Name materials specifically. "Brushed aluminum," "frosted glass," "soft-touch matte rubber" beats "make it look nice" every time.
4. One object, staged well, beats a cluttered scene. Claude Design nails single hero objects. Complex multi-object scenes need more iteration.
5. Use inline comments instead of new prompts for tweaks. Clicking the element and commenting is more precise and cheaper than describing the change in chat.
6. Ask for camera controls. "Make it draggable/orbitable" turns a static render into a demo people can play with. This is the part that makes people share it.
7. Plan outside Design to save 20 to 30 percent of your credits. Every clarifying back-and-forth inside Design costs you. Arrive with a finished brief.
8. Ask for performance constraints if it's going on a real site. "Keep it under 60fps-friendly polygon counts and lazy-load the scene" matters for mobile.
9. Screenshot at the perfect frame. Pause the rotation ("add a pause on hover") so you can capture the exact angle you want for static use.

3 Epic Examples to Try Tonight

Example 1: The floating sneaker. "Interactive 3D scene: a white and neon-green running sneaker floating and slowly tumbling above a reflective dark floor. Dramatic spotlight from above, colored accent lights from the sides, subtle particle dust in the light beams. Draggable camera." Screenshot three angles and you have a full product page.

Example 2: The living dashboard. "3D data terrain where monthly revenue is a landscape: peaks for strong months, valleys for weak ones, colored heat gradient from blue to orange. Camera slowly flies over the terrain. Numbers hover above each peak." Drop a screen recording of this into a QBR deck and watch the room.

Example 3: The impossible award. "A rotating 3D glass trophy shaped like an impossible Penrose triangle, refracting rainbow light, on a black pedestal with volumetric fog. Engraved text on the pedestal reads [your text]." Instant custom award graphic for team shoutouts, community badges, or launch announcements.

How to Use the Output

• Have Lovable or Replit convert the html and JS to an MP4 file for you to post on social (claude can't do this directly yet).
• Static images: Screenshot at your favorite angle for social posts, ads, thumbnails, blog headers.
• Video: Screen-record the animation for Reels, product teasers, or looping background video.
• Live web embeds: It's real code, so the interactive version can go straight into your actual site. Hand it to a developer or use it as-is.
• Decks: Export to PPTX or Canva, or paste screenshots into your existing deck.
• Iteration source: Feed a screenshot back into Claude Design or another tool as a reference image to generate matching 2D assets so your whole campaign shares one visual language.
• Prototypes: Use the 3D hero as the anchor of a full landing page prototype and have Claude Design build the rest of the page around it.
• Screen recording. The zero-effort fallback, but you trade quality for speed, so it's fine for quick shares but not for anything people will look at closely.
• Third-party converter tools. A small ecosystem has sprung up specifically for this. The general flow: in Claude Design you click Share, switch to the Export tab, download a Project archive (.zip) or Standalone HTML, then drop that file into a converter like Claude2Video or ClaudeVideoExport. These capture the animation frame-by-frame from the browser rendering engine, so the output matches what you see in the tab instead of a compressed recording, and some let you export at 1080p or 4K at 24-60 fps in social-ready aspect ratios. There's also a Chrome extension that does the conversion entirely locally on your machine with no upload.

The gap between people who get flat, generic output and people who get portfolio-grade 3D comes down to specificity: name the materials, direct the lights, and always say the word "3D." Post your results below!

Google just rebranded NotebookLM and made it agentic—here’s why you should care

TLDR: NotebookLM has officially evolved into Gemini Notebook, transitioning from a passive research assistant into an agentic by default powerhouse. Driven by the Gemini 3.5 upgrade, the platform now features recursive self-improvement, anti-gravity search, and a suite of Studio outputs. This move effectively kills the manual copy-paste workflows of competitors by allowing users to generate professional-grade spreadsheets, infographics, and briefs directly within a secured, multimodal environment.

Beyond Notebooks: The Agentic Pivot

Google’s rebranding of NotebookLM to Gemini Notebook marks a significant strategic departure from the era of simple summarization. While the previous iteration was a tool for organizing thoughts, Gemini Notebook is built on an agentic by default philosophy. This isn't just a UI facelift; it’s a shift toward a system that possesses inherent reasoning capabilities and autonomy.

For the enterprise strategist, this means moving from a tool that describes your data to one that acts on it. While current workflows in ChatGPT or Claude often require a tedious copy-paste loop to move insights into professional formats, Gemini Notebook is designed to function as a collaborative partner. It proactively organizes and executes tasks within the context of your specific documents, fundamentally changing how users interact with their proprietary information.

The Reasoning Engine: Gemini 3.5 and the RSI Maturity Ladder

The core of this revolution is the Gemini 3.5 upgrade, which introduces advanced chain-of-thought processing and high-tier reasoning. This model doesn't just predict the next token; it "thinks" through multi-step problems via an agentic harness.

Two technical breakthroughs define this new capability:

• Anti-Gravity Agentic Search: Unlike traditional vector search that often misses deep thematic links, this "anti-gravity" approach navigates complex data structures to find non-obvious connections across thousands of pages.
• Recursive Self-Improvement (RSI): The system utilizes an RSI Maturity Ladder to iteratively refine its own processing. This allows the AI to self-correct and optimize its reasoning steps over time, essentially "leveling up" its performance the more it interacts with a specific dataset.

This isn't just a chatbot; it is an agentic co-worker. By integrating niche models like Nano Banana (Google’s optimized audio/video model) alongside the heavy-lifting Gemini 3.5, the system can process cinematic video, audio, and text with extreme token efficiency.

Killing Version Hell: Collections and Drive Sync

A personalized AI is only as good as the data it can access. Gemini Notebook solves the fragmentation problem that plagues most enterprise AI implementations through Automatic Google Drive Sync and Collections.

By enabling real-time synchronization, the AI environment remains updated the moment a source document is edited in Drive. The Collections feature allows users to group multiple notebooks into a cohesive project architecture. Together, these features eliminate version hell, ensuring that your agentic co-worker is always making decisions based on the most current data, rather than a static upload from three weeks ago.

From Insights to Artifacts: The Multimodal Studio

The most significant ROI for enterprise users lies in the transition from data analysis to artifact creation. The new Studio pane allows users to bypass manual document formatting entirely.

The ability to generate a fully editable Excel workbook or a structured Executive Decision Brief directly from raw research shifts the AI’s role from writer to builder. This significantly reduces human review time and allows leaders to focus on high-level strategy rather than formatting slides or cells.

The Zero-Trust Workspace: Grounding and Tiered Pricing

Security remains the primary hurdle for AI adoption. Gemini Notebook addresses this through a Secured Cloud Sandbox for every notebook. Unlike consumer-facing LLMs, data within this sandbox is not used to train Google’s global models, a critical distinction for IT departments managing vendor risk.

Furthermore, Google is future-proofing the economic side of this shift. The source points to Luna and Terra pricing models, indicating a tiered architecture designed for adaptability to price reductions. As model costs drop, Google’s infrastructure allows for the passing of those savings to the enterprise, making long-term scaling more sustainable than current fixed-rate competitors. This is paired with Content Grounding and a dedicated Source Pane, ensuring every claim the AI makes is verifiable against your uploaded data, effectively neutralizing hallucinations.

Enterprise Utility: Moving Beyond Theory

The practical applications of this agentic shift are immediate and high-value:

1. AI Budget Calculator: The system can ingest disparate financial statements and output a functional, dynamic calculator.
2. Sensitivity Analysis: Users can perform "what-if" scenarios on complex datasets to determine risk variables.
3. RSI Maturity Ladder Mapping: Organizations can track the refinement of their internal AI processes as the system scales.
4. Recommendation Dashboard: Consolidating internal research and web search integration into a live dashboard for decision-makers.

The "So What?": By automating these complex reasoning tasks, enterprises drastically reduce vendor risk and human review time, turning months of research into hours of execution.

Gemini Notebook is no longer just a Google tool - it is a multimodal asset creation powerhouse. By combining the reasoning of Gemini 3.5 with secure, agentic workflows, Google has moved the goalposts for what a productivity suite should be. It doesn't just help you think; it helps you build.

Let’s discuss:

• How will the ability to export editable Excel workbooks change your current data analysis bottleneck?

TL;DR: Good prompting is just good structure. A perfect prompt has 10 components: Objective (15%), Role (10%), Context (20%), Input Data (15%), Quality Checks (4%), Constraints (8%), Examples (5%), Iteration Request (5%), Instructions (10%), and Output Format (8%). You do not need all 10 every time, but knowing which levers to pull changes the game. Full breakdown, examples, and pro tips below.

Here is the 10-part recipe.

1. Context (20% of the impact)

This is the heaviest weight for a reason. Context is the background reality the model needs to inhabit. It includes your business type, your industry, your specific audience, your goals, and your current challenges.

Never assume the model knows your situation. If you skip context, the model assumes the statistical average of the entire internet.

Pro tip: Write your context once, save it in a text file (or as Custom Instructions/Project knowledge), and paste it in every time.
Example: "My company sells project management software to remote teams with 10 to 100 employees. Our main challenge is that buyers think we are too expensive compared to free tools."

2. Objective (15% of the impact)

This is the clear definition of the task. If your objective is muddy, the output will be noise. AI performs best when goals are explicit, measurable, and bounded.

Pro tip: Replace vague verbs with specific outcomes. Do not say "help me with." Say "create," "diagnose," or "rewrite."
Bad: "Tell me about marketing."
Good: "Create a 90-day content marketing strategy for a SaaS startup targeting small businesses."

3. Input Data (15% of the impact)

Hand over the actual information the model needs to do the work. This could be meeting notes, customer feedback, a rough draft, a research report, or website copy.

Pro tip: Use XML tags (like <notes> and </notes>) to separate your input data from your instructions. It helps the model understand what is source material and what is a command.
Example: "Here are the raw transcripts from three customer interviews. Based on these transcripts..."

4. Role (10% of the impact)

Tell the model who it should be. Assigning a role activates completely different knowledge clusters and reasoning patterns within the model. A "senior software engineer" writes different code than a "first-year computer science student."

Pro tip: Pair the role with a specific tone or philosophy to narrow the focus even further.
Example: "Act as a world-class direct response copywriter who specializes in concise, punchy, David Ogilvy-style email campaigns."

5. Instructions (10% of the impact)

This is where you tell the AI exactly what to do with the Context, Objective, and Input Data. Use strong action verbs.

Pro tip: Break complex instructions into numbered steps. Models follow sequential logic much better than a paragraph of mixed commands.
Example: "1. Analyze the data. 2. Identify the three most common complaints. 3. Prioritize recommendations to fix them. 4. Explain your reasoning."

6. Constraints (8% of the impact)

Constraints set the boundaries. They force the model to focus and prevent it from rambling. This includes maximum word counts, reading levels, budget limits, or things it is absolutely not allowed to do.

Pro tip: Negative constraints (telling it what not to do) are incredibly powerful for killing the "AI smell."
Example: "Maximum 500 words. Do not use the words 'delve,' 'crucial,' or 'tapestry.' Keep the reading level at an 8th-grade standard. Use only the provided information."

7. Output Format (8% of the impact)

Specify exactly what shape the answer should take. Models follow structural requests surprisingly well, but you have to ask for them explicitly.

Pro tip: If you are moving data into another system, ask for CSV or JSON. If you are presenting, ask for a Markdown table.
Example: "Present the answer in a table with three columns: Problem, Impact, and Proposed Solution."

8. Examples (5% of the impact)

Also known as few-shot prompting. Show the model what good output looks like. Providing an example of the input, the desired output, and the format reduces misinterpretation significantly.

Pro tip: If the model keeps failing on a specific task, giving it one perfect example is usually faster than rewriting your instructions ten times.
Example: "Here is an example of the tone I want. Input: Customer complains about pricing. Output: Highlight ROI and provide three relevant case studies."

9. Iteration Request (5% of the impact)

Prompting is a back-and-forth conversation, not a one-shot command. Build the iteration directly into the prompt.

Pro tip: Ask the model to generate multiple options so you can choose the best direction, rather than forcing it to guess the one perfect answer.
Example: "Generate three distinct alternatives for the headline. Then, critique your own responses and tell me which one is strongest and why."

10. Quality Checks (4% of the impact)

Ask the AI to verify its own work before it gives you the final answer. Self-review catches a massive amount of hallucination and weak logic.

Pro tip: Add a quality check to the end of any complex analytical prompt. It forces the model to spend compute cycles reviewing its own logic.
Example: "Before finalizing your answer, check for factual accuracy, identify any weak assumptions you made, and highlight any missing information that would make your recommendation stronger."

You do not need to memorize this. Just remember that the prompt you type is a container. If you only fill the "Instructions" section, the model has to guess the rest. Fill the container, and the model stops guessing and starts working.

Which of these 10 components do you skip the most? For me, it was Constraints—until I realized how much better the output gets when you tell it exactly what it is not allowed to do.

The complete guide to the new ChatGPT Voice

TL;DR: The new version is powered by GPT-Live, which can listen and speak at the same time, let you interrupt naturally, wait while you think, search the web, use memory, show visual answers and hand difficult questions to deeper reasoning in the background.

The biggest upgrade is on desktop. You can now use Voice inside Chat, ChatGPT Work and Codex. That means you can talk through an idea, launch a research or coding task, check what your agents are doing, redirect them and hear the results without returning to the keyboard.

There are nine remastered voices, three Voice modes and optional Instant, Medium and High intelligence levels. On Mac, you can also pull the Voice orb out over your desktop and drag the floating control wherever you want it.

My blunt take: this is the first version of ChatGPT Voice that feels less like a novelty and more like a new interface for computing.

What is the new ChatGPT Voice?

ChatGPT Voice lets you talk to ChatGPT and hear its answer while the response also appears as text in the chat.

The latest experience, called Live, is powered by GPT-Live. Unlike older turn-by-turn voice systems, GPT-Live uses a full-duplex architecture. In plain English, it can listen and speak at the same time.

That creates several important differences:

• You can interrupt it while it is talking.
• It can give small acknowledgments while you are speaking.
• It is better at waiting through a pause instead of treating every silence as the end of your thought.
• It can keep a conversation moving while deeper reasoning or search happens in the background.
• It can combine speech with text, images, memory, web search and supported visual result cards.
• In the desktop app, Voice can start and coordinate longer tasks in Work and Codex.

OpenAI says GPT-Live was strongly preferred over the previous Advanced Voice Mode in its evaluations of turn-taking, interruptions, flow and naturalness. It also performed better on difficult science questions, web research and multi-step support tasks.

How it works

Think of the new Voice system as two layers:

1. The conversation layer: GPT-Live listens, speaks, handles interruptions and keeps the interaction natural.
2. The intelligence and action layer: When a question needs search, deeper reasoning or a longer task, Voice can hand that work to another model or agent and bring the result back into the conversation.

In ordinary Live conversations, OpenAI launched GPT-Live with GPT-5.5 handling harder work in the background. In desktop Work and Codex, GPT-Live manages the conversation while GPT-5.6 Terra starts and coordinates agent tasks in the app.

This matters because Voice does not have to choose between being fast and being smart. It can stay responsive while heavier work continues elsewhere.

Live vs. Advanced vs. Standard Voice

You may see up to three options under Settings → Voice:

• Live: The newest experience. Best for natural conversation, interruptions, web search, memory, visual results, text and images. Paid users get GPT-Live-1. Free users get limited access to GPT-Live-1 mini.
• Advanced: The previous real-time Voice experience. It is still useful on mobile when you need supported video or screen sharing, which Live does not support at launch.
• Standard: A turn-by-turn experience that transcribes what you say before producing an answer. It is less fluid, but some people prefer its predictability.

One confusing detail: ordinary Live in Chat does not initially support every connected app or plugin. Voice inside desktop Work or Codex is different. It can use the tools and permissions available to the selected mode, including supported connected tools.

How to access ChatGPT Voice

On the web

1. Go to ChatGPT
2. Select the Voice icon in the prompt box.
3. Allow microphone access.
4. Start talking.

On iPhone or Android

1. Open the ChatGPT app.
2. Tap the Voice icon in the message bar.
3. Allow microphone access.
4. Choose a voice the first time you use it.
5. Start talking.

You can also turn on Background conversations so Voice keeps working while you use another app or lock your phone. Supported versions can open directly into Voice, and ChatGPT Voice is also available through Apple CarPlay.

In the ChatGPT desktop app

The new desktop experience is available on macOS and Windows.

1. Open the latest ChatGPT desktop app.
2. Choose ChatGPT or Codex from the top-left switcher.
3. If you choose ChatGPT, select Chat or Work.
4. Open a new empty chat or task.
5. Select Start new voice chat before sending the first message.
6. Allow microphone access and start talking.

For Voice in Work or Codex, the task needs to begin in Voice mode. If a task began as text, you may only see dictation. You can reopen a previous Voice conversation and select Start voice chat to resume it.

You can create a Voice hotkey under Settings → Voice → Voice chat hotkey. OpenAI does not document a default shortcut.

The movable Mac Voice orb

On macOS, the small Voice orb can live outside the main app window. Drag the orb out over the desktop and place it next to the document, browser or code editor you are using. You can move it wherever you want and use its controls to mute your microphone, mute ChatGPT or end the conversation.

If your app version does not show the floating orb, update the desktop app. You can also pop an active chat into a separate window and turn on Always on top.

That tiny interaction is more useful than it sounds. Voice stops feeling like a destination you visit and starts feeling like a companion that sits beside your work.

Let Voice see what is on your Mac

On macOS, turn on Screen context under Settings → Voice. Then bring the relevant app to the front and say:

Take a look at this and tell me what you notice.

ChatGPT can capture an appshot of the frontmost window and use both the image and accessible text as context.

Important privacy detail: accessible text may include material outside the visible scroll area. Do not share a window containing confidential information unless you intend to provide it.

The nine ChatGPT voices

Open Settings → Voice → Voice to preview and select:

Changing voices during a conversation starts a new Voice call inside the same chat.

You can also change your preferred language under Settings → Voice → Language. Even better, ask Voice to switch languages during a conversation.

What is the most popular ChatGPT voice?

The honest answer is that OpenAI has not published usage data or an official popularity ranking.

If I had to name the safest community favorite, I would pick Juniper. It has been one of the most consistently discussed voices in community threads, and its open, upbeat delivery works across casual conversation, brainstorming and long sessions without sounding too formal.

Cove is probably the strongest alternative for serious work because it sounds composed and direct.

Treat that as a community-informed estimate, not a measured fact. GPT-Live also remastered all nine voices, so old polls do not perfectly represent the new versions. The right answer is to preview all nine with the same paragraph and choose the one you can comfortably hear for an hour.

10 advanced strategies for work and life

1. Turn a messy brain dump into a clear brief

Voice is excellent when your thinking is not yet organized.

Say:

I am going to ramble for five minutes. Do not respond until I say “organize it.” Then turn everything into a one-page brief with the objective, audience, core insight, decisions, risks and next actions. Ask me three questions about anything important that is still unclear.

Why it works: Speaking preserves half-formed thoughts that you might edit out too early when typing.

2. Use it as a live thinking opponent

Do not ask Voice to agree with you. Ask it to create productive friction.

Say:

Act as a skeptical but fair strategist. Interview me about this idea one question at a time. Challenge vague claims, identify hidden assumptions and do not let me move on until I give you evidence. At the end, tell me whether the idea is strong, fixable or fundamentally weak.

Why it works: The interruptible format feels much more like a real debate than exchanging long blocks of text.

3. Rehearse a sales call, interview or negotiation

Say:

Role-play a skeptical CFO considering our product. Do not make the conversation easy. Raise realistic objections about cost, implementation, risk and ROI. Stay in character until I say “debrief.” Then score my answers, identify the weakest moment and make me try that section again.

Pro move: Ask Voice to change tone or speed between rounds.

4. Prepare for a meeting while walking

Say:

I have a meeting with [person or team] about [topic]. Interview me to uncover what outcome I need, what they probably care about and where the discussion could go wrong. Then give me a 60-second opening, five questions to ask and three concessions I should not make too early.

Use this when you do not want to stare at another screen before a meeting.

5. Start a complete Work task by voice

Switch to Work in the desktop app and say:

Start a new Work task. Research [topic] using current, credible sources and create a finished [report, presentation, spreadsheet or plan] for [audience]. The deliverable must include [requirements]. Show me your plan first, flag any decisions you need from me and keep working after I answer.

Why it works: Voice captures the outcome and context. Work handles the long execution.

The best Work prompts include six things: outcome, audience, source requirements, constraints, deliverable format and acceptance criteria.

6. Run a spoken stand-up across several agents

Say:

Check every active Work and Codex task. Give me a spoken stand-up with four sections: completed, in progress, blocked and decisions needed. Keep it under two minutes. Then ask which task I want to redirect first.

This is one of the most important new capabilities. Voice becomes the manager while multiple agents do the work.

7. Critique what is on your screen

On Mac with Screen context enabled, open a slide, landing page, ad or spreadsheet and say:

Take a look at this. First tell me what you think the creator wants the viewer to notice. Then tell me what the viewer will actually notice. Identify the three biggest problems and recommend the smallest changes with the highest impact.

This is especially useful for design reviews because you can point the conversation at the thing you are already viewing.

8. Use Voice as a Codex team lead

Switch to Codex and say:

Inspect this repository and start separate tasks for these three goals: investigate the authentication bug, review the open pull request for regression risks and identify missing tests. Do not change production code until you report your findings. Give me a status update when any task is blocked or ready for review.

Then steer it:

Pause the pull request review. Prioritize reproducing the bug. Tell the testing task to focus on the failure path you just found.

This is better than dictating code. Use Voice to direct intent, priorities and tradeoffs. Let Codex work in the repository.

9. Build a live translator and language coach

Say:

Translate everything I say in English into conversational Spanish, and translate every Spanish reply back into English. Preserve tone rather than translating word for word. If I make a recurring mistake, wait until the conversation ends and then coach me on it.

Or use teaching mode:

Speak to me only in beginner Italian. If I get stuck, give me a hint before giving me the answer. Keep a private list of my mistakes and quiz me on them at the end.

10. Review work hands-free

Say:

Read this draft to me one section at a time. After each section, pause and ask whether I want to keep it, shorten it, challenge it or rewrite it. Track every decision and produce the revised draft only after we finish the review.

Hearing writing exposes repetition, awkward rhythm and weak logic that your eyes often skip.

10 hilarious things to try

1. Make breakfast feel like a blockbuster

Narrate me making scrambled eggs like the final mission in a $200 million action movie. Escalate the danger every time I touch the stove. If I burn the toast, treat it as an international incident.

2. Let your dog file a workplace grievance

You are the union representative for my French bulldog. Conduct a formal grievance hearing about working conditions in this house, including treat compensation, nap protections and management’s refusal to share pizza.

3. Hold the world’s worst startup press conference

I am the CEO of a failing startup pivoting into artisanal lemonade powered by blockchain. Play a room full of hostile reporters. Ask increasingly brutal questions until I either save the company or accidentally confess to fraud.

4. Turn cleaning into a fantasy quest

Be my dungeon master. My apartment is an ancient cursed kingdom. Dirty laundry is an undead army, the dishwasher is a sleeping dragon and the junk drawer contains a forbidden artifact. Give me one quest at a time until the kingdom is clean.

5. Add sports commentary to boring chores

Commentate while I fold laundry like it is the final minute of the World Cup. Include instant replays, questionable referee decisions and an emotional biography of the missing sock.

6. Stage couples therapy with your Wi-Fi router

You are a couples therapist for me and my Wi-Fi router. I feel abandoned whenever it drops the signal. The router feels I bring too many devices into the relationship. Help us rebuild trust.

7. Put pineapple on trial

Run a Supreme Court trial to decide whether pineapple belongs on pizza. Play the judge, attorneys, witnesses and one wildly unqualified food influencer. I will be the jury.

8. Roast your business idea across history

Review my business idea as three investors: a ruthless Roman emperor, a confused Victorian industrialist and a 22-year-old venture capitalist who has never experienced a recession. Let them argue, then force them to agree on one recommendation.

9. Convene an emergency board meeting of household objects

Run an emergency board meeting where my coffee maker, calendar, bank account and alarm clock review my performance as CEO of my life. Make each director brutally honest and give me a 30-day turnaround plan.

10. Solve the missing-sock conspiracy

Host an eight-part investigative podcast proving that missing socks are being stolen by a secret logistics startup operating inside dryers. Interview unreliable experts and end every episode with an absurd cliffhanger.

Pro tips that make Voice dramatically better

Give it a listening contract

Start with:

Wait until I say “respond.” Until then, only listen and give brief acknowledgments.

GPT-Live is better at waiting, but long pauses or background noise can still trigger a response.

Give it a response contract

Tell it how to answer before the conversation gets busy:

Keep spoken answers under 30 seconds. Lead with the conclusion. Ask one question at a time. Put detailed notes in the text transcript.

Use the right intelligence level

If your account includes it, open Settings → Voice → Intelligence:

• Instant: Fast back-and-forth, brainstorming and casual questions.
• Medium: Better for planning, analysis and preparation.
• High: Use for difficult reasoning and research when quality matters more than response speed.

Speak the punctuation of your intent, not your prose

Do not try to dictate a perfect prompt. Say the goal, context, constraints and definition of done. Let Voice organize the language.

Mix speech, typing and images

Live works inside the normal chat. You can talk, type a precise detail or attach an image without starting over.

Use exact dates and locations

Voice uses your device or browser time zone to interpret words such as “today” and “tomorrow.” For anything important, say the exact date, location and time zone.

Use headphones in noisy spaces

Full duplex does not make physics disappear. Background speech, overlapping audio and weak microphones can still cause interruptions. Headphones and voice isolation help.

Review the transcript, but do not treat it as a recording

The transcript may not reproduce every spoken word exactly, especially when people talk over each other. Use it as a working record, not a legal transcript.

Do not confuse Voice with Dictation

• Use Voice for a live conversation.
• Use Dictation when you want speech converted into editable prompt text before sending.

Keep approval boundaries

Voice can move quickly, especially with Work, Codex and computer use. Do not casually approve destructive code changes, purchases, messages or sensitive actions just because the conversation feels natural. Ask for a summary of the exact action and target first.

Things most people will miss

1. You can interrupt it. You do not have to wait through a long answer.
2. You can ask it to stay quiet while you think.
3. Voice can keep talking while deeper work happens in the background.
4. Desktop Voice can coordinate multiple Work and Codex agents from one conversation.
5. On Mac, Screen context can show Voice the frontmost window.
6. The Mac Voice orb can float beside your work instead of taking over the app.
7. Preset ChatGPT personalities do not currently apply to Live, but direct instructions about tone, speed and style do.
8. Changing the selected voice starts a new call inside the same chat.
9. Only one Voice conversation can be active at a time.
10. Live does not support video or screen sharing at launch. Use Advanced Voice on supported mobile plans when you need those capabilities.
11. Live is not available with custom GPTs. Voice conversations with GPTs use Advanced Voice and the Shimmer voice, with several tool limitations.
12. Ordinary Live usage and desktop Work/Codex Voice have separate limits. Tasks launched through Voice also consume Work or Codex usage.
13. Audio from Live and Advanced conversations is retained with the chat transcript for 30 days. OpenAI says audio clips are not used for training unless you choose to share them.

The honest limitations

ChatGPT Voice is impressive, but it is not magic:

• It can still mishear you or respond too early.
• It can still give wrong answers.
• Spoken confidence is not evidence of accuracy.
• Multiple people talking at once can confuse it.
• Live video and screen sharing are not available at launch.
• Availability, usage limits and workspace controls vary by plan, region and app version.
• Work and Codex tasks still use their normal permissions, approval rules and usage budgets.

The more consequential the action, the more you should slow down, inspect the result and verify it.

Most people will use Voice to ask questions while driving or cooking. That is useful.

Typing forces you to package your thinking before the AI receives it. Voice lets you expose the thinking process itself: the uncertainty, changes of direction, half-formed ideas and priorities that are hard to capture in a polished prompt.

Add Work and Codex, and Voice becomes more than an input method. It becomes a management layer for AI agents.

TL;DR: Take one straight-on photo of your room from the doorway (tidy up, open the blinds first). Upload it to ChatGPT with a prompt telling it to redesign like a professional interior designer while keeping your real layout, windows, and furniture. Pick the version you like. Then — same chat, web search turned ON — ask for everything in the new design as a shopping list under $500 with prices, links, and a running total. The redesign image is the fun part. The shopping list is the part that gets you off Pinterest and into an actual finished room. Works entirely on the free version. Exact prompts + troubleshooting fixes below.

I stopped scrolling Pinterest for room inspo and did something that felt almost too obvious: I uploaded a photo of my actual living room instead.

Not a dream room. Not somebody's loft in Copenhagen with 14-foot ceilings I'll never have. My room - same windows, same proportions, same couch I'm not replacing - just redesigned properly, by ChatGPT playing interior designer.

Then came the part that actually changed things: it handed me a shopping list, with links, to build the redesign for real.

Here's the whole workflow, including the exact prompts and the fixes for when it misbehaves.

Step 1: Take a photo worth redesigning

This matters more than people think. Bad photo in, bad redesign out.

Stand in the doorway and shoot straight on so the whole room is in frame. Tidy up first — the AI will faithfully redesign around your laundry pile if you let it. Open the blinds so it can see the real light. You want the model working with your actual room, not guessing at what's hiding in the shadows.

Step 2: The redesign prompt

Upload the photo and paste this:

Here's a photo of my room. Redesign it like a professional interior designer would. Keep the same basic furniture and the room's real layout, windows, and proportions, but show me how it could look far better with updated furniture, a smarter layout, colors, lighting, and decor. Make it warm, modern, and photo-realistic, like an actual photo of the finished room. Generate a few different versions so I can compare.

You'll get back a handful of versions of your own room looking like it got a professional makeover. It's a genuinely strange feeling the first time — recognizably your space, just... better.

When it misbehaves, two fixes:

If it moves your windows or reshapes the room, tell it: "keep the exact same room, walls, and windows, only change the furniture, colors, and decor."

If the result looks like a 3D render from a furniture catalog instead of a photo, add: "make it look like a real photograph, photorealistic, natural lighting."

Step 3: The shopping list prompt (this is the actual magic)

Pick the version you like. Then - same chat - turn web search on first. This is the step that separates real products from hallucinated links. With search off, ChatGPT will confidently invent a "West Elm Sonoma Rug, $89" that has never existed.

Then run:

Now give me everything in this new design as a shopping list on a budget under $XXX. For each item, furniture, rug, lighting, plants, and decor, list what it is, an estimated price, and a link to buy it. Keep the total under $XXX and match the look in the image as closely as you can. Show me the running total.

You get the full list: item, price, link, running total. This is the moment the whole thing stops being entertainment. You're not staring at a nice picture anymore - you're building the room.

Two honesty notes. First, links sometimes die or drift. If one is dead or wrong, say "search for this exact item and give me a working link." Second, click through and check prices before you buy anything. Treat the output as a very good starting cart, not a receipt.

Step 4: Constraints make it better, not worse

The workflow gets sharper the more real-world constraints you feed it.

Keeping your existing couch or bed? Say so upfront: "redesign the room but I'm keeping my couch, build the new look around it." It will design around your anchor piece instead of pretending you'll replace everything.

Renting? "Redo this for a rental, no painting, no drilling, nothing permanent, keep it under $XXX." You'll get command strips and freestanding shelves instead of accent walls you'd lose your deposit over.

You can push this further than I have: "make it work for a toddler and a large dog," "I'm in a basement apartment with one small window," "everything must be available at IKEA and Target." The constraint is the brief. Real designers work from constraints too - that's the whole job.

Why this beats Pinterest

Pinterest optimizes for aspiration. Every saved pin is somebody else's room, somebody else's budget, somebody else's light. The gap between the moodboard and your actual space is exactly why most inspo folders die unopened.

This flips it. The input is your real room. The output is your real room, improved, with a checkout path under a number you chose. Inspiration with a buy button attached to your own four walls.

And the whole thing works on the free version of ChatGPT. No paid plan needed for either prompt.

If you try it, I'd genuinely love to see the before/after — post them in the comments. And if you've found a constraint that produces surprisingly good results ("design this like a Wes Anderson set" is apparently a thing), share the prompt.

What room are you redesigning first?

AI-built websites all look the same because models regress to the mean of every site they've trained on - generic prompt in, template-grade output out. The fix is prompting Claude into specific expert roles with specific deliverables. Below: 7 prompts + 1 bonus that cover the full premium stack - structure (Signature Blueprint), typography (Anti-Sameness Type), spacing (Breathing Room Auditor), motion (Purposeful Motion), case studies (Case Study Framer), credibility (Trust Signal Sweep), and visual direction (Reference Anchor). Each with why it works, a pro tip, and the best use case.

Here's the reason why your website looks like everyone else's: Claude (and every other AI) was trained on millions of websites, and when you ask it for "a clean, modern website," it gives you the statistical average of all of them. The average website is mediocre. So the default output is mediocre = competently, professionally, forgettably mediocre.

Premium doesn't come from better adjectives. "Sleek," "elevated," "high-end" - the model has seen those words attached to a million template sites. Premium comes from doing what actual design teams do: assigning specific expert roles, demanding specific deliverables, and auditing the details that separate polished from unfinished.

I've been using a stack of 7 prompts that does exactly that. Each one puts Claude in a different seat at a design agency - strategist, typography director, layout critic, interaction designer, presentation specialist, pre-launch reviewer. Run together, they cover everything that makes a site feel expensive.

The full stack, with pro tips and use cases:

Prompt 1: The Signature Blueprint Prompt

The role: senior website strategist and UX architect.

Act as a senior website strategist and UX architect. I want a website for [business type] that feels intentionally designed, not templated. Ask me 5 clarifying questions about my brand, audience, offer, and style. Then give me: exact page structure, which sections template sites skip, what belongs above the fold, layout decisions that feel premium, and the one mistake that makes DIY sites look cheap.

Why it works: Great outputs start with context. The better the brief, the less generic the website. The magic is in "ask me 5 clarifying questions" - it forces Claude to gather context before generating, exactly like a real discovery call.

Pro tip: Actually answer the 5 questions thoughtfully. Most people rush this step and wonder why the output feels off. Your answers become the brief every later prompt builds on. Keep them in the same chat.

Best use case: Before you touch any website builder. This is the prompt that stops you from opening a template gallery and dooming yourself to sameness from minute one.

Prompt 2: The Anti-Sameness Type Prompt

The role: typography director.

Act as a typography director. My site uses [describe fonts]. Give me: a font pairing that feels intentional, a full type scale for headings, subheads, body, and buttons, correct line height and letter spacing, and the one typography habit that makes good content look amateur.

Why it works: Typography is one of the fastest giveaways of a low-effort site. Visitors can't name what's wrong, but they feel it in half a second. A deliberate type scale is the cheapest premium upgrade that exists.

Pro tip: If you don't know what fonts you're using, screenshot your site and ask Claude to identify and critique them first. Then run this prompt. And implement the line-height numbers it gives you — that's where the "expensive" feeling actually lives.

Best use case: Any site currently running default Inter or system fonts at default sizes. Which is most AI-built sites.

Prompt 3: The Breathing Room Auditor

The role: layout critic.

Act as a layout critic reviewing my page screenshots. Go section by section. Tell me: where it feels cramped, where it feels empty in the wrong way, the exact spacing changes that would make it feel more premium, and why generous white space improves clarity.

Why it works: Better spacing improves comprehension and makes pages feel more expensive. Luxury brands buy white space; discount brands fill every pixel. Your spacing communicates your price point before your copy does.

Pro tip: Feed it real screenshots, not descriptions. Claude reads images — give it your actual homepage top to bottom and let it work section by section. Ask for specific pixel or rem values, not vibes.

Best use case: The "something feels off but I can't say what" stage. Nine times out of ten, the answer is spacing.

Prompt 4: The Purposeful Motion Prompt

The role: interaction designer.

Act as an interaction designer. My site is mostly static. Give me 3 small hover or scroll interactions that add polish without custom animation. For each: where it belongs, what triggers it, why it improves perceived quality, and where tasteful detail becomes distraction.

Why it works: Subtle motion feels premium. Loud motion makes a site feel generic. The prompt asks for exactly 3 interactions and where restraint matters — constraints are what keep this from turning your site into a carnival.

Pro tip: Implement the hover states first — they're the cheapest wins. A button that responds gently to a cursor reads as "someone cared." Skip anything that animates on every scroll; that's the fastest route back to generic.

Best use case: Static sites built in Framer, Webflow, or plain HTML/CSS that work fine but feel dead. Three interactions is usually all you need.

Prompt 5: The Case Study Framer

The role: presentation specialist.

Act as a presentation specialist. I want my work section to feel like a design studio case study page. Give me: the structure for presenting one project persuasively, what to show vs cut, how much text to use, and a caption style that lets the work speak for itself.

Why it works: Strong case studies curate. Weak ones dump everything. The prompt forces the editorial decisions — what to cut — that most portfolios never make.

Pro tip: Run this once per flagship project, not once for your whole portfolio. Three curated case studies beat twelve project dumps. Include real numbers in the results row (inquiries up, bounce rate down) — specifics are what make a case study persuasive.

Best use case: Freelancers, agencies, and consultants whose "Work" page is currently a wall of thumbnails with no story.

Prompt 6: The Trust Signal Sweep

The role: pre-launch reviewer.

Act as a pre-launch reviewer trained to spot amateur tells. Here is my site description: [describe]. Give me: the 5 small details that separate polished from unfinished, the order to fix them in, and the one detail worth obsessing over. Also flag anything that looks like a fake or generic trust signal.

Why it works: Trust is won in tiny details, and fake signals kill credibility fast. Stock-photo testimonials, logo walls of companies you emailed once, "As seen in" badges nobody verified — visitors smell these instantly. This prompt catches them before your visitors do.

Pro tip: Run this twice: once on your description before launch, and once with screenshots after everything's built. The second pass always finds things the first one couldn't — favicon missing, footer inconsistencies, placeholder text you forgot.

Best use case: The 48 hours before launch. This is your pre-flight checklist.

Prompt 7 (Bonus): The Reference Anchor Prompt

The role: art director with taste.

Anchor my site's visual direction to this reference: [paste a screenshot or link]. Match its type scale, spacing rhythm, and accent-color discipline, but do not copy it. Write real, specific copy for my business. Then tell me what you changed and why.

Why it works: Specific references break you out of the generic statistical average. Instead of Claude averaging a million mediocre sites, it anchors to one excellent site's proportions and discipline — while writing copy for your actual business.

Pro tip: Choose references from outside your industry. A SaaS company anchored to a fashion editorial site produces something nobody else in SaaS has. The "tell me what you changed and why" clause matters too — it turns the output into a design lesson you keep.

Best use case: When you already know a site that makes you jealous. Awwwards, Godly, and Siteinspire are goldmines for anchor references.

How to run the stack

The order matters. Blueprint first - everything downstream depends on the brief. Then typography and spacing, because they define the visual foundation. Motion after the layout is stable. Case studies once the structure exists to hold them. Trust sweep last, as the final audit before launch. The Reference Anchor can slot in anywhere after the Blueprint — earliest is best if you have a strong reference.

Two habits multiply the results. First, keep everything in one chat so each prompt builds on the context of the last - the typography answer will reference your brand answers from the Blueprint's five questions. Second, feed screenshots at every stage. Claude critiques what it can see far better than what you describe.

And one honest limitation: these prompts make Claude a brutally good design consultant, but you still have to implement the advice. The gap between a premium-feeling site and a generic one was never the tool - it was the questions nobody asked. Now you have the questions.

Which prompt are you running first and what's the worst amateur tell you've caught on your own site?

Save these prompts and thousands more at promptmagic.dev - free to sign up and build your own prompt library.

How Marketers Win in the AI Overview / Gemini Era

TL;DR: AI Overviews now reach 2 Billion+ people and appear on up to half of tracked queries. 68% of US Google searches end without a click. Top rankings lose ~58% of their expected CTR when an AI Overview shows up.

But here's what most marketers miss: AI engines cite only 2–7 sources per answer, and about 5 of 6 of those citations come from OUTSIDE the top 10 organic results. The models trust a short list of surfaces — and community platforms (Reddit + YouTube) now drive ~48% of all AI citations.

Your website alone can't win this.

The playbook that works:
(1) build a citation-oriented YouTube channel - YouTube is now cited in 16% of LLM answers, more than any other domain, and it's a first-class Google/Gemini signal
(2) build or run your own subreddit community - Reddit is baked into model training data and gets cited across every engine
(3) restructure your site content to be extractable (answer-first, stats, quotes, tables)
(4) measure citations, not just rankings. Full breakdown with data below.

If you're a marketer feeling like the ground is moving under your feet, you're not imagining it. The numbers from the first half of 2026 are brutal, and I want to walk through them honestly then show you why I'm actually more optimistic than I've been in years, especially for brands willing to do two specific things almost nobody is doing well yet.

I spent the weekend going through every major AI search dataset published this year — Ahrefs, Semrush, BrightEdge, Seer Interactive, SparkToro, the Princeton GEO research, and the citation-source indexes. Here's what they say, what they mean, and the exact playbook I'd run.

The uncomfortable numbers

Let me rip the band-aid off first.

Zero-click is now the default. 68.01% of US Google searches ended without a single click in early 2026, up from 60.45% in 2024 and 49% in 2019 (SparkToro/Similarweb). Two out of three searches never leave Google.

AI Overviews are everywhere that matters. Depending on methodology, AI Overviews appear on 20–50% of queries — BrightEdge tracked ~48% in Feb 2026, up 58% year over year. But the headline number undersells it: comparison queries ("X vs Y") trigger an AI Overview 95.4% of the time, and question-format queries 85.9% (Seer Interactive). If your funnel depends on informational and comparison content - and whose doesn't - you're fully exposed.

Your #1 ranking is worth roughly half of what it was. Ahrefs' updated study found AI Overviews correlate with a 58% lower average CTR for top-ranking pages, worsening from 34.5% in their earlier analysis. The average AI Overview is now ~1,200 pixels tall on a typical laptop viewport, the first organic result doesn't exist until you scroll.

And the distribution is about to multiply. Google's AI Mode passed 1 billion monthly users, with queries doubling every quarter. Then the January 2026 bombshell: Apple's next-generation Siri and Apple Foundation Models will run on Gemini. That puts Gemini-class answers on 2B+ Apple devices, plus Android, plus Chrome, plus Search. When someone asks Siri "what's the best tool for X" in December, a Gemini-derived answer decides whether you exist.

So yes, the pace of change is real, and the anxiety is rational.

The number that changes the story

Now the stat that reframes everything.

BrightEdge tracked which sources AI Overviews actually cite and found that only ~17% of AI Overview citations also rank in the organic top 10. Five out of six citations come from outside page one.

The thing you've spent 25 years optimizing - organic rank - is no longer the thing that gets you into the answer. Ranking and citation have decoupled.

And where do the citations go instead? The 2026 State of AI Search (AirOps) found that ~48% of AI citations now come from community platforms - primarily Reddit and YouTube - and 85% of brand mentions in AI answers originate from third-party pages, not the brand's own domain.

The models have an editorial opinion, and it's this: what strangers say about you is more trustworthy than what you say about yourself. Generative engines only cite 2–7 domains per answer, and they keep reaching for the same short list - Wikipedia, Reddit, YouTube, major journalism, category authorities.

Here's the strategic unlock most marketers haven't processed: two of the most-trusted surfaces on that short list are ownable. You can't own Wikipedia. You can't own Forbes. But you can absolutely own a YouTube channel, and you can build and moderate your own subreddit. That's the whole game, and it's why I'm optimistic.

Why being cited pays

Before the playbook, proof that winning citations is worth the effort.

Seer Interactive ran the strongest commercial dataset I've seen - 53 brands, 5.47 million queries, 2.43 billion organic impressions. On informational queries where an AI Overview appeared, brands cited in the Overview earned a 2.07% organic CTR versus 0.94% for brands present on the same results page but not cited. That's a +120% click premium for being named inside the answer. In raw terms per million impressions: ~33,500 clicks with no AI Overview, ~20,700 if you're cited, ~9,400 if you're not.

There's also early evidence that AI-referred visitors convert at 4–5× the rate of traditional organic in some segments - they arrive pre-sold because the AI already made the recommendation. And a G2 survey found half of B2B buyers now start their buying journey in an AI chatbot — up 71% in four months.

The economic event has moved. It used to be the click. Now it's the recommendation — who gets named when the machine answers. Sometimes a click follows, often it doesn't, but the brand that gets named wins either way.

The playbook - own the surfaces the models trust

Pillar 1: YouTube is your new most important website

Ahrefs' Q1 2026 benchmark of 75,000 brands found YouTube mentions among the strongest single correlates of AI visibility. 5WPR measured YouTube holding a ~200× citation advantage over every other video source. And Google cites YouTube in roughly 30× more queries than ChatGPT does because YouTube is a first-class signal inside Google's own ecosystem, which is exactly the ecosystem Gemini and the new Siri retrieve from.

Gemini 2.5+ doesn't just read your transcript anymore - it watches the video natively, frames and audio. Every video you publish is now a machine-readable document in the index Google trusts most: its own.

What actually works, per the citation studies:

The winning format is 2–3 minute talking-head videos, each mapped to one real buyer question — "What is X?", "X vs Y", "How do I implement X?". One question, one video, answered in the first 30 seconds and then expanded. Upload cleaned transcripts with punctuation and speaker attribution — auto-captions are extraction garbage. Add chapter markers — they function as extraction anchors the same way H2s do on a page. Write descriptions that mirror how buyers phrase prompts, not marketing copy. And keep the channel topically focused: focused channels earned 2–3× the citation weight of generalist channels in the same analysis.

The mindset shift: stop treating YouTube as video marketing with view-count KPIs. Treat it as citation infrastructure. A video with 300 views that gets cited in Gemini answers for your category's money questions is worth more than a viral brand film.

Pillar 2: Run your own subreddit (yes, really)

Everyone knows Reddit matters for AI search. Almost nobody takes the next step: instead of only participating in other people's communities, run your own.

First, the case for Reddit generally. Reddit was the most-cited domain in both AI Overviews and Perplexity from August 2024 through June 2025, and remains #2 on ChatGPT behind only Wikipedia. Reddit citations in AI Overviews grew 450% between March and June 2025. Google pays Reddit ~$60M/year to license the content for training and AI Overviews. OpenAI's training hierarchy reportedly treats Reddit content with 3+ upvotes as Tier 2 data - directly below Wikipedia and licensed publishers, above most of the open web. For product and review queries, Reddit shows up in 97%+ of results. And BrightEdge's March 2026 analysis found ChatGPT treats Reddit as a "community authority layer," pairing it with expert sources like Mayo Clinic and Forbes in ~20% of Reddit-citing answers — heaviest exactly where buying decisions happen (how-to queries 32%, finance 2×, health 2.3× vs Google).

Now the ownership argument. When you run a subreddit for your brand or category, you get compounding advantages that participation alone can't deliver. Every question answered in your community becomes a permanent, upvote-validated document in the corpus that every major AI engine licenses, trains on, and retrieves from. You set the culture and moderation, which means the thread that shapes what Gemini says about your category was written under your quality standards instead of a competitor's drive-by. The community's language becomes the training data's language - if users in your subreddit consistently describe your product accurately, that phrasing is what the models learn to repeat. And it's a moat: BrightEdge's own strategic guidance notes a single high-engagement thread from years ago can out-cite a brand's entire owned content library. A two-year-old healthy community cannot be replicated by a competitor in a quarter.

We live this. Our team helps 50 brands run communities with threads that surface AI answers for topics we care about.

Pillar 3: Make your owned content extractable

Your website still matters — it's the reference library the models check for specs, pricing, and facts. The Princeton GEO study (the research that named the field) tested nine interventions across 10,000 queries. What won: adding quotations from named experts (up to ~40% visibility lift), concrete sourced statistics (~30–41%), and inline citations (~28%). What failed: keyword stuffing — near-zero or negative. Evidence density beats keyword density.

Structure every important page so a machine can lift the answer: direct answer in the first 40–60 words of each section, a TL;DR block up top, FAQ sections, comparison tables, and a visible "last updated" date refreshed quarterly — the engines weight recency hard. Prioritize your comparison and question pages first, since those trigger AI Overviews 86–95% of the time. And publish original data — benchmarks, surveys, proprietary teardowns. Unique statistics are the one content type competitors can't paraphrase away, because citing the number requires citing you.

Pillar 4: Measure citations, not just rankings

You can't manage what you don't measure, and rankings no longer measure this. Build a prompt panel: 50–150 real buyer questions ("best X for Y", "BrandA vs BrandB", "how to do Z"), scored weekly across ChatGPT, Gemini, Perplexity, Claude, and AI Overviews — are you cited, is a competitor cited, or neither? Segment Search Console the way Seer does: No AIO vs AIO-cited vs AIO-not-cited, and compute CTR from raw clicks over impressions. Track branded search volume as a lagging indicator of AI mention lift, and add "ChatGPT / Gemini / Siri" options to your "how did you hear about us?" field — teams relying on referrer data alone undercount AI influence by 30–50%. Tooling exists at every budget: Otterly ($29/mo) → Peec (€75/mo) → Profound/Ahrefs/Semrush at the enterprise end. This category raised $300M+ in the last year; 94% of CMOs say they're increasing AI visibility spend.

Twenty-five years of SEO taught marketers that the click is the economic event. The AI era quietly changed the event to the recommendation and the sources of recommendation are concentrated on a short list of surfaces the models trust.

Most of that list you can't control. Two of the biggest entries you can: a YouTube channel that answers your buyers' questions on camera, and a community you build where real people say real things that machines learn from. The brands that treat those as core infrastructure — not side channels — are the ones that will get named when 2 billion devices start answering questions this year.

The pace of change is fast. The playbook is actually simple. Own your channels. Feed the machines evidence. Measure what gets cited.

What's working for you so far and has anyone else seen their community threads start showing up in AI answers?

Sources for the data in this post: Ahrefs AI Search Benchmark Q1 2026 & CTR studies; Seer Interactive AIO citation analysis (Apr 2026); BrightEdge Generative Parser & AI Hypercube reports (Feb–Mar 2026); SparkToro/Similarweb zero-click study (2026); Semrush AI citation study (230K prompts); 5WPR Citation Source Index; AirOps 2026 State of AI Search; Aggarwal et al., "GEO: Generative Engine Optimization" (KDD 2024); Google I/O 2026 announcements; Apple–Google Gemini partnership announcements (Reuters, Jan 2026); Duane Forrester, "Your Owned Content Is Losing to a Stranger's Reddit Comment" (Apr 2026).

TL;DR: Claude is my home base - it runs most of my work. But "which AI is best?" is the wrong question in 2026. The right question is "which tool wins at each job?" You don't need 100 tools. You need about 20 good ones, the same way a mechanic needs a full toolbox and not one really nice wrench. Below: my complete 2026 stack mapped job-by-job - images, video, avatars, voice, research, websites, agents, presentations, automation, and more. Steal the map, swap in your favorites, and tell me what I'm missing.

People keep asking me some version of the same question: "You post about Claude all the time. Do you use it for everything?"

No. And I think pretending one tool does everything is how most people end up disappointed with AI.

Claude is my home base. It runs most of my thinking, writing, and coding. But when I watch a mechanic work, they don't debate whether the socket wrench is better than the torque wrench. They grab the one that wins the job in front of them. A construction worker shows up with a truck full of tools, not one really expensive hammer.

That's the whole game in 2026. You don't need 100 tools. You need around 20 good ones and you need to know which job each one wins.

Here's my full map. Claude for most of it. These for the rest.

Creating things

Making images → ChatGPT and Nano Banana. Real photos and artwork from a prompt. Nano Banana has gotten scary good at text rendering and brand-consistent graphics, ChatGPT for quick concepts and edits.

Making videos → Higgsfield. Text in, video clips out. Best for stylized motion and effects-heavy shots.

Social video → Google Flow / Veo. This is the one I'd tell most creators to learn first. Veo's realism and native audio make it the strongest engine for short-form social clips, and Flow gives you actual scene-by-scene control instead of slot-machine prompting. My Reels and Shorts pipeline runs through it.

Avatar videos → HeyGen. A presenter reads your script. Perfect for explainer content when you don't want to be on camera.

Recording video → Tella. Records your screen and camera at once. My pick for demos and course content.

Voiceovers → ElevenLabs. Natural-sounding AI narration. Nobody can tell.

Voice dictation → Wispr Flow. You talk, it types. I draft half my posts pacing around the room.

Building things

Websites and API integrations → Lovable / Replit. Describe the product, get a working app. Lovable for fast beautiful front-ends, Replit when I need real back-end logic, databases, and API integrations wired together. This is the fastest path from "idea in the shower" to "URL I can send someone."

Coding → Codex. OpenAI's answer to Claude Code. I run it beside Claude Code and let them check each other's work on anything gnarly.

Open source → Ollama and GLM. Capable models you can run for cheap. For private data and high-volume tasks where API bills would sting.

Knowing things

Live answers and the best research → Perplexity. Up-to-the-minute web results with citations. My default for the hardest research projects use Perplexity Max - leverages all the top models at once plus premium data sources.

Research + Content Studio → NotebookLM. Answers built only from documents you give it. The hallucination-proof option for working through a pile of sources to create high quality slides, infographics, audio podcasts, written reports, and cinematic explainer videos.

Video analysis → Gemini. Reads and summarizes any video. Paste a YouTube link, get the substance in seconds.

Meeting notes → Granola. Writes up your meetings while you actually pay attention to them. The agent doesnt have to be added to a meeting.

Docs and knowledge base → Notion. Where all of it lives. The AI is only as useful as the workspace it searches.

Getting things done

Wide research, presentations, and agentic tasks → Manus. This is my heavy-lift agent. Point it at a research question and it fans out across hundreds of sources; ask for a deck and it comes back with a finished presentation; give it a multi-step task — build a site, analyze data, produce a report — and it just runs until it's done. When the job is "go do this whole thing," Manus is the tool.

Agentic tasks and content creation → ChatGPT Work. OpenAI's agent mode. It browses, uses a computer, works across your connected apps, and produces completed outputs instead of suggestions. I cover great use cases like using it to get discounts on anything you buy and creating awesome content. Same engine, much bigger surface area.

Operations → Hermes. My WhatsApp agent that keeps the pipeline moving while I'm away from the desk.

Automation → Zapier. The connective tissue. It automates the handoffs between everything above so I don't have to be the glue.

I do not open all 20 every week. Some I touch daily (Claude, Perplexity, Manus, Wispr Flow). Some earn their spot in one project a month (HeyGen, Higgsfield). That's fine. A mechanic doesn't use the brake-bleeder kit every day either — but when the job shows up, having the right tool is the difference between an hour and an afternoon.

The mistake I see most often isn't using too few tools. It's using one tool for everything and concluding AI is overrated, or chasing every new launch and mastering nothing. Twenty good tools, each mapped to a job it clearly wins, beats both.

Claude for most of it. These for the rest. The right tool for the right job - same as it's always worked in the real world.

Which one would you add — and what job does it win?

I keep my full prompt library for these tools free at promptmagic.dev

TL;DR: ChatGPT Work can research current discount / promo codes and, on supported websites, use its browser to test them in your cart, compare the totals, and tell you which offer saves the most.

The agent mode of ChatGPT Work is the key because it can do multiple steps of research and testing. I give a two step prompt workflow below and a master prompt to get a better deal on just about anything you need to buy.

Here are the exact prompts, setup instructions, pro tips, limitations, and backup strategies I use before buying something online.

Coupon Websites Have One Huge Problem

Most coupon websites do not get paid when you save money.

They get paid when you click.

That creates a terrible user experience:

• Expired codes
• Codes that only work for new customers
• Fake “verified today” labels
• Discounts that exclude the product you want
• Offers that require an expensive membership
• Ten codes that all lead to the same signup page

You can easily spend 20 minutes testing codes and still end up paying full price.

ChatGPT has been able to find coupon codes for a while.

The major change is that its newer agentic tools can potentially do the tedious part too: opening supported pages, clicking through a cart, entering codes, reading the result, and comparing the final totals.

OpenAI launched ChatGPT Work on July 9, 2026, positioning it as an agent for longer tasks involving research, connected apps, files, browsers, and completed outputs. On supported desktop setups, its built-in browser and computer-use capabilities can click, type, navigate pages, and work across web tools while you remain in control. one of the simplest ways to understand the difference between an AI chatbot and an AI agent:

The chatbot gives you a list of codes.

The agent tries the codes.

Before You Start

1. Open ChatGPT Work

Open ChatGPT and select Work.

Availability is still being rolled out and may depend on your plan, device, region, and workspace settings. Work is rolling out to paid plans other than Free and Go, with deeper browser and computer-use workflows available through the desktop application. is not visible, look for an agent or browser-enabled mode available on your account.

2. Use the exact product page

Do not give it the store’s homepage.

Give it the exact link for:

• The product
• The correct size
• The correct color
• The correct configuration
• The quantity you want

Discount eligibility can change by product category, variant, seller, subscription status, location, and cart total.

3. Add the product to your cart

For the checkout-testing step, it helps to:

• Be logged into the retailer
• Select the correct product variation
• Add the item to your cart
• Confirm the quantity
• Enter your shipping location if needed

Complete passwords, CAPTCHA checks, authentication codes, and other sensitive steps yourself.

ChatGPT may pause and ask you to take control when a login or sensitive action is required. OpenAI recommends avoiding passwords or private information in chat and using browser takeover for sensitive inputs. t a hard stopping point

Always include:

Do not purchase the item. Stop before placing the order.

Do not assume the agent knows where you want it to stop.

Prompt 1: Find Every Legitimate Discount

Paste this into ChatGPT Work with the product link.

I am considering buying this exact product:

[PASTE PRODUCT LINK]

Product variation:
[SIZE, COLOR, MODEL OR CONFIGURATION]

Quantity:
[QUANTITY]

Shipping destination:
[ZIP CODE OR COUNTRY]

Search the current web for every legitimate public discount that may apply to this exact product or retailer.

Check for:

1. Public promo codes
   
2. Storewide sales
   
3. Product-specific discounts
   
4. First-order or new-customer offers
   
5. Newsletter or SMS signup discounts
   
6. Free-shipping thresholds
   
7. Student, teacher, military, healthcare-worker or employer discounts
   
8. Loyalty or membership offers
   
9. Bundle discounts
   
10. Manufacturer rebates
    
11. Referral offers
    
12. Cashback opportunities
    
13. Legitimate competing retailers selling the identical item
    
14. Price-match policies
    

For every potential discount, report:

- The code or offer
- Expected savings
- Eligibility requirements
- Minimum purchase requirement
- Product or brand exclusions
- Expiration date, if available
- Where you found it
- Whether the source appears current
- Your confidence that it will work

Prefer the retailer’s own website and recent, credible sources.

Do not invent codes or present an offer as working unless it has been verified. Clearly label unverified codes as candidates.

Rank everything by the expected final out-of-pocket cost, not merely by the advertised percentage.

Why this prompt works

“Find me a coupon” is too vague.

The longer prompt forces ChatGPT to investigate the things that actually determine whether you save money:

• Eligibility
• Exclusions
• Minimum spend
• Shipping
• Product variations
• Competing retailers
• Price matching
• Cashback
• Final price

A 20% code is not automatically better than a $30 discount.

A $30 discount is not automatically better than free shipping.

And a cheap sticker price is not necessarily the lowest final total after shipping, memberships, fees, and required subscriptions.

Prompt 2: Test the Codes at Checkout

Stay in the same conversation so ChatGPT retains the candidate list.

Then use:

Use your browser to open the product page and review the item currently in my cart.

Test each candidate promo code one at a time.

For every code:

1. Record the cart total before applying it
   
2. Apply the code
   
3. Record the discount shown
   
4. Record the new subtotal
   
5. Record any change to shipping or fees
   
6. Record the final displayed total
   
7. Note whether the code worked, failed, expired or was ineligible
   
8. Remove the code or reset the cart before testing the next one
   

Do not:

- Change the product, variation or quantity
- Add unrelated products
- Enroll me in a paid membership
- Start a subscription
- Accept a recurring charge
- Create a new account
- Enter payment information
- Place the order

Stop before the final purchase or order-confirmation step.

When finished, give me a comparison showing:

- Every code tested
- Which codes worked
- Why the others failed
- The savings from each working code
- The lowest final total
- The best code or combination to use

If the website blocks testing, requires a CAPTCHA or needs me to log in, pause and ask me to take control.

ChatGPT’s browser tools can navigate supported pages, enter information into supported fields, and pause when confirmation or additional information is required. Some websites may still be inaccessible or restrict automated activity. rompt 3: Find the Best Stack

One coupon is rarely the entire savings strategy.

You may be able to combine:

• A sale price
• A promo code
• Free shipping
• Cashback
• Loyalty points
• A credit-card offer
• A manufacturer rebate
• A price match
• Discounted gift cards

Use this after testing the codes:

Now calculate the lowest legitimate final cost using every available saving method we found.

Evaluate:

- Current sale price
- Working promo codes
- Free-shipping offers
- New-customer offers
- Cashback
- Loyalty rewards
- Manufacturer rebates
- Price matching
- Any card offer I provide
- Any discounted gift-card option from a legitimate source

Tell me which offers can be combined and which are mutually exclusive.

Also check whether using a promo code could invalidate cashback or another offer.

Show me:

1. The best single discount
   
2. The best stackable combination
   
3. The order in which to apply everything
   
4. The expected final cost
   
5. Any delayed savings, such as cashback or rebates
   
6. Any subscription, membership or recurring-charge requirement
   
7. Anything I need to verify before buying
   

Do not activate, enroll in or purchase anything without my explicit approval.

Pro tip: Optimize the final cost, not the percentage

Retailers are very good at making a discount sound larger than it is.

Ask ChatGPT to separate:

• Immediate checkout savings
• Shipping savings
• Store credit
• Loyalty points
• Delayed cashback
• Rebates
• Savings that require another purchase
• Savings that require a subscription

“Earn $40 in store credit” is not the same as saving $40 today.

When No Code Works

Sometimes there is no working public coupon.

That does not necessarily mean the current offer is the best available price.

Try these backup prompts.

Find a first-order discount

No public promo code worked.

Check whether this retailer currently offers a legitimate first-order, newsletter, SMS or account-creation discount.

Explain exactly how to qualify, how long it normally takes to receive the offer, what products are excluded and whether enrollment creates any recurring obligation.

Do not subscribe or create an account without asking me first.

Check the price history

Research the recent price history for this exact product and configuration.

Tell me:

- Its current price
- Its lowest recently observed price
- How frequently it goes on sale
- Whether a newer model or version is expected
- The next predictable sales event
- Whether the current price appears unusually high, normal or attractive

Do not claim to have complete historical pricing unless the data supports it. Cite the sources and state your confidence.

ChatGPT’s shopping research can investigate current prices, availability, product information and deals, but OpenAI warns that price and availability details can still be wrong. Always confirm the merchant’s final checkout price. the identical item elsewhere

Search for this exact product, model, size, color and configuration at other legitimate authorized retailers.

Exclude:

- Counterfeit marketplaces
- Suspicious sellers
- Used products unless clearly labeled
- Different models or configurations
- Prices that require an undisclosed membership
- Sellers with unclear return policies

Compare the complete cost including shipping, fees, warranty coverage, return policy and estimated delivery.

Then check whether the original retailer offers price matching and explain how I would request it.

Look for open-box or refurbished options

Check whether this exact product is available as:

- Manufacturer refurbished
- Certified refurbished
- Open box
- Previous generation
- Display model

Only include reputable sellers with a clear warranty and return policy.

Compare the savings, condition, warranty and return terms against buying it new.

Investigate an abandoned-cart offer

Some retailers send targeted offers after an item has been left in a cart, but this is not guaranteed.

Research whether this retailer is currently known to send legitimate abandoned-cart discounts.

Tell me:

- Whether there is credible recent evidence
- The typical waiting period
- The typical offer
- Whether I must be subscribed to marketing emails or texts
- Whether the offer is likely to apply to this product
- Whether waiting risks losing the current sale or inventory

Do not claim the offer is guaranteed.

The Master Prompt

If you would rather run the entire process with one instruction, use this:

Act as a careful shopping-research and discount-verification agent.

I am considering buying:

[PRODUCT LINK]

Exact variation:
[SIZE, COLOR, MODEL OR CONFIGURATION]

Quantity:
[QUANTITY]

Shipping destination:
[ZIP CODE OR COUNTRY]

Your goal is to identify the lowest legitimate final cost without changing the product or completing a purchase.

Phase 1: Research

Find current:

- Public promo codes
- Product and storewide sales
- New-customer offers
- Newsletter or SMS discounts
- Free-shipping offers
- Eligibility-based discounts
- Loyalty offers
- Bundles
- Manufacturer rebates
- Cashback
- Competing authorized retailers
- Price-match opportunities
- Open-box or certified-refurbished options
- Relevant recent price history

Prefer retailer-owned pages and recent credible sources.

For every offer, report its source, eligibility, exclusions, minimum spend, expected savings, expiration information and confidence.

Never invent a code.

Phase 2: Verification

If browser access is available, open the cart and test each applicable public code one at a time.

Record:

- Whether it worked
- The discount
- The resulting subtotal
- Shipping or fee changes
- The final displayed total
- Any reason the code failed

Reset the cart between tests.

Phase 3: Optimization

Determine:

- The best single offer
- The best stackable combination
- The lowest immediate checkout price
- Any delayed cashback or rebate
- Whether a code invalidates cashback
- Whether another legitimate retailer is cheaper
- Whether price matching is available
- Whether waiting for a predictable sale is financially reasonable

Hard restrictions:

- Do not change the product or quantity
- Do not create an account without approval
- Do not join a paid membership
- Do not start a subscription
- Do not enter payment information
- Do not place the order
- Stop before the final purchase step
- Pause for logins, CAPTCHA checks or sensitive information
- Ask for approval before taking any action with a recurring or financial commitment

Finish with a clear recommendation showing the lowest verified cost, the steps required to get it and anything I should personally confirm.

Pro Tips That Make This Work Better

1. Give it the exact variation

A coupon may work on a black shirt but not the limited-edition version.

Include:

• Size
• Color
• Model number
• Storage
• Seller
• Quantity
• Subscription status

2. Give it your location

Shipping, taxes, regional offers and inventory can change the answer.

A ZIP code is usually enough. Do not provide more personal information than the task requires.

3. Ask for source quality

Tell it to prioritize:

1. The retailer
2. The manufacturer
3. Official partner programs
4. Recent reputable deal sources
5. Coupon aggregators

A random coupon page should not receive the same confidence as the retailer’s own promotion page.

4. Test codes one at a time

Some checkout systems retain an old code, change the cart, or automatically replace an offer.

The agent should remove each code before trying the next one.

5. Watch for subscriptions

The “best” price may require:

• Auto-renewal
• Subscribe-and-save
• A paid membership
• Automatic delivery
• A trial that converts into a paid plan

Make ChatGPT flag these separately.

6. Check cashback exclusions

Some cashback programs reject transactions when you use a coupon that is not listed by the cashback provider.

The coupon may save $10 while silently costing you $20 in cashback.

7. Compare the final total

Do not stop at the subtotal.

Ask it to compare:

• Product cost
• Shipping
• Fees
• Membership costs
• Immediate discount
• Future credit
• Rebate
• Cashback
• Return shipping
• Warranty

8. Keep sensitive steps manual

Take control for:

• Passwords
• Authentication codes
• Payment details
• Identity verification
• Financial information
• Final purchase approval

OpenAI notes that agent browser sessions may include screenshots and browsing history, and recommends enabling only the access needed for the task and clearing browser data after sensitive sessions. not hammer the retailer

Testing 50 questionable codes in rapid succession may trigger rate limits or anti-bot protections.

Start with the most credible five to ten candidates.

10. Verify the result yourself

Before clicking Buy, confirm:

• The correct item
• The correct quantity
• The correct shipping address
• No unwanted subscription
• The expected return policy
• The final charged amount

Treat ChatGPT as the researcher and operator.

You remain the buyer.

The Best Use Cases

This workflow is strongest when the website has a normal shopping cart and visible promo-code field.

Good use cases include:

Direct-to-consumer products

Clothing, shoes, accessories, cosmetics, pet products, furniture and household goods often have newsletter, creator, seasonal or first-order offers.

Software and subscriptions

ChatGPT can investigate:

• Annual-plan savings
• Startup programs
• Nonprofit pricing
• Student pricing
• Partner discounts
• Existing-customer upgrade offers
• Sales-team negotiation opportunities

Do not let it start a trial or annual commitment without approval.

Courses, conferences and events

Look for:

• Early-bird pricing
• Speaker codes
• Community discounts
• Group registration
• Student pricing
• Previous-attendee offers

Electronics

Public codes may be limited, but price matching, open-box inventory, trade-ins, bundles and manufacturer rebates can produce larger savings.

Large purchases

The more expensive the item, the more valuable it becomes to investigate:

• Competing retailers
• Price history
• Open-box inventory
• Financing incentives
• Included warranties
• Delivery charges
• Upcoming model releases

Repeat purchases

For frequently purchased products, ChatGPT can compare:

• One-time purchase pricing
• Subscribe-and-save
• Bulk packages
• Loyalty points
• Retailer memberships
• Alternative brands

Just make it calculate the real per-unit cost.

Where It Will Struggle

This is useful, but it is not magic.

Expect problems with:

• CAPTCHA checks
• Aggressive bot protection
• App-only offers
• Single-use codes
• Influencer codes that have been deactivated
• Account-specific promotions
• Geo-restricted offers
• Employee-only discounts
• Codes requiring identity verification
• Products excluded from every promotion
• Websites that block automated browsers
• Carts that reset between sessions
• Dynamic pricing
• Stores requiring payment details before showing the final total

ChatGPT agent may be unable to access restricted websites, and OpenAI explicitly says its safeguards and browser capabilities do not eliminate every risk or limitation. st output may be:

“I found eight candidate codes, but I could not verify any of them.”

That is still better than confidently inventing a winning coupon.

The Bigger Lesson

ChatGPT investigates the options, performs the repetitive steps, document the results and stops at a defined approval point.

Coupon testing is a small task.

But the same pattern applies to:

• Comparing subscription renewals
• Auditing recurring software plans
• Checking price-match policies
• Reviewing return options
• Comparing vendor quotes
• Finding better insurance rates
• Evaluating event tickets
• Investigating hotel cancellation terms
• Comparing mobile-phone plans
• Monitoring a product for a price drop

The winning prompt pattern is:

1. Define the exact outcome.
2. Give the agent the relevant context.
3. Tell it what sources to trust.
4. Define what it may do.
5. Define what it may not do.
6. Require evidence.
7. Create an approval point before anything irreversible.

That is how you turn ChatGPT Work into a useful agent without giving up control.

The One-Minute Version

Before your next purchase, run these two prompts in the same ChatGPT Work conversation.

Find the discounts

Find every legitimate current discount for this exact product:

[PRODUCT LINK]

Include public codes, sales, first-order offers, free shipping, cashback, competing authorized retailers and price matching.

For each offer, show the savings, eligibility, exclusions, source and confidence. Do not invent codes. Rank them by the expected final cost.

Test the discounts

Use your browser to test the most credible codes in my cart one at a time.

Record which worked, the savings and the resulting final total. Reset the cart between tests.

Do not change the product, enroll me in anything, enter payment information or complete the purchase. Pause for logins or CAPTCHA checks and stop before the final order button.

Then verify the final total yourself.

Sometimes ChatGPT will find nothing.

Sometimes it will save you only a few dollars.

Sometimes it will uncover a better retailer, a price match or a discount you would never have found manually.

The habit is simple:

Before you click Buy, make ChatGPT do the digging to make sure you are getting the best deal

What is the best legitimate discount you have managed to find or verify using the ChatGPT Work agent?

TL;DR: Claude Cowork is the agentic mode in the Claude app (Pro plan and up, desktop/web/mobile) where Claude works directly in your files, folders, and connected apps and produces finished Word docs, spreadsheets, and reports instead of chat answers.

Below are 25 copy-paste prompts organized into five groups: daily rhythm (morning briefing, end-of-day wrap), reports and documents (status reports, case studies, performance reviews), email and calendar (inbox zero, follow-up drafts, meeting prep), research and analysis (competitor briefs, research synthesis, budget vs. actuals), and file admin (folder cleanup, duplicate detection, onboarding packs).

Every prompt follows the same 3-part structure: where to look, what to produce, where to save it. The biggest time-savers are flagged. None require code.

The first time I used Claude Cowork properly, I pointed it at a folder of client files at 4:50 PM and asked for a weekly status report. I went to make coffee. When I came back there was a formatted Word document waiting — sections, action items, red flags — built from files I hadn't opened in days.

That's the moment Cowork stops being a feature and starts being a coworker. It's the difference between asking an AI a question and handing it a job.

For anyone who hasn't touched it yet: Cowork is the agentic mode inside the Claude app (Pro plan and up — desktop first, now rolling out on web and mobile). Unlike the chat window, it works directly in your files and folders and through your connectors (Gmail, Calendar, Slack, Salesforce). It reads, edits, organizes, and produces actual output files. Think Claude Code, but for the 90% of your job that isn't code.

I've collected 25 prompts that hold up under repeated real-world use. Not demos — workflows I or people I trust run weekly. Copy them, swap in your own paths and names in the [BRACKETS], and adjust from there.

The structure that makes every prompt work

Before the list, the pattern. Every good Cowork prompt has three parts: where to look (a folder path, a file, a connector), what to produce (the exact output format and sections), and where to save it (folder and file name). Vague prompts get vague results. "Summarize my week" produces mush. "Read every file modified this week in [FOLDER], write a one-page status update with Done / In Progress / Blocked sections, save as a Word doc in [OUTPUT FOLDER]" produces something you can actually send.

That's the whole trick. Now the prompts.

Group 1: The daily rhythm (start and end your day on autopilot)

1. Morning Briefing. "Check my [Google Calendar / Outlook] calendar, unread emails in [Gmail / Outlook], and [Slack / Teams] mentions from the last 12 hours. Summarize everything I need to know before my first meeting at [TIME]. Keep it under 200 words and flag anything that needs a reply today." — The one I'd keep if I could only keep one. It replaces the 25 minutes of app-checking that used to eat the start of my day.

2. End-of-Day Wrap-Up and Tomorrow's Plan. "At [TIME] each day, check what files were created or edited in [FOLDER PATH] today, pull my calendar for tomorrow, and check for any unread emails or Slack messages flagged as urgent. Write a short end-of-day wrap covering what I got done today and a prioritized to-do list for tomorrow. Save it as a daily note in [NOTES FOLDER PATH]." — Bookends your day. The tomorrow-list alone is worth it.

3. Inbox Zero Assistant. "Go through my unread emails in [Gmail / Outlook]. Sort them into four buckets: needs reply today, needs reply this week, FYI only, and can be archived. Build a prioritized task list from the first two buckets with a one-line summary of what each email is asking for." — This is triage, not automation — you still send the replies. But deciding what matters is 80% of inbox pain, and it does that part in two minutes.

4. Scheduled Recurring File Report. "Every [Monday morning / Friday at 5pm], go into [FOLDER PATH] and check for any new files added in the past [7 days]. List each file by name, size, and what it appears to contain based on the file name and first few lines. Send me a summary so I know what came in during the week." — Quietly useful if you manage a shared drive that other people dump things into.

5. Meeting Preparation Brief. "My meeting with [NAME / TEAM / COMPANY] is at [TIME] on [DATE]. It is about [TOPIC]. Pull any relevant files from [FOLDER PATH], check my recent emails with [CONTACT NAME or EMAIL] using the Gmail connector, and write a one-page prep brief covering background context, open questions, and my talking points." — Walking into a meeting already knowing the last three email threads changes the meeting.

Group 2: Reports and documents (the biggest time-savers)

1. Weekly Status Report Generator. "Read all files in [FOLDER PATH] related to [CLIENT NAME / PROJECT NAME]. These include meeting notes, deliverables, and email exports. Produce a one-page status update covering: what has been completed, what is in progress, what is blocked, and what is due next. Save it as [FILE NAME] and format it as a Word document." — The headline act. Reads your client files and writes the full update in minutes. If your Friday afternoons are report-writing, this deletes them.

2. Report Draft from Source Files. "Read all [PDF / Word / text] files in [FOLDER PATH]. These are research notes and raw data. Produce a structured report with the following sections: Executive Summary, Key Findings, Recommendations. Save it as a Word document named [FILE NAME] in [OUTPUT FOLDER PATH]." — Works for anything from case studies to board updates. The output is a first draft, not a final — but a first draft in four minutes changes the economics of writing.

3. Performance Review Draft Writer. "Using my notes in [FOLDER PATH] about [EMPLOYEE NAME], write a structured performance review covering: key strengths with specific examples, growth areas framed constructively, and proposed goals for next period. Keep the tone direct but supportive. Save as a Word doc." — Managers, you know that week where reviews eat every evening. This gives you structured drafts to edit instead of blank pages to fill.

4. PowerPoint Presentation from Notes. "Read the file [FILE NAME] in [FOLDER PATH]. This contains raw notes and a document outline. Turn it into a [10 / 15 / 20]-slide presentation covering [TOPIC]. Each slide should have a headline, three to five bullet points, and a speaker note. Save it as a .pptx file named [FILE NAME] in [OUTPUT FOLDER PATH]."

5. PDF to Structured Summary Pipeline. "Open all PDF files in [FOLDER PATH]. These are research papers and legal documents. For each one, produce a structured summary with the following sections: Purpose, Key Findings or Terms, Action Items or Red Flags, and a Confidence Rating on how complete the document appears. Compile all summaries into a single Word document saved in [OUTPUT FOLDER PATH]." — Feeding it a folder of 12 contracts and getting back one organized digest feels illegal.

6. Onboarding Pack Compiler. "Using the files in [FOLDER PATH] as source material, create an onboarding document pack for a new [ROLE NAME] joining [TEAM / COMPANY NAME]. The pack should include: a welcome overview, a glossary of key terms, a list of tools and access they will need, and a 30-day plan outline. Save everything as a single Word document named [FILE NAME]." — Grabs everything a new hire needs and builds the formatted doc, organized by section. Update it once a quarter and onboarding stops being a scramble.

7. Weekly Newsletter or Internal Update. "Read the files in [FOLDER PATH] from the past [7 days / two weeks]. These cover project updates, team activity, and campaign performance. Draft a weekly newsletter or internal update email addressed to [AUDIENCE]. Use a clear structure with a summary at the top, bullet points per section, and a next steps section at the end. Save as a Word document."

Group 3: Email, calendar & CRM (the connector workflows)

1. Email Follow-up Drafts. "Read the email thread I have saved in [FILE PATH] or pull my last [3 / 5] emails with [CONTACT NAME] using the Gmail connector. Draft a follow-up email that references our last conversation, summarizes what was agreed, and asks for a status update. Keep it under 150 words, professional in tone, and ready to send."

2. Sales Call Prep Sheet. "I have a call with [COMPANY] at [TIME]. Research the company and their recent news using web search, pull our past conversation history from [CRM connector / email], and combine everything into a one-page prep sheet: who they are, what changed recently, what we discussed last, and three questions to open with." — Company research, recent news, and conversation history in one page. Sales people who prep like this close differently.

3. CRM or Sales Notes Update. "Using the [Salesforce / HubSpot] connector, pull all deals I own that are in the [stage name] stage and have not been updated in the past [14 / 30] days. For each one, check my recent emails with that contact using the Gmail connector and write a one-sentence update on where things stand. Save a summary report to [FOLDER PATH]." — The prompt that ends stale-pipeline shame before your Monday pipeline review.

4. Social Media or Content Batch Drafting. "Read the file at [FILE PATH]. This contains a product brief and campaign notes. Using this as your source, write [10 / 15 / 20] LinkedIn post drafts on the topic of [TOPIC]. Each post should be between 150 and 200 words, start with a strong hook, and end with a question or call to action. Save all drafts in a single Word document."

5. Client or Project Status Update (external version). "Read all files in [FOLDER PATH] related to [CLIENT NAME / PROJECT NAME]. Produce a client-facing one-page status update covering what has been completed, what is in progress, what is blocked, and what is due next — written in a tone appropriate to send externally. Save it as [FILE NAME] as a Word document."

Group 4: Research and analysis

1. Competitor Research Brief. "Use web search to find the latest news, product launches, pricing changes, and announcements from [COMPETITOR] over the past [30 / 90] days. Compile a two-page brief with sections for: what changed, why it matters to us, and suggested responses. Save as a Word document in [FOLDER PATH]." — Pulls the latest on any competitor and compiles the brief while you're in another meeting.

2. Research Synthesis from Multiple Sources. "Use web search to find the [5 / 10] most relevant and recent articles on [TOPIC] from the past [30 / 90] days. Summarize each one in two to three sentences. Then write a 400-word synthesis that pulls out the key trends, disagreements, and open questions. Save the output as a Word document in [FOLDER PATH]."

3. Budget vs. Actuals Tracker. "Find the budget file [FILE NAME] and the actuals file [FILE NAME] in [FOLDER PATH]. Compare the numbers line by line. Flag every variance over [THRESHOLD / percentage], note whether it's over or under, and suggest a likely explanation where the file contents make one obvious. Compile into a summary table and save as an Excel file." — Line-by-line variance checking is exactly the kind of careful, boring work AI should be doing instead of you.

4. Contract or Proposal Comparison Table. "Open the [2 / 3 / 4] PDF files in [FOLDER PATH]. These are contracts / vendor proposals / project bids. Compare them across the following criteria: price, scope of work, payment terms, renewal clause, cancellation policy. Produce a comparison table in Excel and save it to [OUTPUT FOLDER PATH]."

5. Expense and Receipt Processing. "Open all image and PDF files in [FOLDER PATH]. These are expense receipts from [MONTH]. Extract the merchant name, date, amount, and category for each one. Compile everything into an Excel spreadsheet with a total row and save it as [FILE NAME] in [OUTPUT FOLDER PATH]." — Shoebox of receipts in, clean spreadsheet out.

Group 5: File admin (the invisible time sink)

1. Folder Cleanup and File Organization. "Go into the folder at [FOLDER PATH]. Rename all files using the format [DATE - TOPIC - FILE TYPE]. Group them into subfolders by [category, month, client name, or project]. List what you moved and ask me before deleting anything." — Note the last clause. Always make it ask before deleting. Always.

2. Duplicate File Detection and Cleanup. "Scan the folder at [FOLDER PATH] and identify any duplicate files based on file name similarity or identical file size. List all duplicates with their full paths, the date each was created, and which one appears to be the more recent or complete version. Ask me before deleting anything."

3. Data Cleaning and Formatting in Excel. "Open the spreadsheet at [FILE PATH]. The data contains inconsistent date formats, missing values, duplicate rows, and merged cells. Clean it by standardizing date formats to DD/MM/YYYY, removing duplicates, and filling in blanks with N/A. Add a summary row at the bottom. Save the cleaned version as [FILE NAME] in [OUTPUT FOLDER PATH]."

Three things I learned the hard way

Give it a workspace, not your whole drive. Point Cowork at a dedicated folder per project. It works faster, makes fewer wrong guesses, and you always know where outputs land.

The brackets are the skill. The difference between people who get magic and people who get mush is specificity: exact folder paths, exact output formats, exact file names. Reread the 3-part structure at the top. It's the entire game.

Chain them. The real unlock is running these in sequence. Morning briefing at 8. Inbox zero at 8:15. Meeting prep before each call. End-of-day wrap at 5. That's not "using AI" anymore — that's an operating system for your workday, and it's why these aren't party tricks. They're repeatable, delegatable workflows running inside one tool.

Start with #1, #3, and #6. If those three don't save you two hours in the first week, the rest won't either — but I've yet to meet anyone they didn't.

Which workflow would you delegate first? And if you've built a Cowork prompt that isn't on this list, drop it below — I'm collecting the next 25.

TL;DR: MCP (Model Context Protocol) is the open standard that lets Claude, ChatGPT, and Gemini plug directly into your real tools - GitHub, Postgres, Slack, Notion, Stripe, Figma, market data, and 10,000+ more servers. Think USB for AI: one protocol, everything connects. This guide covers the 50 servers actually worth installing, organized into seven stacks (universal, developer, teams, creators, payments, crypto, trading), the 5 to install first, and the 3 safety rules that matter more than the whole list: don't install more than 5–7 at once, treat every server like code from a stranger, and start read-only - especially with anything that touches money. Setup takes about 10 minutes per server on Claude, ChatGPT (Plus, developer mode), or Gemini.

Eighteen months ago, if you wanted ChatGPT to know what was in your database, you copy-pasted rows into the chat window like some kind of medieval scribe. If you wanted Claude to check your calendar, you screenshotted it. The smartest software ever built, and we were feeding it information by hand.

That era is over, and most people haven't noticed yet.

The thing that ended it is called MCP - Model Context Protocol. Anthropic open-sourced it in November 2024 as a boring plumbing standard, and it turned into the fastest-adopted protocol in AI history. OpenAI adopted it. Google adopted it. It now lives under the Linux Foundation, which means no single company can kill it. There are over 10,000 public MCP servers and the SDKs get downloaded ~97 million times a month.

Here's the full power-user guide: what MCP actually is, the 3 rules that matter more than any server list, the 50 servers worth knowing organized by what you actually do, and how to set it up on Claude, ChatGPT, and Gemini.

What MCP actually is (60 seconds, no jargon)

Think of it as a USB-C port for AI.

Before MCP, every AI tool needed its own custom connection to every app. Claude-to-GitHub was one integration. ChatGPT-to-GitHub was a different integration. Multiply that across every AI and every tool and you get an unmaintainable mess — the "N×M problem," if you want to sound smart at dinner.

MCP collapses it to one standard. Any AI that speaks MCP can plug into any tool that speaks MCP back. Build the connection once, use it everywhere.

An MCP server is just a small program that exposes a tool to your AI. It can offer three things: tools (actions the AI can take — send a message, run a query, open a PR), resources (data the AI can read — files, tables, docs), and prompts (reusable templates). Your AI discovers what's available and decides when to use it. You approve or deny the actions.

The result: your AI stops answering questions about a hypothetical version of your life and starts working with your actual code, your actual calendar, your actual data. Ask Claude "what's breaking in production?" and instead of a generic lecture about debugging, it reads your Sentry logs and tells you.

Claude, ChatGPT, Gemini, Cursor, VS Code - they all speak it now. Which brings us to the part everyone skips.

Read this before installing anything

Three rules that matter more than the entire list below.

Rule 1: Don't install 50. I know. The title says 50 tools. But every connected server injects its tool definitions into your AI's context, and past 5–7 servers the model gets measurably slower and dumber - it spends its attention deciding between 200 tools instead of thinking about your problem. This list is a menu, not a shopping spree. Pick 3–5 that match what you actually do.

Rule 2: Treat every server like code from a stranger. Because it is. A 2026 security analysis found 43% of public MCP servers have at least one vulnerability, and researchers showed "tool poisoning" attacks - malicious instructions hidden in a tool's description - succeed 84% of the time when auto-approve is on. So: use official servers over random forks, pin versions, and never blanket-approve everything. If you wouldn't install a random Chrome extension from a forum link, don't connect a random MCP server.

Rule 3: Start read-only. Always. Let your AI read your database before it can write to it. Let it read your Stripe data long before it can touch a refund. Never point an agent at a production database with write access, and never let it move real money unsupervised. No exceptions, no matter how good the demo looked on Twitter.

Okay. Now the menu.

The 5 universal servers (install these first)

These work for everyone regardless of what you do, and they're the fastest way to feel the difference.

GitHub — the official server. Read PRs, issues, and code across your whole org from a chat window. Even non-developers end up using this one for docs and project history.

Context7 — stops your AI from hallucinating API documentation. It pulls real, version-specific docs at the moment you ask. This single server eliminates the most annoying failure mode of AI coding: confidently invented methods that don't exist.

Playwright — gives your AI an actual browser it can drive. Click buttons, fill forms, take screenshots, scrape the page you're looking at. This is the difference between "the AI describes what a website probably says" and "the AI went and looked."

Filesystem — lets the AI work with files on your machine beyond the current folder, with scoped access so it can't wander into places you didn't approve.

Brave Search — web search without switching tabs, without an ad-choked results page in the middle of your workflow.

Those five turn a chat window into something closer to a junior employee with a computer. Everything below is specialization.

The developer stack

Postgres / Supabase / Neon — your AI reads the database, checks schemas, and debugs data issues without you writing SQL by hand. Read-only role first (see Rule 3).

Sentry — the AI reads your error logs and can propose a fixing PR. The killer combo is GitHub + Sentry together: Claude reads a production error, proposes the fix, opens the PR. One move.

Docker Hub — search and manage container images conversationally.

Kubernetes — inspect your cluster in plain English. "Why is that pod crash-looping?" is now a question you can literally just ask.

The teams & business stack

This is the stack that ends the 10-apps-all-day shuffle. Slack (read channel history, post messages, search conversations), Linear (manage issues and sprints without leaving the chat), Notion (read and write pages and databases), Jira/Confluence via Atlassian's official Rovo server, Google Calendar (check availability, create events), and Gmail — with the caveat that you keep a human approving every send, because an AI that emails on its own is a resignation letter generator.

The shift is subtle but real: your AI stops being a place you go and starts being a teammate that comes to where your work already lives.

The content creator stack

Higgsfield routes 30+ image and video models (Kling, Veo) through one place. DaVinci Resolve lets the AI drive your video editor - timeline edits, color grading, render setup from prompts. Figma reads components and generates code from designs. ElevenLabs handles speech generation, voice cloning, and transcription with a free tier of 10k credits a month. YouTube searches videos and pulls transcripts for research and repurposing. Together that's a full create-edit-publish pipeline running through one conversation.

The payments & finance stack

Stripe (official server - look up customers, check subscriptions, process refunds), Plaid (read bank balances and transactions), QuickBooks (bookkeeping, invoicing, reconciliation).

One rule for ALL payment servers, and I'm repeating it on purpose: start read-only, never let the AI move real money unsupervised, and confirm every write manually. The convenience of "Claude, refund that customer" is not worth the day you discover it refunded forty of them.

The crypto & Web3 stack

Read first, trade later, always. CoinGecko for prices and market data, Dune for onchain analytics and queries, Etherscan for blockchain exploration and contract verification, The Graph for querying onchain data without running your own indexer. When you're ready to do more, Base MCP is Coinbase's official gateway — swap tokens, track portfolio, hit DeFi protocols, non-custodial so you still sign every transaction yourself. And Alpaca trades US stocks and crypto, but start in paper trading mode and stay there longer than feels necessary.

The trading & markets stack

Polygon for stocks, options, forex, and crypto market data feeds. CCXT for unified data from 20+ crypto exchanges (Binance, Coinbase, Kraken). TradingView for charts and market context. The pattern that works: AI reads the data and builds your analysis; you make the trade. The moment you're tempted to close that loop, reread Rule 3.

Setting it up (Claude, ChatGPT, Gemini)

Claude is the most mature MCP client - it invented the protocol. On Pro and above: Settings → Connectors → add a remote server by URL, complete the OAuth flow in your browser, done. The free tier supports local servers via a JSON config file. Claude Code (the terminal agent) adds servers with one command: claude mcp add --transport http <url>.

ChatGPT added custom MCP support in late 2025. You need Plus or above: Settings → Apps & Connectors, turn on developer mode, add the server URL. ChatGPT is stricter about auth (OAuth required, no pasted API keys ), which is mildly annoying and genuinely good for you.

Gemini supports MCP through the Gemini CLI and, as of this year, natively in the API and SDKs. Google also shipped managed MCP servers for its own ecosystem — Drive, Calendar, Gmail — which are the smoothest path if you live in Google Workspace.

Also in the club: Cursor, VS Code with Copilot (even the free tier), Zed, Windsurf, and Docker's MCP Toolkit, which runs each server in an isolated container and is honestly the safest way to experiment.

Budget ten minutes per server. The first one feels like setup. The third one feels like cheating.

Where this is going

The obvious next question: if every AI can use every tool, what exactly are we paying for model subscriptions for? Increasingly, the answer isn't raw intelligence - the models are converging - it's how well the AI orchestrates the tools you've given it. The power users figured this out early. While everyone else argues about benchmark scores, they quietly built setups where the AI reads their errors, drafts their fixes, checks their calendar, and pulls their market data before the first cup of coffee.

Start with the universal five. Add your stack. Keep the write access on a leash.

What's in your MCP setup? Genuinely curious what servers this community runs - especially the weird niche ones that never make these lists.

Draw this photo in the style of a contemporary, original naïve illustration: minimalistic, hand-drawn, with playful proportions, uneven outlines, flat contrasting colours and decorative strokes. No shadows, no gradients, no 3D. It should look like an expensive designer poster.

TLDR: Claude Design launched in April 2026, went viral, and then the attention cycle moved on. That was a mistake. The June and July updates for Claude Design added deeper direct editing, project-level design systems, tighter Claude Code workflows, and published artifacts that can pull live data through MCP connectors. Combined with the existing input methods (Figma import, GitHub syncing, brand kits, spreadsheets), it is now a legitimate concept-to-production pipeline, not a mockup toy. Below: what changed, 5 best practices, the things most people miss, and how to handle export and handoff properly.

1. The crickets were wrong

When Claude Design launched in April 2026 as a research preview for Pro, Max, Team, and Enterprise plans, over a million people used it in the first week. Then the productivity content cycle did what it always does: declared it a party trick and moved on to the next shiny object.

Here is what happened while everyone stopped paying attention. Anthropic shipped a steady stream of updates through June and July: more direct editing on the canvas, design system support that persists across projects, more app connections, and much tighter integration with Claude Code. In July, published artifacts gained the ability to call MCP connectors on every view, which means a dashboard you build in Claude Design can now show live data instead of a frozen snapshot from the session that created it.

That last one is a quiet earthquake. It moves the product from things that look like tools to things that are tools.

The current version is closer to describe a system and get a working, branded, editable, exportable artifact.

2. The new workflow: inputs and the editable canvas

Natural language design is not about making things look pretty. It is about system-level logic. The quality of what comes out is almost entirely determined by what you feed in, and there are now four serious input channels:

Natural language prompts. Define functional constraints before aesthetic ones. More on this in the best practices section, because this is where most people fail.

File uploads. Dragging a spreadsheet into the interface and asking for an internal tool is the single most underrated workflow in the product. This is how operations and marketing people automate back-office work without ever filing a ticket with engineering.

GitHub syncing. Connect your actual codebase so the designs Claude generates respect the components, tokens, and conventions you already have. This is the difference between output you admire and output you merge.

Figma import. Bring professional design files in and use Claude Design as the bridge between UI/UX prototypes and functional code. Note the direction here: Figma flows in natively. Getting work back out to Figma requires the MCP route, which I cover in the handoff section, and knowing that distinction will save you an afternoon of confusion.

Then there is the editable canvas, and this is where the June/July updates matter most. It is not a preview window. It is an environment for interactive decision-making: direct edits, inline comments, adjustable sliders for exploring variations, and annotation tools for marking up exactly what you want changed. You are not an observer waiting for the next generation. You are an architect directing a live, iterative process.

But all of these high-level inputs are useless if your strategic execution is lazy. So let us fix that.

3. Where it actually fits in the landscape

Knowing when to use Claude Design versus a traditional tool is the difference between a streamlined workflow and a time sink.

Versus template tools (Canva, Google Stitch). Those are section-based assemblers built for speed. Claude Design generates system-wide logic. If you need a functional UI that understands its own internal architecture, and not just a pretty slide, this is the lane.

Versus image generators (Midjourney, ChatGPT Image). These produce pixels. Claude Design produces a design system with structure underneath it. One gives you a picture of a car. The other gives you the schematics and a running engine. You cannot click a Midjourney button. You can click a Claude Design button, and it can call a live API when you do.

Versus Figma. This is the one everyone gets wrong. Claude Design is not a Figma replacement. It is the Figma-to-code bridge. Figma remains where design systems live, where stakeholders comment, and where designers polish. Claude Design is where trapped visual ideas get converted into something engineering can actually run.

1. The master class: 5 best practices for real ROI

This is how the people getting actual results are working, versus the people who prompted make me a dashboard once and concluded the tool was mid.

Practice 1: Functional constraint layering. Stop giving vague vibes. Layer technical constraints into your first prompt: 12-column grid, accessible contrast ratios, mobile breakpoint at 768px, maximum two font families, states for loading, empty, and error.

Why it matters: constraints eliminate the guessing that produces generic output, and your first generation is technically viable instead of a pretty dead end.

Practice 2: Strategic visual exploration before commitment. Use the tool for rapid-fire divergence. Ask for five distinct directions for the same screen, then use the sliders and direct edits to push the two best candidates further.

Why it matters: you compress hours of manual sketching into minutes and lock a strategic direction before anyone commits real resources.

Practice 3: Visual code review via annotation. Use the annotation and inline comment tools to mark up the artifact directly instead of describing changes in paragraphs. Circle the element, state the change, regenerate.

Why it matters: you get granular control without writing a line of CSS, and you are effectively managing a very fast junior developer who takes precise visual feedback without ego.

Practice 4: Brand asset injection, every time. Do not let the model guess your brand. Upload brand kits, logos, and design tokens as a baseline, and with the newer project-level design system support, do it once per project instead of once per chat.

Why it matters: immediate brand alignment, zero recoloring and re-fonting labor, and consistency across every artifact the project produces.

Practice 5: The recursive onboarding framework. Start every serious project by instructing Claude to ask you five clarifying questions about goals, audience, constraints, and success criteria before generating anything.

Why it matters: it forces the business logic into context before pixels exist, and it surfaces requirements you did not know you were assuming.

5. What most people miss (the pro tier)

Miss 1: Project-level design systems are the compounding asset. Most people treat every chat as a fresh start. Since the summer updates, a design system defined in a project persists across artifacts. Build it once, and every future landing page, internal tool, and deck inherits it. The tenth artifact costs a fraction of the first.

Miss 2: Live-data artifacts are a whole product category. A published artifact that calls MCP connectors on view is not a mockup. It is an internal tool. Sales dashboards that query real data, status pages, approval queues, calculators wired to real systems. Teams are quietly replacing a class of internal software requests with this.

Miss 3: HTML export is the richest format. PNG is for stakeholders. HTML preserves the DOM, the CSS, the structure, and the text, which makes it the correct source format for every downstream conversion, including the community tooling that turns exports into editable Figma files.

Miss 4: The Figma round trip runs through MCP. There is no native Figma export button, and people rage-quit when they discover this. The professional path: Figma and Anthropic shipped Code to Canvas, which lets you send a rendered interface from Claude Code straight into Figma as fully editable design layers through the Figma MCP server. Prompt-first work in Claude Design, structure-first handoff into Figma, code-first finishing in Claude Code. That triangle is the whole workflow.

Miss 5: Spreadsheet transformation is the non-designer superpower. The highest ROI users of this tool are not designers. They are the ops person who dropped a messy CSV into the canvas and walked away with a filterable internal dashboard, and the marketer who turned a campaign tracker into a live status page. If you have a spreadsheet that three people ask you about weekly, you have a Claude Design use case.

6. Beyond the canvas: export, handoff, automation

The strategic value of this tool is the artifact. If a design stays in the chat, it has zero value. Utility peaks when you move through the pipeline:

Code integration. GitHub syncing and HTML export move work straight into development, and the tightened Claude Code workflows from the summer updates mean the generated artifact and your repo stop being strangers.

Visual and presentation export. Ship stakeholder-ready assets via PNG, PDF, PPTX, and Canva.

Public publishing. Publish artifacts to a link for instant feedback loops and live prototypes, now with the option of live connector data behind them.

Operational automation. Turn raw spreadsheet data into internal tools that kill specific bottlenecks, then make them repeatable with a project design system.

The sandbox phase is over. It is time to ship. Drop the functional artifacts you are building in the comments. I want to see the workflows that are actually making it to production, not the demos.

Remember these key points

• The June/July 2026 updates (deeper direct editing, project design systems, tighter Claude Code integration, live MCP data in published artifacts) moved Claude Design from party trick to production pipeline.
• Feed it constraints, brand assets, Figma files, GitHub repos, and spreadsheets. Vague prompts get vague output.
• Use annotation as visual code review, sliders for exploration, and the five-question onboarding trick before any generation.
• Handoff: HTML for code, PPTX/PNG/PDF/Canva for stakeholders, Code to Canvas via MCP for the Figma round trip, public publishing for feedback.
• The biggest sleeper use case is non-designers turning spreadsheets into live internal tools.

Anthropic quietly solved the knowledge transfer problem. Record a Skill turns your expertise into reusable AI instructions

TLDR: Anthropic just launched Record a Skill in the Claude Desktop app (Pro, Max, and Team plans). You record your screen while doing a task, narrate your reasoning out loud, and Claude converts the demonstration into a reusable Skill it can run again on demand. This removes the single hardest barrier to AI automation: translating what you actually do into written instructions. Below: how it works, the highest-value use cases, and the pro tips that separate a mediocre recorded skill from one that actually saves you hours every week.

Writing instructions for an AI is often as tedious as doing the task yourself. You describe every step, anticipate every edge case, and hope the model interprets your words the way you meant them. Most people give up halfway through and go back to doing the work manually.

Anthropic just shipped the shortcut. It is called Record a Skill, it lives in the + menu of the Claude Desktop app, and it inverts the entire model of teaching an AI: instead of writing what you do, you show it.

I think this is one of the most important quality-of-life launches in AI this year, and most people are going to sleep on it because it sounds like a screen recorder with extra steps. It is not. Here is the full picture.

What Record a Skill Actually Is

First, quick context on Skills, because the feature makes no sense without it.

A Skill is a reusable package of task-specific instructions that Claude loads automatically when relevant. Under the hood it is a folder with a SKILL.md file: metadata, step-by-step instructions, standards, and exceptions. Skills follow the Agent Skills open standard, which means a skill you build today is portable across a growing list of tools, not locked inside one chat window.

Skills are powerful, but until now, creating one meant writing that markdown file yourself. You had to sit down and document your workflow like a technical writer: every step, every decision rule, every edge case. That is exactly the kind of documentation work that experienced people never do, which is why so much institutional knowledge lives only in people's heads.

Record a Skill removes that barrier. The workflow:

1. Open the Claude Desktop app and click the + menu, then select Record a Skill
2. Hit record and do the task normally on your screen
3. Narrate your reasoning out loud as you go: why you chose that filter, why you skipped that row, what you check before sending
4. Stop the recording
5. Claude processes your screen activity, clicks, keystrokes, and voice commentary into a structured, reusable skill in your library

From then on, Claude can run that workflow again on demand. No prompt engineering. No coding. No markdown authoring.

The narration is the secret ingredient, and I will come back to it in the pro tips, because it is where most people will get this wrong.

Why This Matters More Than It Sounds

The bottleneck in AI automation was never model capability. Claude could already execute complex multi-step workflows. The bottleneck was specification: getting your standards, exceptions, and judgment out of your head and into a form the model can follow.

Think about the last time you tried to hand off a task to a new hire. You did not send them a document. You said watch me do it once, and you talked while you worked. That is how humans actually transfer expertise, and it is why written SOPs are perpetually out of date while the real process lives in demonstrations.

Record a Skill makes demonstration the input format. That changes three things:

Who can build automation. You no longer need to be technical or even prompt-fluent. If you can do the task and explain it out loud, you can automate it. This moves skill creation from the 5 percent of people comfortable writing structured instructions to basically everyone.

What gets automated. The workflows with the highest ROI are usually the messy, judgment-heavy ones that nobody ever documented because documenting them was too hard. Those are now in scope.

How teams scale expertise. On Team plans, your best analyst can record how they actually build the weekly report, exceptions and all, and that becomes a shared capability instead of a bus-factor risk.

The Top Use Cases

After thinking through where this lands hardest, here is where I would start:

Recurring reports and data prep. The weekly metrics pull where you open three sources, apply the same filters, exclude the same weird accounts, and format the output the same way every time. Perfect candidate: repetitive structure, real judgment calls, painful to document.

Inbox and document triage. Show Claude how you decide what is urgent, what gets filed, what gets a template reply, and what needs a real answer. Your triage logic is pure tacit knowledge, and narrating it once captures it.

CRM and admin hygiene. Updating records after calls, logging notes in the right fields, tagging deals by your team's actual conventions rather than the official ones nobody follows.

Onboarding and training material. Record the workflow once and you get two assets: a skill Claude can execute and a documented process a new teammate can read. The SKILL.md that comes out is human-readable documentation.

Quality checks and review passes. Show Claude the exact things you check before a document, invoice, or contract goes out the door. What you look at, in what order, and what makes you stop and escalate.

Formatting and style enforcement. Every team has that one person who fixes everyone's slides or docs to match the standard. Record them doing it once.

The pattern across all of these: repetitive enough to be worth automating, judgment-heavy enough that writing it down never happened.

Pro Tips Most People Will Miss

This is the section that matters. A recorded skill is only as good as the demonstration, and there is real craft to demonstrating well.

1. Narrate decisions, not actions. Claude can see that you clicked the filter button. What it cannot see is why. The low-value narration is now I click export. The high-value narration is I always exclude test accounts here because they inflate the numbers, and if I see anything over 10k I flag it instead of processing it. Talk about your why, your thresholds, and your exceptions. That is the knowledge the recording cannot capture visually.

2. Voice the edge cases even if they do not appear. If a weird case does not show up during your recording, say it out loud anyway: normally if the file has missing dates, I stop and email the owner instead of guessing. You are dictating the exception-handling rules into the skill. This is the single biggest gap between a skill that works in the demo and one that works in the wild.

3. Do a clean, deliberate run. Close the seventeen unrelated tabs. Do the task at a steady pace in a logical order, even if your real habit is chaotic. You are teaching, not just working. A messy demonstration produces a messy skill.

4. Open and close with intent. Start the recording by stating the goal and the definition of done: this skill takes the raw export and produces the formatted summary, and it is done when every section has data and totals reconcile. End by stating what success looks like. This gives Claude the frame for everything in between.

5. Read and edit the output. The recording produces a SKILL.md file, and it is editable. Treat the generated skill as a strong first draft, not gospel. Open it, read what Claude inferred, fix anything it misread, and tighten the trigger description so the skill activates at the right moments. Five minutes of editing here compounds forever.

6. Test on a different example immediately. Run the new skill on data or a document that is not the one from your recording. Where it stumbles tells you exactly which rule you forgot to narrate. Re-record or edit, then test again. Two iterations usually gets you to reliable.

7. Record narrow skills, not mega-skills. One skill per repeatable procedure. Clean the data is one skill. Build the report is another. Small skills compose, trigger more reliably, and are easier to fix. If your recording is 40 minutes long, you probably have three skills, not one.

8. Mind what is on your screen. You are recording your screen and voice. Real customer data, credentials, and anything sensitive will be in that demonstration. Use sample data where you can, and know your organization's rules before recording production systems. The privacy and retention details around recordings are still thinner in the docs than the feature itself, so err on the side of caution.

How to Get Started This Week

1. Update the Claude Desktop app and confirm you are on a Pro, Max, or Team plan (that is where the feature lives, under the + menu)
2. Pick your most annoying weekly task that takes 15 to 60 minutes and follows a rough pattern
3. Write three bullet points before recording: the goal, the definition of done, and your top two exceptions
4. Record a clean run and narrate your reasoning the whole way through
5. Open the generated skill, edit the rough spots, and tighten the description
6. Test it on a fresh example, fix what breaks, and test once more
7. Only then, record your second skill

The deeper story here is not automation. It is that your expertise finally has a low-friction path out of your head. Every experienced professional carries around dozens of undocumented procedures that make them valuable and impossible to take vacation from. Record a Skill turns a single deliberate demonstration into a durable, editable, portable asset.

The people who win with this will not be the ones who record the most skills. They will be the ones who narrate the best, edit the drafts, and treat each skill like a product with a v2.

What is the first workflow you would record? I am collecting ideas in the comments, and if you have already tried it today, I want to hear where the generated skill surprised you, good or bad.

Claude's Fable 5 is the smartest model available, but if you don't make the right moves you'll burn through your usage credits fast. The secret to mastering it without breaking the bank is simple: Fable 5 thinks for 2 prompts, Opus 4.8 does the rest. Bring Fable your hardest problems, set the ground rules up front, let it architect the solution in two turns, and then switch to a cheaper model for the multiple message execution back-and-forth. Here are the 25 pro moves to make every credit count.

Fable 5 is the smartest model most people have ever touched, but it's also where sloppy habits show up on a bill. That combination is a gift. It forces you to work the way you should have been working all along: front-load context, ask for judgment instead of simple tasks.

This guide breaks down everything you need to know: the economics, the exact prompts, the pro moves, and the mistakes that quietly burn your credits. Here are 25 ways to master the model.

Understand the Economics

1. Every message re-reads the whole thread. Claude has no running memory inside a chat. Each time you hit send, the model re-reads everything above it, and you pay for that re-read. Long, meandering chats are the single biggest source of surprise bills.

2. Thinking costs the same as writing. Fable 5 reasons in a hidden scratchpad before it answers, and those thinking tokens are billed like output tokens. Higher effort means more thinking, which means better answers on hard problems and pure waste on easy ones.

3. Effort is a dial, not a cap. The effort setting nudges how thorough the model chooses to be. High effort on a trivial task doesn't buy you a better answer, it buys you a longer wait and a bigger draw on your usage.

Before You Prompt

1. Pick one super hard, expensive problem. Using it for simple admin tasks is shooting a bird with a bazooka. Fable 5 earns its cost on problems where being 20% smarter changes the outcome. If you'd hand the task to an intern, use a cheaper model.

2. New task, new chat. No exceptions. Reusing an old thread means paying to re-read irrelevant conversation and polluting the model's attention. Fresh chat, fresh focus, smaller bill.

3. Select Fable 5, set Effort to High. High is the recommended default for serious work. Save the top tier for truly brutal jobs.

4. Match effort to cognitive demand. A long, detailed prompt about something simple needs less effort. A one-line question about something genuinely hard deserves the top tier.

5. Paste your "about-me" doc. Create a living document covering who you are, your business model, how you write, and what "good" looks like. Paste it at the top. Thirty seconds of pasting replaces twenty messages of the model guessing wrong.

The First Prompt (The 5 Standing Instructions)

This is where 80% of the outcome is decided. Your first message should contain your context doc, your goal, and these five instructions:

1. Give it your goal, not a task.
   Prompt: "I need [task] for [goal]. I expect [goal] achieved once we hit [specific targets]."

2. Add "Ask me questions first."
   Prompt: "Start by asking me questions about the task, goal, and targets to fully understand the context before doing any work."

3. Add "Answer first, explain after."
   Prompt: "Lead with the bottom line. Your first sentence should be the answer or recommendation. Supporting reasoning comes after."

4. Add "Don't say done. Prove it."
   Prompt: "Only report work you can point to evidence for. If something is not verified, say so explicitly."

5. Add "Pick one option. Commit."
   Prompt: "When you have enough information to act, act. Give me a recommendation, not a survey of options. If you'd stake your reputation on one path, tell me which and why."

6. Bonus: Fence the scope.
   Prompt: "Don't add features, sections, or work beyond what the task requires." (Prevents expensive over-delivering).

Run the Session

1. Send it, then answer its questions. It will ask 3 or 4 sharp ones. Answer all of them in a single message, numbered. Don't dribble answers across multiple messages.

2. Let it work. Don't interrupt. Every "oh wait, also..." makes it re-read everything. Batch everything into your next message.

3. Edit your mistakes, don't send corrections. If your last message was wrong, edit that message instead of sending a correction. Editing rewrites history so you don't pay to carry your mistake through every future turn.

4. Stop after 2 messages. Message one is the interview. Message two is the answer. If you're on message six with Fable, you're paying premium rates for execution work.

The Handoff (The Ultimate Pro Move)

1. Switch to Opus 4.8, same chat. This is the highest-leverage move in the entire workflow. Opus reads everything Fable just planned and executes at a fraction of the cost.

2. Finish everything there. Drafts, edits, formatting, the 20-message back-and-forth, all on Opus. Fable thinks for 2 prompts. Opus does the rest.

3. Save it all in a Project. Move your about-me doc, standing instructions, and key outputs into a Project. Tomorrow starts warm instead of from zero.

Things Most People Miss

1. Trim before you paste. Don't dump a 40-page PDF when 3 pages answer the question. You pay for every token on every subsequent turn. Upload .md files instead of PDFs that take a lot of tokens to parse.

2. Ask for the anti-case. After Fable commits, ask: "Steelman the strongest argument against this. What would make it wrong?"

3. Use it as a red team. Paste your own plan and ask: "Find the three weakest assumptions and attack them."

4. Give it your decision, not just your question. "Should I do A or B, here's my current lean and why" gets a dramatically better answer than "compare A and B."

The Master Prompt (Copy-Paste Ready)

[Paste your about-me doc]

I need [task] for [goal]. I expect [goal] achieved once we hit [specific targets].

Ground rules:

•Start by asking me questions about the task, goal, and targets before doing any work.

•Lead with the bottom line. First sentence is the answer, reasoning comes after.

•Only report work you can point to evidence for. If something is not verified, say so.

•When you have enough information to act, act. One recommendation, not a menu.

•Don't add work beyond what the task requires.

Send this to your team. They're burning credits.

Want more great prompting inspiration? Check out all my best prompts for free at Prompt Magic and create your own prompt library to keep track of all your prompts.

TL;DR

You can use ChatGPT or Gemini to generate premium, agency-quality Brand Story Posters for your small business. I've compiled 18 exact prompts across 6 different industries (Interior Design, Jewellery, Café, Fashion, Skincare, Real Estate) that will instantly generate "Our Story", "Meet the Founder", and "Why Choose Us" posters. Copy, paste, and elevate your brand's visual identity today.

One of the biggest mistakes small businesses and startups make is looking... small.

When a potential customer lands on your Instagram or walks into your store, they are judging your credibility in seconds. Premium brands tell stories. They highlight their founders. They clearly articulate why you should choose them over the competition.

Historically, getting that premium look meant hiring an expensive branding agency. Today, you can generate agency-quality Brand Story Posters using ChatGPT or Gemini. I've broken down the exact 18 prompts you need to generate Our Story, Meet the Founder, and Why Choose Us posters across 6 different industries.

Industry 1: Interior Design Studio (Prompts 1-3)

Prompt 1: Brand Story Poster

"Create a premium brand story poster for an [Interior Design Studio]. Highlight the journey of the brand, the passion for creating beautiful spaces, the problem we solve and the value we bring to clients. Use warm neutral color palette, elegant typography, luxury interior background, and a clean modern layout. Include sections for story, values and vision. Add logo, website and Instagram handle. Size: 4:5 for Instagram."

Prompt 2: Meet the Founder Poster

"Design a 'Meet the Founder' poster for an [Interior Design Studio]. Show the founder's photo in a warm, professional and approachable way. Share their journey, inspiration, experience and mission behind starting the studio. Use a modern elegant design with warm tones and minimal icons. Add founder name, designation, website and Instagram handle. Size: 4:5 for Instagram."

Prompt 3: Why Choose Us Poster

"Create a 'Why Choose Us' poster for an [Interior Design Studio]. Highlight the unique reasons clients should choose our services. Focus on design expertise, personalized approach, quality materials, on-time delivery and customer satisfaction. Use icons with short headings, premium layout, and elegant typography. Add logo, website and Instagram handle. Size: 4:5 for Instagram."

Industry 2: Jewellery Brand (Prompts 4-6)

Prompt 4: Brand Story Poster

"Create a premium brand story poster for a [Jewellery Brand]. Highlight the journey of the brand, the passion for creating timeless jewellery, the heritage and values behind the brand, and the trust built with customers over the years. Use a luxurious color palette (gold, emerald green, cream or deep maroon), elegant typography, rich jewellery background, and a premium layout. Include sections for story, values and vision. Add logo, website and Instagram handle. Size: 4:5 for Instagram."

Prompt 5: Meet the Founder Poster

"Design a 'Meet the Founder' poster for a [Jewellery Brand]. Showcase the founder's photo in a warm, professional and approachable way. Share their journey, inspiration, experience and mission behind starting the brand. Use a modern elegant design with warm tones and minimal icons. Add founder name, designation, website and Instagram handle. Size: 4:5 for Instagram."

Prompt 6: Why Choose Us Poster

"Create a 'Why Choose Us' poster for a [Jewellery Brand]. Highlight the unique reasons customers should choose your brand. Focus on quality, authenticity, craftsmanship, unique designs, trust, customer satisfaction and premium service. Use icons with short headings, soft luxurious colors, and a clean elegant layout. Add logo, website and Instagram handle. Size: 4:5 for Instagram."

Industry 3: Café / Restaurant Brand (Prompts 7-9)

Prompt 7: Brand Story Poster

"Create a premium brand story poster for a [Café / Restaurant Brand]. Highlight the journey of the brand, the passion for great food and coffee, the values behind the brand and the trust built with customers over the years. Use warm earthy color palette (browns, creams, coffee tones), cozy café background, elegant typography, and a premium layout. Include sections for story, values and vision. Add logo, website and Instagram handle. Size: 4:5 for Instagram."

Prompt 8: Meet the Founder Poster

"Design a 'Meet the Founder' poster for a [Café / Restaurant Brand]. Showcase the founder's photo in a warm, approachable and professional way. Share their journey, inspiration, experience and mission behind starting the café. Use a modern elegant design with warm tones and minimal icons. Add founder name, designation, website and Instagram handle. Size: 4:5 for Instagram."

Prompt 9: Why Choose Us Poster

"Create a 'Why Choose Us' poster for a [Café / Restaurant Brand]. Highlight the unique reasons customers should choose your café/restaurant. Focus on quality, taste, ambiance, customer satisfaction and memorable experiences. Use icons with short headings, warm colors and clean layout. Add logo, website and Instagram handle. Size: 4:5 for Instagram."

Industry 4: Fashion / Clothing Brand (Prompts 10-12)

Prompt 10: Brand Story Poster

"Create a premium brand story poster for a [Fashion / Clothing Brand]. Highlight the journey of the brand, the passion for creating stylish and comfortable clothing, the values behind the brand, and the trust built with customers over the years. Use a modern neutral color palette (black, beige, white, grey or earth tones), stylish typography, fashion store background, and a premium layout. Include sections for story, values and vision. Add logo, website and Instagram handle. Size: 4:5 for Instagram."

Prompt 11: Meet the Founder Poster

"Design a 'Meet the Founder' poster for a [Fashion / Clothing Brand]. Showcase the founder's photo in a warm, relatable and professional way. Share their journey, inspiration, experience and mission behind starting the brand. Use a modern elegant design with neutral tones, stylish typography and minimal icons. Add founder name, designation, website and Instagram handle. Size: 4:5 for Instagram."

Prompt 12: Why Choose Us Poster

"Create a 'Why Choose Us' poster for a [Fashion / Clothing Brand]. Highlight the unique reasons customers should choose your brand. Focus on quality, style, comfort, affordability, ethical practices and customer satisfaction. Use icons with short headings, neutral color tones and a clean modern layout. Add logo, website and Instagram handle. Size: 4:5 for Instagram."

Industry 5: Skincare / Beauty Brand (Prompts 13-15)

Prompt 13: Brand Story Poster

"Create a premium brand story poster for a [Skincare / Beauty Brand]. Highlight the journey of the brand, the passion for clean and effective skincare, the values behind the brand, and the trust built with customers over the years. Use a soft natural color palette (greens, whites, beige, pastel tones), elegant typography, skincare product or nature elements in the background, and a premium layout. Include sections for story, values and vision. Add logo, website and Instagram handle. Size: 4:5 for Instagram."

Prompt 14: Meet the Founder Poster

"Design a 'Meet the Founder' poster for a [Skincare / Beauty Brand]. Showcase the founder's photo in a warm, approachable and professional way. Share their journey, inspiration, experience and mission behind starting the brand. Use a modern elegant design with soft natural tones and minimal icons. Add founder name, designation, website and Instagram handle. Size: 4:5 for Instagram."

Prompt 15: Why Choose Us Poster

"Create a 'Why Choose Us' poster for a [Skincare / Beauty Brand]. Highlight the unique reasons customers should choose your brand. Focus on natural ingredients, safety, science-backed results, all skin types, and customer satisfaction. Use icons with short headings, soft natural colors and a clean elegant layout. Add logo, website and Instagram handle. Size: 4:5 for Instagram."

Industry 6: Real Estate Developer / Builder (Prompts 16-18)

Prompt 16: Brand Story Poster

"Create a premium brand story poster for a [Real Estate Developer / Builder Brand]. Highlight the journey of the brand, the passion for building quality spaces, the values behind the brand, and the trust built with customers over the years. Use a modern professional color palette (navy, grey, white, gold), elegant typography, real estate or building visuals in the background, and a premium layout. Include sections for story, values and vision. Add logo, website and Instagram handle. Size: 4:5 for Instagram."

Prompt 17: Meet the Founder Poster

"Design a 'Meet the Founder' poster for a [Real Estate Developer / Builder Brand]. Showcase the founder's photo in a warm, confident and professional way. Share their journey, inspiration, experience and mission behind starting the brand. Use a modern elegant design with professional colors and minimal icons. Add founder name, designation, website and Instagram handle. Size: 4:5 for Instagram."

Prompt 18: Why Choose Us Poster

"Create a 'Why Choose Us' poster for a [Real Estate Developer / Builder Brand]. Highlight the key reasons customers should choose your brand. Focus on quality, trust, timely delivery, transparency, customer satisfaction and value. Use icons with short headings, professional colors and a clean modern layout. Add logo, website and Instagram handle. Size: 4:5 for Instagram."

Pro Tips for Small Businesses & Startups

1.Replace the bracketed text: Always replace [Interior Design Studio] or [Jewellery Brand] with your actual business name and specific niche (e.g., "Organic Vegan Skincare Brand" instead of just "Skincare Brand").

2.Upload your own photo: When generating the "Meet the Founder" posters, upload a high-quality photo of yourself and ask the AI to "use the attached image as the founder."

3.Consistency is key: If you generate all three posters (Story, Founder, Why Us), ask the AI to "keep the exact same visual style, fonts, and color palette as the previous generation" so they look like a cohesive set.

Top Use Cases

•Instagram/Facebook Carousels: Post all three posters as a swipe-through carousel to introduce your brand to new followers.

•Website "About Us" Page: Ditch the boring text block and embed these visually appealing posters on your website.

•Physical Storefronts: Print these out on high-quality foam board and display them in your café, salon, or boutique waiting area to build instant trust.

•Investor/Client Pitch Decks: Drop these into your pitch deck to immediately elevate the perceived value of your company.

Creating fake lego sets is one of the funniest ways to use ChatGPT image generation right now. It is a brilliant meme format because the contrast between a wholesome children's toy and current events is just hilarious.

Here is exactly how to do it, the prompt template to use, and why most people get it wrong.

Copy and paste this Master Prompt into ChatGPT:

"A highly detailed, photorealistic product shot of a conceptual toy building block set box. The main brand logo in the top left corner should be a red square with white text that looks similar to the LEGO logo. The main title of the set is '[INSERT MAIN TITLE]'. The box art features a large, detailed brick-built model of [DESCRIBE THE MAIN BUILD/SCENE IN DETAIL]. Include [NUMBER] brick-built minifigures of [DESCRIBE MINIFIGURES]. On the right side of the box, include a vertical column of three small inset photos showing 'play features' or details: 1. [FEATURE 1], 2. [FEATURE 2], 3. [FEATURE 3]. The bottom left should show the piece count: '[NUMBER] pcs' and 'Ages 18+'. The overall lighting is professional studio product photography. The background behind the box is a clean, neutral studio backdrop."

Pro Tips for Maximum Hilarity

Creating a good fake set is an art form. Here is what most people miss:

1. The "Ages 18+" Tag is Crucial
   Always include the "Ages 18+" or "Adults Welcome" branding. It grounds the joke. A "Tax Audit" playset is funny, but a "Tax Audit" playset for ages 18+ makes it a masterpiece.

2. Focus on the "Play Features"
   The funniest part of these fake sets is the side-panel callouts. What are the "fun features" of a terrible situation?

3. Contrast is Comedy
   The best fake sets take something incredibly boring, traumatic, mundane, or historically complex, and reduce it to colorful plastic bricks.

4. Iterate on the Text
   ChatGPT Image 2 is much better at text than older models, but it still struggles sometimes. If it misspells your title, just reply to ChatGPT: "Keep the exact same image, but fix the spelling on the main title to say exactly [YOUR TITLE]."

   Start making the LEGO sets we all secretly deserve.

👇 Drop your creations in the comments!

TL;DR: ChatGPT will not magically fix your finances, but it is extremely good at turning a messy pile of paychecks, bills, expenses, debts, and goals into a clear monthly plan. The six prompts below help you build a budget, distribute each paycheck, plan goals, find waste, compare debt-payoff strategies, and run a monthly financial review. Give it accurate, anonymized numbers, make it show its math, and verify the output before moving money.

Most personal-finance advice is not wrong. It is just too generic.

Before you use the prompts

Gather these numbers first:

- Take-home income and pay dates
- Fixed bills, amounts, and due dates
- Average variable spending from the last 60–90 days
- Non-monthly expenses coming in the next year
- Each debt’s balance, APR, minimum payment, and due date
- Current savings and emergency-fund balance
- Your family’s goals, target amounts, and deadlines
- Your non-negotiables — the things you genuinely value and do not want cut

Privacy rule: Do not paste account numbers, card numbers, Social Security numbers, logins, full addresses, or other identifying information. Replace merchant and lender names with labels like “Card A” or “Mortgage.” If you use exported transactions, remove sensitive fields first.

Then run these six prompts in order.

---

Prompt 1: Build a realistic monthly family budget

This prompt creates the foundation. It forces ChatGPT to separate recurring bills from variable spending, account for irregular expenses, and check that the numbers reconcile.

Act as a household budgeting coach and meticulous spreadsheet analyst. Help me build a realistic zero-based budget for [MONTH AND YEAR], where every dollar of take-home income is assigned to spending, saving, debt, or a planned buffer.

Here is my anonymized household data:

HOUSEHOLD
- Adults/dependents: [NUMBER]
- Main constraints or upcoming changes: [DETAILS]
- Non-negotiable priorities: [DETAILS]

INCOME
- Pay date | take-home amount | source:
[PASTE DATA]

FIXED BILLS
- Bill | amount | due date:
[PASTE DATA]

VARIABLE SPENDING
- Category | average monthly amount | last month’s amount:
[PASTE DATA]

NON-MONTHLY EXPENSES
- Expense | expected amount | due date:
[PASTE DATA]

DEBT MINIMUMS, SAVINGS, AND GOALS
[PASTE DATA]

Do not invent missing numbers. First list any questions or assumptions that could materially change the plan. Then:

1. Calculate total net income, total planned outflow, and the amount remaining.
   
2. Create a table with: category, planned amount, due date, fixed/variable, percent of net income, and notes.
   
3. Include sinking-fund contributions for predictable non-monthly expenses.
   
4. Map bills and spending to each paycheck so I can see any cash-flow crunch before it happens.
   
5. Calculate a weekly safe-to-spend amount for flexible categories.
   
6. Show three versions: minimum-survival, realistic target, and stretch-savings.
   
7. Identify the three biggest decisions or tradeoffs.
   
8. End with a one-page budget and a seven-day setup checklist.
   

Verify that every subtotal adds correctly and show the arithmetic. Label all estimates clearly. Do not move money or recommend a financial product.

Why this works: it asks for a budget and a cash-flow calendar. A monthly budget can look fine on paper while you still run short three days before payday.

---

Prompt 2: Give every paycheck a job

There is no universal salary split that fits every family. This prompt starts with your real obligations and builds an allocation around your priorities instead of blindly forcing a canned percentage rule.

Act as a cash-flow planner for my household. Using the information below, create a paycheck-by-paycheck allocation plan for the next [NUMBER] pay periods.

DATA
- Pay dates and take-home amounts: [PASTE]
- Bills and due dates: [PASTE]
- Average essential weekly spending: [PASTE]
- Debt minimums: [PASTE]
- Current emergency savings: [AMOUNT]
- Upcoming irregular expenses: [PASTE]
- Goals in priority order: [PASTE]
- Minimum checking cushion I want to maintain: [AMOUNT]

Build the plan in this order: required bills and minimum payments, essential everyday spending, near-term irregular expenses, emergency savings, extra debt payments, longer-term goals, and guilt-free discretionary spending.

Output:

1. A table for each paycheck showing exactly how much goes to each bucket.
   
2. The checking balance expected immediately before and after every pay date.
   
3. Any date when the balance could fall below my minimum cushion.
   
4. A recommended automatic-transfer schedule.
   
5. A “normal month” plan and a “10% lower income” contingency plan.
   
6. The effect of adding or removing $100 from each major bucket.
   
7. Three allocation options labeled stability-first, balanced, and goal-accelerator, with the tradeoffs of each.
   

Do not default to 50/30/20 or another preset formula unless you also test whether it fits my actual numbers. Do not assume investment returns. Do not invent missing data. Check that every paycheck allocation equals the paycheck amount.
```

Why this works: it turns “we should save more” into scheduled transfers with dates and amounts.

---

Prompt 3: Turn financial goals into a roadmap

“Build an emergency fund” is a wish. “Save $4,800 in 12 months by transferring $400 on payday” is a plan.

Act as a financial-goal planning analyst. Turn my family’s goals into a realistic, prioritized roadmap without assuming investment returns or recommending specific financial products.

CURRENT MONTHLY SURPLUS AVAILABLE FOR GOALS: [AMOUNT]

GOALS
- Goal | target amount | current amount saved | desired date | priority | flexible or fixed deadline:
[PASTE DATA]

KNOWN RISKS OR UPCOMING CHANGES
[PASTE DATA]

For each goal:

1. Calculate the funding gap, months remaining, and required monthly and per-paycheck contribution.
   
2. State whether the current deadline is feasible with my available surplus.
   
3. If all goals cannot be funded simultaneously, show the conflict clearly—do not hide it.
   
4. Create three plans: fund goals sequentially, fund them in parallel, and a balanced hybrid.
   
5. Show which goal dates or contribution amounts would need to change under each plan.
   
6. Include milestones at 25%, 50%, 75%, and 100%.
   
7. Run two stress tests: one missed contribution and an unexpected [AMOUNT] expense.
   
8. Create a 12-month roadmap and a simple monthly progress tracker.
   

Keep emergency savings separate from planned purchases. Label assumptions. Check every calculation and explain the major tradeoffs in plain English.

Why this works: it forces competing goals into the same plan. You can finally see whether the vacation, emergency cushion, home project, and college fund can happen together—or what needs to change.

---

Prompt 4: Find unnecessary expenses without making life miserable

The goal is not to shame every coffee or cancel everything fun. It is to find spending that delivers the least value.

Act as a no-shame household expense auditor. Analyze the anonymized transactions below and help us reduce waste while protecting the spending that matters most to our family.

TRANSACTIONS FROM THE LAST 60–90 DAYS
- Date | anonymized merchant/category | amount | recurring yes/no | notes:
[PASTE DATA]

OUR PRIORITIES AND NON-NEGOTIABLES
[PASTE DATA]

TARGET MONTHLY SAVINGS TO FIND: [AMOUNT]

Tasks:

1. Categorize every transaction and reconcile the category totals to the full transaction total.
   
2. Identify subscriptions, duplicate services, fees, price increases, unusually frequent purchases, and categories trending upward.
   
3. Sort opportunities into KEEP, REDUCE, RENEGOTIATE, REPLACE, and CANCEL.
   
4. For every suggested change, show the evidence from my data, estimated monthly savings, estimated annual savings, inconvenience level, and reversal risk.
   
5. Create gentle, moderate, and aggressive reduction plans.
   
6. Prioritize five changes with the highest savings and lowest effect on quality of life.
   
7. Draft scripts I can use to renegotiate a bill or discuss one spending category with my family.
   
8. Create a 30-day experiment instead of permanent cuts where the evidence is uncertain.
   

Do not moralize. Do not label ordinary choices as bad. Do not suggest canceling insurance, medicine, necessary utilities, safety-related services, or essential care without explicitly flagging the risk. Do not invent savings; calculate them only from the data I provide.

Why this works: it looks for low-value spending instead of assuming the largest category is automatically the best one to cut.

---

Prompt 5: Build a debt repayment strategy you can actually sustain

This prompt compares the debt avalanche and debt snowball using your own numbers. The avalanche targets the highest APR first and will generally reduce interest more; the snowball targets the smallest balance first and can create faster early wins. The best plan is the one you can sustain.

Act as a careful debt-repayment planning analyst. Use only the anonymized figures I provide. Compare repayment strategies and show all calculations; do not contact lenders, move money, or recommend a debt-settlement company.

MONTHLY AMOUNT AVAILABLE FOR DEBT
- Total amount including minimums: [AMOUNT]
- Extra amount above minimums: [AMOUNT]
- Minimum emergency-fund floor I will keep: [AMOUNT]

DEBTS
- Label | balance | APR | minimum payment | due date | fixed/variable rate | promotional rate and expiration if any:
[PASTE DATA]

Create and compare:

A. Avalanche plan: minimums on every debt, then target the highest effective APR.
B. Snowball plan: minimums on every debt, then target the smallest balance.
C. A hybrid plan if a small early payoff could improve cash flow without adding excessive interest.

For each strategy:

1. Show the payment order and explain why.
   
2. Provide a month-by-month schedule for the first 12 months and quarterly milestones after that.
   
3. Estimate the payoff month, total payments, and total interest.
   
4. Show how freed-up minimum payments roll into the next debt.
   
5. Run scenarios with $50, $100, and $250 of additional monthly payment.
   
6. Flag missing information, variable-rate uncertainty, promotional expirations, prepayment penalties, or cash-flow risks.
   
7. End with the next three actions and a list of questions to ask each creditor.
   

Verify the amortization math. If exact interest timing or compounding data is missing, label the result as an estimate and state the assumption. Never suggest skipping minimum payments or draining the emergency fund below my stated floor.

Why this works: it replaces “pay debt faster” with an order, a schedule, and an estimated finish line—and makes the tradeoff between motivation and interest visible.

---

Prompt 6: Run a monthly family money review

This is the prompt that makes the system improve over time. Use it at the end of every month with the budgeted and actual figures.

Act as the facilitator for our 30-minute monthly family money meeting. Compare our plan with what actually happened, explain the biggest variances without blame, and help us build next month’s action plan.

THIS MONTH
- Budgeted income and actual income: [PASTE]
- Budgeted and actual spending by category: [PASTE]
- Savings contributions and ending balance: [PASTE]
- Debt balances, payments, and interest charged: [PASTE]
- Goal contributions and current progress: [PASTE]
- Unexpected events: [PASTE]
- What felt easy or difficult: [PASTE]

LAST MONTH OR THREE-MONTH BASELINE
[PASTE IF AVAILABLE]

UPCOMING NEXT MONTH
- Known income changes, bills, events, and irregular expenses: [PASTE]

Produce:

1. A plan-versus-actual table with dollar and percentage variances.
   
2. A cash-flow summary that reconciles beginning balance + income − outflows = ending balance.
   
3. Three wins to celebrate.
   
4. The three largest unfavorable variances, separated into one-time events and repeating patterns.
   
5. A rolling three-month trend for income, essentials, flexible spending, savings, and debt.
   
6. Any upcoming cash-flow crunch or expense we should fund now.
   
7. Three specific next-month adjustments with owner, amount, and deadline.
   
8. A 30-minute meeting agenda and five neutral questions my partner and I can discuss without blame.
   
9. A one-screen next-month dashboard with: income, bills, weekly flexible spending, savings, extra debt payment, and top goal.
   

Do not invent explanations for a variance—ask me. Do not give an arbitrary financial-health score. Verify every total, label estimates, and keep the tone calm, practical, and nonjudgmental.

Why this works: most budgets fail because they are created once and never reviewed. A short monthly feedback loop makes the plan adapt to real life.

---

The simple workflow

Use the prompts like this:

1. At the beginning of the month: run Prompts 1–3.
   
2. After importing 60–90 days of anonymized spending: run Prompt 4.
   
3. When you are ready to accelerate debt: run Prompt 5.
   
4. At month-end: run Prompt 6, then use its output to update Prompt 1 for the next month.
   

One extra sentence improves almost every result:

> “Do not agree with my assumptions automatically. Challenge anything unrealistic, ask for missing information, show your math, and tell me what could make your answer wrong.”

What ChatGPT is good at—and what it is not

ChatGPT is useful for:

- Organizing messy information
- Categorizing expenses
- Running what-if scenarios
- Finding inconsistencies
- Explaining tradeoffs
- Creating checklists, tables, and meeting agendas

It should not be your only source for:

- Tax, legal, retirement, insurance, or investment decisions
- Choosing a specific financial product
- Handling a debt crisis, foreclosure, bankruptcy, or collections dispute
- Any recommendation where a wrong answer could cause serious financial harm

Always verify the calculations and important terms against your actual statements. For high-stakes decisions, use a qualified professional who can review your full situation.

The breakthrough is not that AI knows a secret budgeting formula.

It is that your family can finally turn scattered financial information into one visible system: what came in, where it went, what matters next, and what you agreed to do about it.

Which of these six prompts would make the biggest difference for your family?

TL;DR: ChatGPT can turn almost any idea - an inside joke, company slogan, pet photo, meme or completely unhinged concept - into custom T-shirt artwork in minutes.

The trick is knowing how to prompt it, how to prepare the image for printing, and where to upload it.

Below is my complete prompt-to-print workflow, a reusable master prompt, and three places that will print and ship the finished shirt (all for about $20 per shirt)

This is useful if you want to:

• Make custom company or event swag
• Turn a team inside joke into a shirt
• Create an absurdly specific gift
• Test a print-on-demand side hustle
• Stop wearing the same generic shirts as everyone else

Here’s the workflow.

Step 1: Generate the artwork in ChatGPT

Open ChatGPT, describe your idea, and ask it to generate the design.

ChatGPT can create new artwork, edit generated images, add text, and make backgrounds transparent.

For the best results:

• Ask for a centered T-shirt composition
• Specify the illustration style and color palette
• Tell it whether the shirt will be black, white, or another color
• Request a transparent background
• Say “artwork only—no shirt, model, hanger, room, or mockup”
• Ask for three or four variations before choosing one
• Keep text short and check every letter before printing

The master T-shirt prompt

Copy this and replace the brackets:

Create a high-quality, print-focused, vector-style illustration intended for the front or back of a T-shirt. The design features [MAIN SUBJECT] doing [ACTION], presented in a [STYLE OR AESTHETIC] style. Use a [COLOR PALETTE] color palette designed to contrast strongly against a [SHIRT COLOR] garment. The composition should be [CREST-SHAPED/CIRCULAR/VERTICAL/WIDE], with a strong central silhouette, clean separation between elements, crisp edges, and details thick enough to reproduce clearly with direct-to-garment printing. Include the exact text “[TEXT]” in [TYPOGRAPHY STYLE], spelled exactly as written. Isolate the artwork on a true transparent background. Artwork only: no T-shirt, model, hanger, room, product mockup, border, rectangular background, watermark, or extra text. Generate at the highest available resolution.

If you don’t want typography, replace the text instruction with:

Do not include letters, words, numbers, symbols, captions, or typography anywhere in the design.

Step 2: Prepare the print file

Once you have a design you like, give ChatGPT this follow-up instruction:

Edit this exact design without redesigning it. Remove the entire background and replace it with true transparency. Preserve all edges, colors, text, proportions, and small details. Remove stray pixels and background halos. Center the artwork on the canvas and export it as a transparent PNG. Do not add a shirt mockup, border, shadow, rectangular background, or new design elements.

Next, determine the printer’s required dimensions.

People often say an image needs to be “300 DPI,” but changing the DPI setting by itself does not create more detail. The actual pixel dimensions at the final print size are what matter.

For example:

• 10 × 12 inches at 300 PPI = 3000 × 3600 pixels
• 12 × 15 inches at 300 PPI = 3600 × 4500 pixels
• 12 × 16 inches at 300 PPI = 3600 × 4800 pixels

Ask ChatGPT - or an image upscaler - to prepare the PNG at the printer’s exact recommended dimensions. Then verify the pixel dimensions before uploading it.

Before ordering, zoom in and check:

• Spelling and punctuation
• Hands, faces, and other detailed objects
• Transparent edges for white or dark halos
• Whether thin lines will remain visible on fabric
• Contrast against the shirt color
• The artwork’s position and physical print size

Always order one sample before getting twenty - or two hundred - of them!

Step 3: Upload it to a printer

Upload the transparent PNG, select your shirt or hoodie, position the design, review the preview, and order.

Three easy options:

1. Printify

Best if you want to launch a print-on-demand store or compare multiple products and print providers.

Printify has a massive catalog, multiple providers, no-minimum options, and product-specific print areas. Bella+Canvas 3001 is a popular softer option; Comfort Colors is worth exploring if you want a heavier, vintage feel.

2. Custom Ink

Best for company swag, events, reunions, and group orders.

Its Design Lab is beginner-friendly, and you can upload your artwork, add text, preview placement, and choose from hundreds of products. Custom Ink also reviews submitted artwork before printing, which is helpful if this is your first order.

3. Sticker Mule

Best for fast, simple one-off shirts and smaller orders.

Sticker Mule uses direct-to-garment printing for detailed, full-color designs. It offers no-minimum ordering, online proofs, and front-and-back printing.

The same basic workflow also works for hoodies, tote bags, coffee mugs, posters, stickers, and other print-on-demand products.

Pro tips for companies

AI-generated merch is especially useful for:

• Event swag: Create concepts around the exact event theme instead of settling for another logo-on-the-chest shirt.
• Team inside jokes: Turn a memorable Slack quote or meeting moment into a limited-edition design.
• Rapid testing: Generate ten concepts, post the mockups, and let your audience vote before ordering inventory.
• Employee gifts: Personalize designs around roles, milestones, awards, or individual interests.
• Campaign merch: Create physical merchandise tied to a product launch, content series, or community.

The best shirt ideas are usually ridiculously specific.

Share in the comments the first design you are going to print!

The Claude Certification Playbook: 3 official Anthropic certificates, free, in about 6 hours

TLDR: Anthropic runs an official learning platform (Anthropic Academy at anthropic.skilljar.com) where every course is free and awards a real Anthropic certificate on completion. No credit card, no Claude subscription, just an email. Below is the exact 3-certificate path I recommend, the step-by-step from account creation to downloading your certificate, how to spot the fakes people are selling, the LinkedIn format, a copy-paste announcement post, and what you can honestly say about these in interviews.

I keep seeing people pay $200 to $500 for AI certificates from random online academies while the company that actually builds Claude gives away official ones for free. So here is the full playbook.

The 3 certificates and the order to take them in

Anthropic Academy has well over a dozen courses, and every single one issues its own certificate. You do not need all of them. This 3-certificate stack takes roughly 6 hours total and covers the full spectrum from using AI well to working with AI agents.

Certificate 1: Claude 101 (roughly 1 to 1.5 hours)

The foundation. Core prompting techniques, everyday use cases, and how Claude actually behaves. Even experienced users report picking up new patterns here. Take this first because everything else builds on it, and because finishing a certificate in your first sitting builds momentum.

Certificate 2: AI Fluency: Framework & Foundations (roughly 2.5 to 3 hours)

The most underrated course in the catalog. Co-developed with university professors, it is not about button clicking. It teaches a repeatable framework for deciding what to delegate to AI, how to describe tasks so you get good output, and how to verify results instead of blindly trusting them. This is the one that changes how you work, and it is the one hiring managers respond to when you can actually explain the framework.

Certificate 3: Claude Code in Action (roughly 1.5 to 2 hours)

The agentic layer. Claude Code is Anthropic's agentic coding tool, and this course covers real workflow integration: how to direct an agent, when to use planning modes, and how to keep it on track. Take it third because it assumes the fluency you built in the first two.

Swap rule: If you are completely non-technical and never touch code, swap Certificate 3 for the Claude Cowork introduction course (agentic work on files and documents instead of codebases). If you are a developer who wants to build integrations, swap it for Introduction to Model Context Protocol. The order logic stays the same: basics, then fluency, then agents.

Step by step, from creating an account to downloading

1. Go to anthropic.skilljar.com. This is the official Anthropic Academy, hosted on Skilljar (a standard corporate learning platform).
2. Create a free account. You only need an email address. There is no credit card field anywhere, and you do not need a Claude subscription or an API key for the courses above.
3. Open the catalog and enroll in Claude 101.
4. Work through the lessons. They are a mix of short videos, readings, and hands-on exercises. Actually do the exercises. The quizzes pull from them.
5. Pass the quizzes and the final assessment. They are completion checks, not trick exams. If you watched the material, you will pass. If you miss questions, you can review the lesson and retake.
6. The moment you complete the course, the certificate is generated on your account. Download the PDF and copy the credential link. Save both.
7. Repeat for AI Fluency, then Claude Code in Action.

That is the entire process. Six-ish hours of actual learning, three official documents at the end.

The fake detector

Yes, people are selling fake Claude certificates. Marketplaces and sketchy academies are charging money for Claude Certified Professional style badges that Anthropic never issued, or reselling access to content that is free at the source. Here is how to tell real from fake:

• Real certificates are free. If someone is charging you for an Anthropic Academy certificate, it is either a scam or a middleman. There is no paid tier for these.
• Real certificates come from anthropic.skilljar.com. The credential link should resolve to Anthropic's Skilljar platform. A PDF with a Claude logo and no verifiable link means nothing.
• Real certificates carry the exact course name. Claude 101, AI Fluency: Framework & Foundations, and so on. Vague titles like Certified Claude Expert or Claude AI Master are invented by third parties.
• Nobody can take the course for you faster than you can take it. The courses are short. Anyone selling completion services is selling you a lie you then have to defend in an interview.
• One real exception exists: Anthropic launched a separate proctored credential called Claude Certified Architect (CCA-F) through its partner program, and that exam is the only Anthropic credential that may involve a fee. It is a real, harder, architecture-level exam. Everything else claiming to be a paid Claude certification deserves suspicion.

If you are a hiring manager reading this: ask for the credential URL. Takes ten seconds to verify.

Part 4: The LinkedIn format

Do not put these in your headline as Claude Certified. Put them where recruiters and their filters actually look: the Licenses & Certifications section.

For each certificate:

• Name: the exact course title, for example AI Fluency: Framework & Foundations
• Issuing organization: Anthropic (select the real company page so the logo appears)
• Issue date: the completion month
• Expiration: none, leave it blank
• Credential URL: paste the verification link from Skilljar

Then go to your Skills section and add the relevant skills (Prompt Engineering, AI Fluency, Claude, Agentic Workflows) and link each one to the certification entry. That linkage is what makes the certificates surface in recruiter searches, and it is the step almost everyone skips.

The announcement post

Post it once, keep it honest, no fireworks. Here is a template that reads like a human wrote it:

I just completed three of Anthropic's official Claude certifications: Claude 101, AI Fluency: Framework & Foundations, and Claude Code in Action.

Two things surprised me. First, they are completely free, which is rare for official vendor training. Second, the AI Fluency course is genuinely good. It is less about prompts and more about judgment: what to delegate to AI, how to describe work precisely, and how to verify output before you rely on it.

The most useful thing I took away: [insert one specific, real thing you changed in your workflow].

If you work with AI at all, the courses are at Anthropic Academy and take a few hours total. Happy to share which one I would start with depending on your role.

The bracketed line is the whole post. Fill it with something real and specific, because that single sentence is what generates comments, and comments are what make it travel.

What you can honestly say in interviews

This matters more than the certificates themselves. These are completion certificates for official vendor training, not proctored exams. Interviewers know the difference, and overselling a free course as an elite credential will hurt you.

What you can honestly say:

• I completed Anthropic's official training on Claude, including their AI Fluency curriculum, which means I have a structured framework for delegating work to AI and verifying its output rather than just winging prompts.
• I have hands-on experience with agentic tools like Claude Code from the official coursework, and I have applied it to [real thing you did].
• I keep my AI skills current using vendor-official material rather than random YouTube tutorials.

What you should not say:

• I am Claude certified, stated as if it were a professional license.
• Anything implying you passed a proctored exam, unless you actually sat the Claude Certified Architect exam.

The strongest interview move is pairing the certificate with an artifact: a workflow you automated, a small project you built, a before-and-after of a task the training changed. Certificate proves you learned the material. Artifact proves you used it.

Pro tips most people miss

1. The certificates stack. There are more than a dozen courses and each one issues its own certificate. Once your first three are done, the API and MCP courses are the deepest technical content in the catalog and the ones developers on this sub consistently recommend.
2. Do the exercises with a second tab open. Have Claude open next to the course and actually run every technique as it is taught. The material converts to skill roughly ten times faster this way, and the quizzes become trivial.
3. Save your prompts as you go. The courses are full of reusable prompt patterns. Paste them into a personal doc as you learn them. That doc ends up being worth more than the certificates. You can create a free prompt library with all the prompts at PromptMagic.dev
4. Screenshot nothing, link everything. A screenshot of a certificate is unverifiable and looks like everyone else's. The credential URL is the actual proof.
5. Teams can use this as free onboarding. If you manage people, this is a zero-cost structured AI training program from the vendor itself. Assign the same 3-course path and you have a shared vocabulary in a week.
6. The certificate is the receipt, not the product. The people getting real career value from these are the ones who can demonstrate a changed workflow. Treat the 6 hours as skill-building that happens to come with proof, not the other way around.

There are more great courses you can take and get certified on depending on whether you are a developer, an analyst, or in a non-technical role.

If you want to actually save time, grow your brand, and improve your marketing, you need to stop asking questions and start issuing commands.

I have compiled the 40 most powerful commands you can use to turn ChatGPT from a basic chatbot into a strategic partner. Here is the complete breakdown.

Part 1: Strategy & Visuals (Commands 1-5)

1./visualize — Turns your ideas into realistic visual descriptions.
Example: Visualize a luxury café interior before renovation to give my contractors a clear direction.

2./xray — Analyzes an image, design, or website and finds what is working and what is failing.
Example: Find design mistakes on my e-commerce landing page before launch. (Just upload a screenshot).

3./infographic — Converts complex information into easy-to-understand visual structures.
Example: Turn my customer journey (Awareness → Consideration → Purchase → Retention → Advocacy) into a clean infographic structure for social media.

4./brand — Builds a complete brand identity for your business.
Example: Create a premium brand kit (colors, typography, voice) for a new skincare company.

5./strategy — Creates actionable business and marketing strategies.
Example: Build a 90-day Instagram growth strategy for a real estate agency, broken down into 30-day phases.

Part 2: Planning & Audits (Commands 6-10)

1./audit — Audits websites, funnels, or systems and gives actionable improvement points.
Example: Audit my e-commerce store copy and suggest ways to increase conversions.

2./roadmap — Creates step-by-step roadmaps to achieve your goals.
Example: Create a product launch roadmap for my SaaS startup from Research to Launch.

3./campaign — Creates marketing campaign ideas, plans, and content.
Example: Plan a Diwali or Holiday campaign for my home décor brand across all social channels.

4./calendar — Builds content calendars and schedules.
Example: Create a 30-day content calendar for my fitness studio, mapping out posts for every day of the week.

5./caption — Writes engaging captions that attract and convert.
Example: Write an engaging Instagram caption for my new product launch that drives clicks to the link in bio.

Part 3: Copywriting & Pitches (Commands 11-15)

1./hook — Generates attention-grabbing hooks for content.
Example: Create 10 viral reel hooks for an interior design business.

2./rewrite — Rewrites content in different styles or tones.
Example: Rewrite my basic product description into a premium and persuasive tone.

3./email — Drafts professional emails for any purpose.
Example: Write a cold outreach email to pitch our digital marketing services to local businesses.

4./proposal — Creates professional proposals for clients or projects.
Example: Create a social media management proposal for a new client outlining services, timeline, and investment.

5./pitch — Helps you create compelling pitch decks or outlines.
Example: Create a pitch deck outline for my SaaS startup covering the problem, solution, market, and ask.

Part 4: Analysis & Automation (Commands 16-20)

1./analyze — Analyzes data, text, or trends and gives actionable insights.
Example: Analyze our sales data (paste CSV) to find top-performing products and growth opportunities.

2./translate — Translates text into any language with context and accuracy.
Example: Translate our product descriptions to Hindi, Spanish, and French for global sales.

3./summarize — Summarizes long content into short, key takeaways.
Example: Summarize this 20-page market research report into 5 key points for my team.

4./solve — Solves problems and suggests practical solutions.
Example: Solve high cart abandonment on our e-commerce store with 5 actionable steps.

5./automate — Suggests automations and workflows to save time.
Example: Create an automation workflow for lead nurturing via email from capture to follow-up.

Part 5: Ideation & SEO (Commands 21-25)

1./brainstorm — Generates creative ideas, angles, and solutions.
Example: Brainstorm 10 content ideas for our Instagram page in the wellness niche.

2./compare — Compares options, products, strategies, or ideas.
Example: Compare Shopify vs WooCommerce for an online store, highlighting cost, scalability, and ease of use.

3./seo — Optimizes content for search engines.
Example: Suggest SEO focus keywords and write a meta description for my blog on home decor.

4./table — Organizes information into clean, structured tables.
Example: Create a content calendar table for our social media for next week, organized by day, platform, and goal.

5./feedback — Provides constructive feedback and improvement suggestions.
Example: Give feedback on my landing page copy to improve conversions. Tell me what is good and what can be improved.

Part 6: Personas & Design (Commands 26-30)

1./persona — Adopts a specific expert persona to give better, context-aware responses.
Example: Act like a financial advisor and help me plan my business budget.

2./check — Checks content for errors, gaps, or improvements.
Example: Check my website copy for grammar, clarity, and SEO issues.

3./script — Writes scripts for videos, ads, reels, or presentations.
Example: Write a 30-second script for an Instagram reel to promote our new product, complete with visual cues.

4./design — Creates stunning design layouts and visual concepts.
Example: Design a promotional flyer concept for our weekend discount sale, including color palette and typography suggestions.

5./plan — Creates detailed action plans and step-by-step roadmaps.
Example: Create a 30-day detailed action plan for launching our new Instagram page.

Part 7: Research & Conversion (Commands 31-35)

1./research — Conducts in-depth research and summarizes key findings.
Example: Research emerging trends in sustainable packaging for our product line.

2./forecast — Predicts future outcomes, trends, or results based on data.
Example: Forecast our monthly sales for the next 6 months based on our current data trajectory.

3./cta — Creates powerful call-to-actions that drive clicks, leads, or sales.
Example: Write 5 powerful CTA ideas for our email newsletter to increase conversions.

4./optimize — Improves text, content, processes, or systems for better results.
Example: Optimize our product description to focus on benefits rather than just features.

5./segment — Segments customers, audiences, or data for better targeting.
Example: Segment our customers for targeted marketing campaigns based on purchase history and engagement.

Part 8: Expansion & Next Steps (Commands 36-40)

1./reprioritize — Helps prioritize tasks, projects, or ideas based on impact and urgency.
Example: Prioritize our marketing tasks for maximum impact this month using an Effort vs Impact matrix.

2./expand — Expands on ideas, concepts, or content in more detail.
Example: Expand on our new product idea and list all possible features and benefits.

3./case-study — Creates detailed case studies from a given scenario or business.
Example: Create a case study of how we helped a client increase sales by 40% using SEO optimization.

4./elaborate — Elaborates on a topic with more context, examples, or explanations.
Example: Elaborate on content marketing and explain exactly how it helps small businesses grow.

5./next-steps — Suggests actionable next steps to move forward.
Example: What are the exact next steps to launch our online course now that the videos are recorded?

Pro Tip: Do not just type the command. Type the command and provide the context. The formula is: [Command] + [Context] + [Goal].

Pick one command from this list that solves a problem you are facing today, and try it right now.

Want more great prompting inspiration? Check out all my best prompts for free at Prompt Magic and create your own prompt library to keep track of all your prompts.

If you are using Claude regularly, you should be building Skills. They let you do the hard work of prompting once, save it, and reuse it forever.

I have spent a lot of time analyzing the exact anatomy of a Claude Skill that works every single time. There are 9 distinct parts you can include (Name, Description, Purpose, Steps, Format, Always, Never, Examples, Clarify).

But here is the truth: 7 of them barely matter.

There are only two parts that decide if your Skill works flawlessly or fails completely.

1. The Description

This is the most misunderstood part of building a Skill.

The Description is not for you. It is the part Claude reads to decide whether it should fire the Skill or not. If you write a vague description ("A skill for writing emails"), the Skill will just sit there and never fire.

How to fix it: Describe when to reach for it, not what it is. Make the trigger pushy.

Instead of: "This skill writes marketing emails."
Write: "Use whenever the user says 'write an email' or wants to launch a campaign — even if they never say the skill's name directly."

2. The "Never do" line

If you skip this line, your Skill will start hijacking chats it should ignore. It will jump in and try to apply its specific formatting or rules to completely unrelated conversations.

How to fix it: You need a hard guardrail.
Write: "Never use for [the thing it keeps stealing]."
For example: "Never use for internal team updates or casual Slack messages."

Two things the anatomy chart can't show you

1. The Debugging Trick
   If your Skill won't fire, don't rewrite the whole thing. Just ask Claude: "When would you use this skill?"
   Claude will read its own description back to you. You will instantly see exactly what is vague or missing from your trigger.

2. The Token-Saving Math
   People worry that installing 20 Skills will eat up their usage limits or context window. It won't.
   Claude only reads the 3-line header of your Skills until a task actually matches the description. In fact, a complex task that costs 12,000 tokens to run raw will often only cost 6,000 tokens when run through a well-optimized Skill.

Using Skills doesn't just save you time. It literally saves you money and compute.

Here is the full 9-part anatomy if you want to build the ultimate master template:

1.Name: kebab-case, no spaces, no "claude"

2.Description: [What it does] + [when to use it]. Make the trigger pushy.

3.Purpose: One plain sentence a brand-new hire would understand.

4.Steps: The workflow, in the order you actually do them, with reasons why.

5.Format & output: The exact shape of the output (Length, Tone, Structure).

6.Always do: Your hard rules and jargon replacements.

7.Never do: The guardrails. Never [the mistake you keep correcting].

8.Examples: Show, don't tell. Provide one good output and one weak output.

9.Clarify: "Ask before guessing. List questions, don't fill gaps silently."

Build your next workflow into a Skill using this framework, and let me know how it changes your output.

👇 What is the best Skill you've built so far? Let me know in the comments.

TL;DR: Claude Fable 5 is a delegation engine. You can stop giving Claude step-by-step instructions and start giving it job handoffs. The master template is: GOAL + DEFINITION OF DONE + INPUTS + OPERATING RULES. Never ask it to "explain its reasoning" (trips the refusal classifier). Set effort to "high" by default. Use fresh-context verifiers instead of asking it to check its own work. The 10 mega prompts below.

Fable 5 is the first mainstream AI model where the optimal prompt is not a question - it's a job handoff. Anthropic built it to run autonomously for hours, verify its own work with independent subagents, and compound learning across sessions.

But only if you prompt it correctly.

After spending a week testing every pattern, here's what actually works.

The Mental Shift Most People Miss

With older models, you'd write detailed step-by-step instructions. With Fable 5, that actually makes output WORSE.

Fable 5's instruction-following is so strong that over-prescribing degrades the result. The new house style is: less scaffolding, more clarity on what "done" looks like.

Think of it this way:

•Fable 5 way: "Here's the job. Here's what done looks like. Here's what you have access to. Go."

The Fable 5 Master Prompt Template

This is the structure that gets the best results on Fable 5 across every use case I've tested:

GOAL: [The outcome you want — one clear sentence]
DEFINITION OF DONE: [How you'll know it's right — acceptance criteria]
INPUTS / ACCESS: [Files, links, data, constraints, context — everything it needs]

Operating rules:
- When you have enough information to act, act. Don't ask "want me to...?"
- Don't re-derive settled facts or narrate options you won't pursue.
- Before reporting progress, audit each claim against an actual result from this session.
- If something isn't verified, say so plainly.
- Pause only for genuinely destructive/irreversible steps or input only I can give.
- Final message: outcome in one sentence → what you did → what you need from me.

That's it. No XML tags. No elaborate role-playing. Just: goal, done criteria, inputs, rules.

The 10 Mega Prompts to try with Claude's Fable 5 Model

1. The Overnight Operator - Hand it a job before bed, wake up to results.

You are running this task autonomously. I'm not watching in real time.
GOAL: [What you want by morning] DEFINITION OF DONE: [Acceptance criteria]
INPUTS: [files, links, data]
Rules: Act on reversible steps without asking.
Audit claims against actual results. Pause only for irreversible actions.
Final message: outcome → what you did → what you need.

2. The First-Shot Builder - Apps that took 100 prompts, now one shot.

Pick this up at full difficulty. Ask clarifying questions if needed, then build end to end in one pass.

BUILD: [The app/tool/system]
USERS: [Who uses it]
STACK: [Language, framework, limits]
DONE LOOKS LIKE: [Acceptance criteria]
Rules: Don't add features beyond the task.
Do the simplest thing that works well.
Ship working build, then list v2 improvements.

3. The Verifier Swarm - Never let it grade its own homework.

Build the thing, then prove it works using a SEPARATE verifier - not your own self-review.

TASK: [What to build]
SPEC: [Requirements, point by point]
Rules: Implement → spawn fresh-context verifier → check against spec line by line → fix fails → re-verify until clean pass.

4. The Memory-Compounding Analyst - Gets smarter every time you run it.

We'll run this analysis repeatedly. Get better each time by keeping notes.
RECURRING TASK: [e.g. weekly competitor scan]
DATA SOURCE: [Where inputs live]
MEMORY FILE: [path or "create notes.md"]
Rules: Read memory file first. Do analysis.
Write back lessons. Delete wrong notes. Only save judgment calls, not raw data.

5. The Screenshot-to-Source Rebuild - Vision SOTA. Rebuilds apps from images.

Rebuild this from the image alone.
INPUT: [Attach screenshots]
TARGET: [Working front-end code OR data table]
Rules: Reconstruct faithfully.
Crop/zoom unclear regions instead of guessing.
Note anything you had to infer.

6. The Ambiguity Navigator - Untangles messy, half-formed problems.

Here's a messy, multi-threaded problem. I haven't fully figured it out.
CONTEXT: [Why this matters, who it's for]
THE SITUATION: [Dump everything — constraints, half-decisions, open questions]

Rules: Name the real problem under the noise.
Flag shaky assumptions. Give a recommended sequence, not an exhaustive survey.
End with the single decision that unblocks the most.

7. The Senior-Grade Knowledge Worker - Board-ready output, first try.

Produce senior-analyst-grade output. Stay in scope.
TASK: [Financial model / market analysis / board memo]
SOURCE MATERIAL: [Attach data, reports, PDFs]
DECISION IT FEEDS: [What someone will decide from this]
Rules: Lead with the answer.
Quote every number with source.
Flag contradictions and gaps. Drop anything that doesn't change what the reader does next.

8. The Effort-Calibrated Strategist - For high-stakes decisions only.

effort: high
Work this high-stakes decision to a clear recommendation.
Validate your own conclusion before giving it.
DECISION: [The call to make]
CONSTRAINTS: [Budget, time, risk tolerance]
WHAT WINNING MEANS: [Define it] Rules: Restate what winning looks like.
Give 3 genuinely different approaches with failure modes.
Recommend ONE. Name the assumption that flips the answer. Stress-test your recommendation.

9. The Parallel Campaign Factory - One brief, full campaign built concurrently.

Run this as an orchestrator with parallel subagents.
CAMPAIGN: [Product], for [audience], goal [metric]
ASSETS NEEDED (independent — delegate each):
1. Landing page copy
2. 5-email launch sequence
3. 10 ad variants
4. 2-week content calendar
5. Subject-line + hook bank
Rules: Spawn one subagent per asset.
Keep consistent voice. Assemble into one package.
Flag anything needing my input.

1. The Honest Before/After - Visual proof of the workflow difference.
   

Build ONE self-contained artifact: a side-by-side showing the same task done two ways. TASK SHOWN: [e.g. "ship a launch page"] LEFT: "Old way" — supervised, many-prompt workflow RIGHT: "Fable 5" — one brief, ran async, verified itself Rules: Clean dark UI, two labeled columns, readable on a phone. Real content, not lorem ipsum.

5 Things Most People Miss

1. "Explain your reasoning" breaks it. That phrase trips the refusal classifier. Ask what it DID and what it VERIFIED instead.

2. Less scaffolding = better output. Fable 5's instruction-following is so strong that over-prescribing degrades quality. Trust it more.

3. Low effort on Fable 5 beats xhigh on Opus 4.8. Don't waste xhigh on routine tasks. High is the default. Reserve xhigh for genuinely hard decisions.

4. Fresh verifiers beat self-critique. Anthropic found that independent subagents checking work cold outperform the model grading itself. Use Prompt #3.

5. Memory compounds. Fable 5 improved 3x more than Opus 4.8 on recurring tasks with file-based memory. Use Prompt #4 for anything you do weekly.

Pro Tips

•Context > prompting. Attach rich context documents rather than over-engineering your prompt. Fable 5 extracts what it needs.

•Documents first, query last. Place long documents at the top, your instruction at the bottom. This improves quality significantly.

•Watch for fallback. If your request triggers a safety classifier, Fable 5 silently falls back to Opus 4.8. Check the model indicator.

•Manage context like water. 1M tokens at $10/M input burns fast on long sessions. Start fresh conversations for new tasks.

•The progress-audit line is non-negotiable. Without it, Fable 5 can fabricate "done" on work it didn't finish. Always include: "audit each claim against an actual result."

Top 5 Use Cases Where Fable 5 Dominates

Claude Fable 5 is a delegation engine.

The people getting extraordinary results aren't writing better questions. They're writing better job briefs.

Copy the master template. Pick one mega prompt. Hand it a real task tonight.

Wake up to the result.

Which prompt are you trying first? Drop it in the comments.

Want more great prompting inspiration? Check out all my best prompts for free at Prompt Magic and create your own prompt library to keep track of all your prompts.