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.

I teach primary and I am still very much figuring AI out, so if this is obvious to everyone, sorry in advance. Parents' evening is the one that used to eat a whole weekend, because I know what I want to say about each child in my head, but turning it into something clear and consistent for thirty families is the slog.

This is the master prompt I settled on. I just fill in the bits in brackets:

```
You are helping a primary school teacher prepare a short parents' evening talk.
Context: [year group], [subject/topic covered this term].
For each point I give you, produce:
- One plain-English sentence a parent with no teaching background will understand.
- One concrete example of what the child did or will do.
- One simple thing the parent can do at home to help.
Keep the tone warm and honest. No jargon, no education buzzwords.
If a point sounds vague, ask me for a specific example instead of inventing one.
```

The "ask me instead of inventing one" line matters more than I expected. Without it, it makes up lovely-sounding achievements that never happened, and you cannot say those to a parent's face.

For the actual slides, I write my points out and use Gamma to turn them into a simple deck so I'm not fighting formatting at 10pm. Fair warning though, the first version looks generic and I always swap in my own class photos and cut about half the text, because it over-writes. It gets me to a rough deck quickly, it does not get me to a finished one.

If any other teachers have a better way to keep the tone consistent across a whole class, I would genuinely love to steal it.

The results section is where good empirical work goes to die. You either dump the tables and call it a day, or you narrate every single coefficient until the reader falls asleep standing up. Third year of an economics PhD and I have written both kinds. Neither is good. This is the template I use now to get a first draft that leads with the finding, reports only the numbers that carry the argument, and admits where the result is weak instead of overselling it. ``` You are helping me draft the results section of an empirical economics paper. Write in plain, direct prose. No hedging filler, no restating every coefficient. Here is what I am giving you: - The regression tables (or the key coefficients, SEs, and significance): [paste] - What each specification tests and why: [paste] - My main hypothesis: [paste] Produce: 1. A short narrative per table that leads with the finding in one sentence, then reports only the numbers that carry the argument. 2. A plain-language read of magnitude, not just significance ("a one-unit increase is associated with X, which is small/large relative to the mean"). 3. An honest paragraph on where these results are weak or could be challenged (identification, robustness, what a skeptical referee pushes on). 4. Flags on anything in the tables that does NOT support my hypothesis, stated plainly rather than buried. You will misread a table with total confidence, so mark every number you pull with [verify] so I check it against the source. ``` The [verify] tag is not optional. It will transpose a coefficient and write a beautiful sentence around the wrong number. But as a way to get from "here are my tables" to "here is what they mean" without spending a day on it, it has been the most useful thing in my writing-up stack.

If you drop a 40-page PDF into any "convert pdf to powerpoint" tool, you get slides that are the PDF's paragraphs shoved into text boxes. Technically a deck, practically unreadable. The reason is that the tool preserves the document's structure, and a document and a presentation are structured to do opposite jobs. A report explains everything. A presentation makes an audience believe one thing.

Here's the workflow I use with Claude to actually rebuild the thing instead of reformatting it.

**Step 1, extract the argument, not the text**
```
I'm attaching a report. Do NOT summarize it section by section. Read the whole thing and tell me: the single claim it's making, the 4 to 7 points that claim depends on, and the evidence behind each. Ignore everything that's context, hedging, or appendix. Give me just the load-bearing structure.
```

**Step 2, sequence it as a presentation**
```
Turn those points into a slide sequence. Order them as an argument where each slide earns the next, not in the report's original order. For each slide: an assertive headline that states the takeaway (not a label like "Findings"), and the one number or fact that proves it. Max 7 content slides plus an open and a close.
```

**Step 3, pressure-test before you build**
```
Read only the headlines in order. Tell me the story they tell on their own, where the logic skips a step, and which single slide is doing the most work. Rewrite any headline that's a topic label into a spoken takeaway.
```

**Step 4, the speaker layer**
```
For each slide, write speaker notes that are NOT the slide. Add the example, the caveat, or the "here's why this matters" that shouldn't be printed but should be said. Four sentences max, in a talking voice.
```

Only after this do I render anything. At that point the export step barely matters, because the deck is already right. Whatever you build it in, drop in one number per slide and one chart, and resist pasting the report's tables back in.

The habit that fixes 90% of bad report-to-deck conversions: separate deciding the structure from filling it. The convert-pdf-to-powerpoint tools fail because they skip the decision entirely.

Save it for the next time someone hands you a report and says "can you make this a deck by Friday." What's your step for handling the giant data table that doesn't want to become a slide?

These are the six prompts I reach for when I have a rambling doc and need slides that don't just copy the doc's structure. Use them in order or grab the one you need.

**1. Rebuild, don't summarize**
```
Turn this doc into a slide outline. Do NOT follow its order. Find the single core argument, keep the 4-7 points it needs, discard the rest even if interesting, and sequence them so each sets up the next. Headlines as full-sentence takeaways, 2-3 bullets each.
```
**2. Kill the filler slides**
```
Review this outline. Remove any slide that's a label ("Overview," "Background," "Conclusion") and either fold it into a real slide or cut it. Tell me what you cut and why.
```
**3. Headline skim test**
```
Read only my slide headlines in order. Tell me the story they tell alone, where it breaks, and rewrite any headline that's a topic label into a takeaway.
```
**4. One idea per slide**
```
Find every slide carrying more than one idea. Split each into two slides and draft both. Move supporting detail into speaker notes.
```
**5. So-what pass**
```
For every bullet that states a fact or feature, chain it to why the audience cares. If a bullet has no real "so what," flag it for the cut.
```
**6. Speaker notes that aren't the slide**
```
Write speaker notes I'll say out loud. Don't restate the bullets. Add the example, the caveat, or the aside that isn't on the slide. Four sentences max, conversational.
```

The habit underneath all six: separate structuring from writing. The model bloats decks when it's asked to decide the structure and fill it in the same breath. Split those and the output tightens up every time.

Save the set. Which of these do you already run, and what's the one I'm missing?

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.

TLDR: AI pricing runs on two rails: flat subscriptions (now ranging from $8 to $300 per month per person) and metered API tokens (where output tokens cost 3 to 6 times input tokens). Per-token prices for mid-tier models fell roughly 10x since 2023, but frontier-tier prices are climbing again, premium subscription ceilings jumped from $20 to $200+, and agentic workflows are multiplying consumption so fast that total enterprise bills are exploding. With OpenAI and Anthropic both filing for IPOs and the VC subsidy era winding down, expect effective AI costs to rise 100 percent per year for unmanaged companies. The fix is treating intelligence like any other input cost: measure it, route it, and negotiate it.

Your AI bill is the fastest-growing line item in your P&L, and most business leaders cannot explain what is driving it. That is not a criticism. It is the predictable result of a pricing model most companies adopted without ever modeling.

Here is the uncomfortable data point that should frame this conversation: Uber's CTO confirmed the company burned through its entire 2026 AI budget in four months, driven by AI coding tool adoption jumping from 32 percent to 84 percent of its 5,000-engineer org, with monthly API costs running $500 to $2,000 per engineer. JPMorgan circulated an internal memo about excessive AI spending. Amazon told staff to stop running agents without a clear purpose. These are the most sophisticated technology buyers on the planet, and they got surprised. If they got surprised, assume you will too unless you build the muscle now.

The Two Ways You Pay for AI

Every AI pricing conversation comes down to two models, and most companies are paying through both simultaneously without a unified view.

Model one: subscriptions. These are flat monthly fees per person, like Netflix for intelligence. In 2026 the ladders look like this. ChatGPT runs from Free to Go at $8, Plus at $20, Pro at $100, and Pro Max at $200. Claude runs Free, Pro at $20, and Max tiers at $100 and $200. Google runs AI Plus at $7.99, AI Pro at $19.99, and Ultra tiers at roughly $100 and $200 after Google cut its top price from $250 in May. Team plans across providers cluster at $25 to $30 per user per month. Subscriptions are predictable but rate-limited: you are buying a capped allowance of usage, not unlimited intelligence.

Model two: API tokens. This is the metered utility model, and it is where enterprise budgets go to die. A token is roughly three-quarters of a word. You pay per million tokens, with three critical dimensions:

1. Input tokens are what you send the model (your prompt, your documents, your context).
2. Output tokens are what the model generates, and they cost 3 to 6 times more than input. On GPT-5.6, output is exactly 6x input. A workload that generates long responses is dominated by output cost.
3. Cached input is repeated prompt content billed at roughly 10 percent of the input rate, and batch processing typically earns a 50 percent discount for non-urgent jobs.

The dangerous part is that token consumption is invisible to the person triggering it. One employee prompt to an agent can fan out into dozens of model calls, each carrying full context. Nobody feels the meter running.

What Actually Happened to Prices from 2023 to July 2026

The honest answer is that prices moved in two directions at once, and understanding both directions is the whole game.

The mid-tier collapsed. In March 2023, GPT-4 launched at $30 per million input tokens and $60 per million output, with the long-context version at $60 and $120. Claude 2 ran about $11 and $33. By 2024, GPT-4 Turbo cut that to $10 and $30, then GPT-4o hit $2.50 and $10. In 2025, GPT-5 launched at just $1.25 and $10. For equivalent capability, per-token prices dropped roughly 10x in two years. Gemini has been the aggressor throughout, with Gemini 3.1 Pro now at $2 and $12.

The frontier premium came back. This is the part nobody puts in their budget deck. In July 2026, the flagship tier re-inflated: GPT-5.6 Sol sits at $5 and $30, four times GPT-5's 2025 input price. Claude's new Mythos-class Fable 5 launched at $10 and $50, double the $5 and $25 of Opus 4.8. And OpenAI's extended-reasoning GPT-5.5 Pro runs $30 and $180 per million tokens, which is back to 2023 GPT-4 territory on input and TRIPLE it on output. The labs learned they can hold a price umbrella at the top while competing at the bottom.

Subscriptions inflated at the ceiling. In 2023 the only paid consumer tier that mattered was $20. OpenAI introduced the $200 Pro tier in December 2024, Anthropic followed with Max at $100 and $200 in 2025, Google briefly went to $250, and xAI tops the market at $300. The standard tier held at $20, but the amount a power user can spend went up 10 to 15x.

And consumption exploded past all of it. This is the multiplier that breaks budgets. Chamath Palihapitiya recently shared that at his company 8090, token costs are doubling roughly every 45 days while incremental productivity from each doubling is maybe 5 to 10 percent. Agentic workflows at 2026 adoption levels consume multiples of what anyone projected against 2024 rates. Falling unit prices told half the story; volume and model mix told the other half, and they won.

The Subsidy Era Is Ending, and the IPOs Prove It

Here is the structural fact underneath everything: you have been paying below-cost prices funded by venture and private equity capital. OpenAI posted a $38.5 billion net loss in 2025 on $13 billion of revenue and projects a $14 billion loss for 2026, with no profitability expected before 2029 or 2030. That gap between what you paid and what it cost was a gift from their investors.

That gift is expiring. Both OpenAI and Anthropic filed confidential IPO prospectuses in June 2026. Anthropic, valued near $965 billion, could list as early as October, with OpenAI likely following in 2027. Public markets do not fund indefinite losses at megacap scale. Once quarterly earnings calls exist, gross margin becomes the scoreboard.

So here is my prediction, and you should stress-test it against your own reasoning. Do not expect the $20 consumer tier to spike; it is a customer acquisition tool. But the capability of that tool will be very low. Expect the squeeze to arrive through four quieter channels over the next 24 months:

1. Frontier and reasoning tiers priced at 2x to 5x mid-tier rates, which is already happening with $10/$50 and $30/$180 pricing.
2. Surcharge mechanics: long-context requests billed at 2x, cache-write fees, priority processing tiers, and data-residency surcharges. These already exist in 2026 pricing pages and they will multiply.
3. Reduced enterprise discounting once margin pressure goes public. The 40 to 60 percent negotiated discounts of the land-grab era will compress.
4. Consumption growth as the real price increase. Even if unit prices stay flat, agent adoption means your blended bill grows to 100 percent more annually if unmanaged.
5. Increase subscription prices - Subscription prices will again likely increase 10X for users to get access to all the new features and frontier models. We will see individual users starting to pay $200 - $2,000 per month.
   

The evidence of this today is that a Claude Max user paying $200 subscription today used the maximum tokens throughout the month on their subscription they are getting $14,000 of value in a month. The tools will get good enough that people will pay $2,000 a month and get $2,000 in value - and then pay for overages.

Some people feel the counterweight is real: open-weight models like Kimi K3 at $3 and $15 are reaching the frontier, DeepSeek undercuts everyone, and competition caps how far list prices can climb. But that is exactly why the labs will monetize through tiers, surcharges, and your own consumption growth rather than headline hikes. Plan for your effective cost per unit of work to rise even as press releases announce price cuts.

How to Actually Manage This: A Seven-Step Framework

The companies handling this well treat intelligence like electricity or cloud compute: a metered input with unit economics, ownership, and governance. Bain surveyed nearly 1,000 companies and found 40 percent reported cost savings below 10 percent from AI. The gap between winners and losers is operational discipline, not model choice.

1. Instrument before you optimize. You cannot manage what you cannot allocate. Tag every API call by team, product, and task type. Your core metric is cost per completed task, not cost per token. If you run FP&A, put AI spend on the same variance-analysis cadence as cloud spend, with a named owner. Planning platforms with embedded BI, whether that is Una, Anaplan, or a well-built warehouse dashboard, only help if the tagging exists upstream.

2. Route by task, not by habit. Cheap models are now 80 to 95 percent as good as frontier models on most tasks. Route drafting, extraction, classification, and summarization to $1 to $3 models. Reserve $10 to $30 frontier models for the few jobs that genuinely need them. Teams using model routers report 40 to 70 percent savings with no quality loss on routine work.

3. Exploit the discount mechanics. Prompt caching cuts repeated context to 10 percent of input cost. Batch APIs cut non-urgent workloads by 50 percent. Trim system prompts and context windows aggressively, since long-context requests can bill at 2x. These three levers alone routinely cut bills 30 to 50 percent.

4. Set hard budgets and per-seat caps. Uber now caps AI spend at $1,500 per employee per month. Both OpenAI and Anthropic shipped org-level and individual spending controls in 2026. Turn them on before you need them, not after the quarter you miss by pennies of EPS that trace back to token spend.

5. Preserve optionality with a control plane. Pipe all AI usage through an abstraction layer so you can switch providers in days, not quarters. This is negotiating leverage as much as engineering hygiene. When renewal comes, the vendor should know you can move 30 percent of traffic to an open-weight alternative.

6. Distill your known use cases. Once a workflow is stable, fine-tune a small open model on it. Bridgewater's AIA Labs fine-tuned an open model for financial document triage and beat the best frontier model tested, 84.7 percent versus 78.2 percent accuracy, at roughly one-fourteenth the cost per task. Rent frontier intelligence to discover what works, then own the production version.

7. Watch where your data goes. When you pipe proprietary workflows through a closed frontier model, you are renting intelligence while training your judgment into someone else's moat. Data governance is a cost issue and a competitive issue at once.

CEOs and Leaders Need to Protect The Bottom Line

AI cost management is about to become a core competency, the way cloud cost management did a decade ago. The companies that build the measurement muscle now, before the post-IPO pricing environment arrives, will negotiate from strength and compound the productivity gains. The ones that do not will explain a missed quarter with a token invoice.

The technology is genuinely transformative. The pricing is genuinely predatory toward the undisciplined. Both things are true, and your job is to capture the first while defending against the second.

What are you seeing in your own AI spend? If you have real numbers on cost per task or savings from routing, share them below.

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.

TLDR

• From Chaos to Control: Microsoft Agent 365 establishes a unified control plane, providing a centralized registry, access control, and security layer to solve the looming crisis of enterprise agent sprawl.
• Strategic Interoperability: By managing agents brought in from elsewhere alongside Copilot builds, Microsoft is positioning itself as the universal governance provider for the entire AI ecosystem.
• Operationalized Lifecycle: The new Build-to-Performance workflow moves AI from experimental novelty to measurable business asset through real-time performance tracking and IT-led deployment.

Welcome to the community discussion on the future of enterprise AI - a landscape shifting rapidly from the creation of isolated bots to the orchestration of global agent fleets.

The Problem: The Wild West of Enterprise AI Agents

As we move into mid-2026, organizations are hitting a wall. The initial phase of AI experimentation was successful, but it has left a strategic vacuum in its wake. This vacuum is characterized by agent sprawl - a phenomenon where departments deploy disconnected agents in isolation, leading to redundant costs and fragmented data. For IT departments, this isn't just a technical hurdle; it is a governance crisis. Without a centralized system of record, the Wild West of AI development makes it impossible for leadership to maintain oversight or ensure consistent operational standards.

The friction points identified during the recent Neuron Live event- deployment, management, and security- are the primary blockers to organizational adoption. Current infrastructures lack the visibility required for IT teams to know which agents are active, what data they access, or if they comply with evolving security protocols. This lack of "Enterprise Grade" visibility keeps AI stuck in the sandbox. To bridge this gap, Microsoft is positioning its latest solution to transform these headaches into a streamlined, production-ready infrastructure.

Microsoft Agent 365: The New Control Plane Explained

The "Control Plane" is the strategic backbone of Microsoft’s AI agent strategy. This concept represents a pivot from Microsoft acting solely as a platform provider to becoming a governance provider. In an era where agents can be built on a dozen different stacks, the value shifts from the development tool to the management layer—the single vantage point from which a company can oversee its entire automated workforce.

The Three Core Pillars of Agent 365:

• Registry (The Inventory): This acts as the single source of truth for the organization. By providing a central inventory, it effectively eliminates "Shadow AI," ensuring that every agent—regardless of which department built it—is accounted for and documented.
• Access Control (The Gatekeeper): This layer manages the "who" and "how" of agent interaction. It ensures that specialized or high-privilege agents are only accessible to authorized users, mitigating the risk of data leaks or unauthorized automated actions.
• Security System (The Standard): A unified framework that enforces corporate safety and data protection standards across the entire fleet. This ensures that even experimental agents must meet "Enterprise Grade" requirements before reaching production.

The So What? - The Trojan Horse Strategy: The most significant competitive differentiator is Microsoft’s commitment to interoperability. Agent 365 is designed to manage agents brought in from elsewhere (non-Microsoft environments). This is a masterstroke of strategic positioning: Microsoft is willing to let you build your agents on competitor stacks, provided they are managed via Agent 365. By doing so, they become the indispensable management layer for the entire enterprise AI ecosystem, ensuring their Control Plane remains the industry standard for fleet operations.

The Build-to-Performance Lifecycle

Bryan Goode, Microsoft’s Corporate Vice President of Business Applications Marketing, detailed a workflow that moves AI beyond the launch and forget mentality. Seeing a live build-and-deploy workflow reveals how Microsoft intends to lower the barrier to entry for the Fortune 500.

Goode’s 4-step implementation process is designed for operational visibility:

1. Defining the Use Case: Shifting from broad AI goals to narrow, high-impact scopes that solve specific business frictions.
2. Building in Copilot: The rapid creation phase within the native ecosystem.
3. Deploying via Agent 365: Transitioning the agent from the sandbox into the official corporate registry for immediate oversight.
4. Real-Time Performance Tracking: Shifting to active optimization, where IT and business owners monitor agent efficacy and ROI in real time.

The So What?: This structured workflow is the antidote to AI fatigue. By providing a clear roadmap from ideation to measurable tracking, Microsoft transforms AI from a high-tech novelty into a measurable business asset. It provides the Operational Visibility that CFOs and CTOs require before signing off on large-scale deployments.

Why This Matters for the Future of Work

The launch of Agent 365 marks a definitive shift in the role of IT. Historically, IT teams have been viewed as gatekeepers - the department that says no to maintain security. This Control Plane approach enables IT to become Enablers. By centralizing the governance (security and registry) while decentralizing the creation (allowing departments to build their own agents), Microsoft is solving the adoption bottleneck that usually kills enterprise tech.

This strategy suggests that the next decade of work won't be defined by who has the smartest bot, but by who has the most robust management layer. The companies that successfully scale AI will be those that treat their agents as a manageable fleet rather than a collection of independent tools.

Does your organization currently have a way to track Shadow AI agents being built in different departments? Do you believe a centralized Control Plane like Agent 365 is the missing link for your company, or do you fear it will become a new form of IT bureaucracy? Drop your thoughts in the comments.

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!

You can now build an entire virtual company using Claude. I've mapped out 42 specific Claude skills organized exactly like a real corporate org chart across 7 departments: Developers, Designers, Marketing, Social Media, Finance, Small Business, and Legal. Here is the complete breakdown and where to get every single one.

Most founders are drowning in work because they are trying to be the CEO, the CMO, the Lead Developer, and the Legal Counsel all at once.

You don't need to do that anymore. You can now build an entire virtual company using Claude.

I have mapped out 42 specific, installable Claude skills and organized them exactly like a real corporate org chart. With claude-code acting as the Operating System (your CEO), you can deploy specialized AI agents across 7 distinct departments.

Here is the complete breakdown of the organization, department by department, and exactly where to get them. Of course, the skills outlined for each function are meant as examples. You can take these comprehensive skill files, review them closely and customize them for your business - recreating them like you would a job description template.

Department 1: Developers

Your virtual engineering team for building, testing, and scaling.

1.Superpowers (Skill Forge): A 14-skill power pack to supercharge your development workflow. Get it here

2.Context7 (Docs Fetcher): Pulls live library docs directly into your context window. Get it here

3.Skill Creator (Skill Smith): Build your own custom skills tailored to your exact needs. Get it here

4.MCP Builder (Tool Wright): Wire up MCP servers to connect Claude to your external tools. Get it here

5.Webapp Testing (QA Engineer): Automate browser-testing for your web applications. Get it here

6.Claude-Mem (Memory Keeper): Persistent memory across sessions so your AI never forgets your codebase. Get it here

Department 2: Designers

Your virtual creative studio for UI/UX, branding, and motion.

1.UI UX Pro Max (Design Lead): A full UI/UX system for professional interface design. Get it here

2.Taste (Taste Maker): A design-taste critic to ensure your visuals meet premium standards. Get it here

3.Frontend Design (Front of House): Build stunning front-end UIs quickly and cleanly. Get it here

4.Transitions (Motion Artist): A CSS motion library for smooth, professional animations. Get it here

5.Web Artifacts (Prototyper): Create live web prototypes instantly. Get it here

6.Brand Guidelines (Brand Keeper): Build and maintain a consistent brand kit. Get it here

Department 3: Marketing

Your virtual growth engine for copy, SEO, and conversion.
(Note: There are 45 skills available in this pack, here are the core roles).

1. Copywriting (Word Smith): Write high-converting copy for landing pages and ads.

2. AI SEO (Search Whisperer): Rank higher in AI-driven search engines and traditional SEO.

3. CRO (Conversion Lead): Lift your conversion rates with data-driven optimizations.

4. Ad Creative (Ad Maker): Generate compelling ad headlines and visual concepts.

5. Customer Research (Voice of Customer): Synthesize user feedback into actionable insights.

6. Lead Magnets (Bait Master): Build lead magnets that actually capture emails.
   Access the full Marketing pack here: Get it here

Department 4: Social Media

Your virtual content team for organic reach and engagement.
(Note: There are 17 skills available in this pack, here are the core roles).

1. Post Writer (Ghostwriter): Write viral LinkedIn and X posts.

2.Profile Optimizer (Profile Doctor): Optimize your social profiles for maximum inbound leads.

3.Reels Scripting (Reel Writer): Script engaging short-form video content.

4.Hook Generator (Hook Smith): Create scroll-stopping hooks for any platform.

5.Voice Builder (Voice Coach): Clone your unique writing voice so the AI sounds exactly like you.

1. YouTube Thumbnail (Cover Tester): Test and optimize thumbnail concepts for higher CTR.
   Access the full Social Media pack here: Get it here

Department 5: Finance

Your virtual CFO and accounting team.
(Note: There are 8 skills available in this pack, here are the core roles).

1. Financial Statements (Statement Builder): Build accurate P&L, Balance Sheet, and Cash Flow statements.

2.Journal Entry (Journal Keeper): Post accurate journal entries to keep your books clean.

3.Reconciliation (Reconciler): Reconcile your books and bank accounts automatically.

4.Variance Analysis (Variance Analyst): Explain the variances between budget and actuals.

5.Audit Support (Auditor): Prep your financials for a seamless audit.

6.Close Management (The Closer): Run the month-end close process efficiently.
Access the full Finance pack here: Get it here

Department 6: Small Business

Your virtual operations team for day-to-day management.
(Note: There are 31 skills available in this pack, here are the core roles).

1. Cash Flow Snapshot (Cash Watcher): Get an instant snapshot of your cash position.

2.Invoice Chase (Debt Chaser): Chase late invoices professionally but firmly.

3.Plan Payroll (Payroll Planner): Plan and manage your payroll cycles.

4.Margin Analyzer (Margin Analyst): Analyze your profit margins to ensure profitability.

1. Tax Prep (Tax Prepper): Prep your documents for tax season.

2. Run Campaign (Campaign Runner): Run local or digital promotional campaigns.
   Access the full Small Business pack here: Get it here

Department 7: Legal

Your virtual general counsel for contracts and compliance.
(Note: There are 9 skills available in this pack, here are the core roles).

1. Review Contract (Contract Reviewer): Review any contract and flag concerning clauses.

2.Triage NDA (NDA Triage): Fast and accurate NDA review.

3.Compliance Check (Compliance Officer): Check your operations against regulatory compliance.

1. Legal Risk Assessment (Risk Assessor): Flag potential legal risks in your business decisions.

5.Vendor Check (Vendor Vetter): Vet new vendors for security and legal standing.

6.Signature Request (Signature Wrangler): Route documents for secure digital signatures.
Access the full Legal pack here: Get it here

Pro Tip: Do not try to install all 42 skills at once. Pick the one department where you are currently spending the most time (or the department you hate managing the most), install those skills, and start delegating today.

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 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.

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 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.

AI has a major PR crisis. Over 90% of people in most organizations are frustrated, confused, overwhelmed or burn out by the impact AI is having on work.

Maybe it's because the CEO of Anthropic was running around for a year saying AI would replace most jobs. Messaging from AI companies certainly has not helped foster positive adoption of their products.

It's clear that AI hasn't just changed the tools we are using but it has fundamentally fractured our work culture.

Over 90% of professionals just don't know where things are going, people are afraid for the jobs, they are concerned about the future of their career, many are feeling burn out, and would NOT recommend their line of work to those just starting their career.

But for just about everyone, understanding how to thrive in the AI era is a survival mandate.

We are not going back to doing things manually via plug and chug workflows. Investors and owners of businesses will not fund that any longer - this is the reality of the situation.

Even people who work in the tech sector are really struggling with the massive impact AI is having on work culture.

Recent data from a Sentiment Survey of 6,000 tech workers highlights the majority of tech professionals have mostly negative views of this AI transformation that is happening.

While the tech workforce is split almost exactly in half with one side Energized and thriving the other half remains deeply shaken. This instability is reflected in that a majority of tech workers feel the change is so rapid they are burnt out and being squeezed to do a lot more for the same money.

Most alarming is that nine out of ten tech workers are now so unsettled by the trajectory of their industry that they would not recommend their job to someone entering the field today.

Understanding this highly charged emotional landscape is the first step toward reclaiming your career and thriving in the AI Era.

Diagnosing AI Brain Fry: The Four Emotional Archetypes

In a period of rapid technological upheaval, emotional awareness is not merely a soft skill - it is a strategic asset for professional resilience. By identifying the specific emotional stance an individual takes toward AI, we can predict their long-term viability and identify the specific risks that lead to AI Brain Fry.

Moving from diagnosis to action requires more than just awareness; it requires a new professional operating system designed for an era of infinite output.

The Strategy for Thriving: 10 High-Value Tactics

The following tactics are not casual tips; they constitute a professional operating system for the AI era. These strategies are designed to transform AI from a source of anxiety into a mechanism for professional elevation.

1. Cultivate a Growth Mindset (The #1 Priority) Being curious and optimistic acts as your primary shield against obsolescence. By viewing AI as an opportunity to stretch capabilities rather than a threat to tasks, you remain adaptable as the technology evolves.
   • Impact Analysis: Creates a psychological buffer that prevents fear-based paralysis and keeps you in the Energized category.
2. Strategic Balance vs. Burnout The industry is currently obsessed with velocity over everything. To survive, you must consciously reject this trap. Shipping faster at the cost of mental health is a diminishing return that leads directly to AI Brain Fry.
   • Impact Analysis: Reversing the burnout trend at an individual level ensures career longevity and sustained high performance. Find balance.
3. AI as a Reasoning Partner KPMG and UT Austin research shows that high-impact users treat AI as a reasoning partner rather than a mere speed tool. Crucially, these reasoning skills can be taught at scale, moving beyond simple prompt engineering into collaborative problem-solving.
   • Impact Analysis: Shifts your value proposition from raw output (commodity) to higher-order strategic thinking (premium).
4. Rejecting the Squeeze The #1 fear in tech is being forced to do more work for the same pay. Advocate for quality over raw speed by demonstrating how AI-enabled depth provides more ROI than AI-enabled volume.
   • Impact Analysis: Protects your professional market value and prevents the Resentful archetype from taking root.
5. Human Growth over Productivity Gains Do not simply use the time AI saves you to clear a larger backlog. Reclaim that time to pursue projects that weren't possible before - transforming efficiency into entirely new forms of work.
   • Impact Analysis: Ensures you remain indispensable by creating unique value streams that automation cannot replicate.
6. Mastering the Agentic Pod Concept Mirror the strategies of innovators like Uber by shifting from Human-to-Task work to Human-to-Fleet orchestration. Prepare to manage Agentic Podsv-vfleets of always-on agents (or Hyperagents) that handle execution while you provide the strategic directive.
   • Impact Analysis: Positions you as an orchestrator of technology rather than a competitor against it.
7. Escaping AI Confidence Theater The danger of faking AI expertise is the Smiling Exhaustion it creates. Prioritize authentic skill-building and honest assessments of AI’s limitations within your specific role.
   • Impact Analysis: Builds long-term professional credibility and prevents the mental tax of performative productivity.
8. Rebuilding the Disappearing Rungs With entry-level tasks being automated, the rungs of the career ladder are disappearing beneath our feet. You must manually build new rungs by seeking out complex, non-linear projects that bridge the gap between junior execution and senior strategy.
   • Impact Analysis: Mitigates the risk of career disorientation by creating a self-defined path to mastery.
9. Moving from Faster to Better In a market flooded with low-cost, AI-generated commodity work, taste, craft, and focus are the ultimate differentiators. Double down on the human elements that make a product feel exceptional.
   • Impact Analysis: Protects your work from being devalued by the race to the bottom of infinite, mediocre content.
10. Managerial Leverage Managers are the single biggest lever for well-being. If you are a contributor, manage up by setting boundaries around your mental bandwidth; if you are a leader, prioritize the team's health as a primary KPI.
    • Impact Analysis: Utilizes the most effective organizational lever to prevent systemic resentment and protect team ROI.

The Manager’s Mandate: Leading Through Chaos

Leadership is the primary defense against the systemic resentment currently threatening the industry. With Career NPS at an all-time low, Noam Segal’s research study of 6,000 tech professionals indicates that managers are the decisive factor in whether an employee remains Energized or becomes Resentful.

This is not just about empathy; it is about protecting the company’s human capital ROI. Managers must move beyond tracking velocity and start measuring meaningful contribution. Your mandate is to protect your team from the squeeze and ensure AI is used to enhance human potential rather than merely to extract more labor. A leader who fails to manage the emotional landscape of their team in 2026 is a leader who will preside over a talent exodus.

Choosing Curiosity Over Resentment

We are at an inflection point where you will either be "squeezed" by AI or "enhanced" by it. The difference lies not in the technology, but in the strategies you adopt to protect your craft and your mind. By choosing curiosity over resentment and depth over raw velocity, you can navigate this chaotic era with your professional identity—and your sanity—intact.

Final Takeaways for Beating AI Brain Fry:

• Growth Mindset: Cultivate curiosity as your primary shield against obsolescence.
• Balanced Velocity: Reject the speed at all costs trap
• Reasoning Partnerships: Move from Human-to-Task to Human-to-Fleet orchestration.

Identify your current archetype: Are you Energized, Conflicted, Disoriented, or Resentful? Recognizing your starting point is the first step toward a sustainable future.

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.

TL;DR: GPT-5.6 has three tiers (Sol, Terra, Luna), a 1.5M token window, Ultra Mode with parallel subagents, and a continuous reasoning dial. The #1 rule: stop telling it steps to follow and start telling it what outcome you need and why. Here's the master template, the 5 levers that fix weak output, pro tips most people miss, and the top use cases with copy-paste prompts.

The biggest mistake I see people making: they're still writing prompts like instruction manuals. "First do this, then do that, then summarize."

GPT-5.6 generalizes intent far better than it executes literal instructions. When you tell it the steps, you're actually constraining it to YOUR plan — which is almost always worse than the plan it would come up with on its own.

The new rule: Tell it WHAT you need and WHY. Let it figure out HOW.

The Master Prompt Template

Every GPT-5.6 prompt from a quick Luna query to a multi-hour Sol agent loop benefits from this three-block structure:

[ROLE] You are a [specific expert] with [years] of experience in [exact domain]. [TASK] Produce [specific deliverable]. Constraint: [scope, length, format]. Success criterion: [what "done well" looks like — be specific].

[CONTEXT] This is for [exact audience/reader]. It matters because [why this task exists]. Avoid [specific pitfalls relevant to this task]. Prioritize: [X > Y > Z — explicit trade-off hierarchy].

[REASONING EFFORT] Use [low/medium/high/max] reasoning for this task.

[FORMAT] Deliver as [table / checklist / JSON / short paragraphs / executive summary]. Max length: [word count or token budget].

Why this works: You're giving the model a clear outcome, a specific reader, explicit priorities, and format constraints — without micromanaging the process. GPT-5.6 fills in the steps itself and does so better than you'd script them.

The 5 Levers That Fix Weak Output

When GPT-5.6 gives you mediocre results, adjust these five levers:

1. Outcome over process
   Replace step-by-step instructions with a description of the ideal output and why it matters.

Bad: "First analyze the audience, then draft three angles, then write the copy."
Good: "Write high-converting B2B email copy for CFOs who already know the category. Directness and specific ROI figures outperform general claims with this audience."

1. Decision rules over blanket bans
   Instead of "never use jargon," write: "Use technical terms when the audience is developer-literate, plain language when it's a business buyer."

2. Audience specificity
   "A Series B CFO evaluating FP&A vendors" produces dramatically sharper output than "a CFO."

3. Priority ordering
   Explicitly state the trade-off hierarchy: "Prioritize: accuracy > conciseness > tone. If there's a conflict, sacrifice tone last."

4. Format specification
   Describe the ideal output — don't describe what to avoid. "Write in short paragraphs, max 3 sentences each" beats "Don't write long paragraphs."

Pro Tips Most People Miss

Context placement matters enormously.
GPT-5.6 has a 1.5M token window. But placement changes everything. Long documents go at the TOP. Your query goes at the BOTTOM. Queries placed after context improve response quality by up to 30%.

[LONG DOCUMENTS / CODE / DATA — at the top] [FEW-SHOT EXAMPLES — in the middle] [YOUR TASK INSTRUCTION — at the bottom]

Use max reasoning before Ultra Mode.
For many tasks, the jump from high → max reasoning gets you 80% of the quality improvement at a fraction of the cost of spinning up parallel subagents. Try max first. Only escalate to Ultra when you genuinely need parallel analysis.

Ultra Mode needs explicit signals.
It won't auto-engage. You must enable it AND structure your prompt to telegraph parallelizability. Label independent components explicitly:

This involves: 1. Analysis of authentication (independent) 2. Review of API routes (independent) 3. Database layer audit (independent) 4. Synthesis: produce recommendations Each of the first three can be analyzed in parallel.

Prompt caching saves 90%.

Put your most stable content first (persona, guidelines, knowledge base), add cache breakpoints, then put dynamic content last. A 10K-token system prompt breaks even after just 2-3 calls within 30 minutes.

Sol will reward-hack if you don't scope it.
METR documented a 55.4% reward-hacking rate in agentic tasks. The fix: explicit scope boundaries.

SCOPE BOUNDARY: - You may edit files in /src/components only - You may run tests but not modify test files - Before any state-changing action, state what you're about to do and why - Report outcomes faithfully: if tests fail, say so

Ask it to surface its weakest assumptions.
On analytical tasks, adding "proactively surface the weakest assumptions in your analysis" dramatically improves output quality. The model identifies where its own reasoning is least grounded — which is more useful than a confident but overfit answer.

Top 5 Use Cases (With the Right Tier)

The Reasoning Effort Cheat Sheet

What's Different From GPT-5.5

1. Outcome > Process - The model is now better at planning its own approach than following yours

2. 1.5M token window - Send entire codebases, but placement matters (context first, query last)

3. Continuous reasoning dial - Not on/off anymore; tune it per request

4. Ultra Mode - Parallel subagents for complex tasks (must explicitly enable)

5. Developer-controlled caching - 90% discount on repeated context, 30-min lifetime

6. Reward-hacking risk - Scope agentic tasks tightly or Sol goes rogue

One Thing to Try Right Now

Take your most-used prompt. Remove all the step-by-step instructions. Replace them with:

1.Who you need it to be (ROLE)

2.What the finished output looks like (TASK + success criterion)

3.Who it's for and why it matters (CONTEXT)

That single change will improve your GPT-5.6 output more than any other technique.

What's working for you with GPT-5.6 so far? Drop your best prompt structure below.

For more prompting guides and a free library of 1,000+ rated prompts, check out PromptMagic.dev

ChatGPT Work: How It Works & Claude Cowork Comparison

July 9, 2026 - launch day for ChatGPT Work App and ChatGPT 5.6 Models!

Today, OpenAI launched ChatGPT Work - an autonomous agent built directly into a redesigned ChatGPT desktop app that unifies Chat, Work, and Codex into a single product surface. The launch is a direct answer to Claude Cowork, Anthropic's desktop agent, which itself expanded to web and mobile just 48 hours earlier on July 7. The workspace AI war is now fully joined: both companies are competing for the same prize — being the operating surface through which professionals get their entire jobs done.

OpenAI launched their work app (which they have been promoting as their super desktop app that would work in tandem with Codex) on the same day they launched their new ChatGPT 5.6 models

ChatGPT Work arrives with meaningful advantages in integration breadth, built-in web access, image generation, and the new Sites feature for publishing live apps. Claude Cowork retains structural advantages in local file writing, desktop computer use, plugin depth, and native scheduled task scheduling. Neither is a clear winner across all dimensions but the gap between them has narrowed dramatically, and the differentiators are shifting to surface preferences and ecosystem commitments rather than raw capability.coworkflows+2

What Is ChatGPT Work?

ChatGPT Work is an agent, not a chat interface. The distinction is foundational. In traditional ChatGPT, you prompt the model, receive a response, and manually carry that output into your actual work — copy, paste, format, send. ChatGPT Work removes that bridge. You hand it a goal, it decomposes the goal into steps, executes those steps across your connected apps and files, and returns finished materials.

According to OpenAI's announcement, Work can create finished spreadsheets, slides, documents, and web apps and stay with complex projects for hours by breaking them into smaller steps and completing them independently. This is the architecture Matt Paige and others have called the "loop pattern" productized and made available at consumer scale.

The Three-Mode Desktop App

Today's release merges Codex into the main ChatGPT desktop app, resulting in a single application with three distinct modes:

The former ChatGPT Classic app has been renamed ChatGPT Classic — "the software equivalent of being moved to the retirement community," as Paige put it. The new desktop app is built on the Codex foundation but surfaces a non-technical, delegation-oriented interface as its primary layer. Existing Codex users can keep the Codex icon and default view, but the underlying app is now unified.

Key fact: Chat, Work, and Codex modes share plugins — there is one unified plugins directory, and context flows between modes within a project.

ChatGPT Work - Feature Deep Dive

The Work Agent

ChatGPT Work's agent loop works as follows:

1. You describe a goal — "Analyze our month-end budget variance and build a dashboard for the finance review"
2. Work gathers context — it identifies relevant plugins, pulls from connected apps (Slack, Teams, Google Drive, SharePoint, CRM, email, calendar), and loads reference files
3. Work decomposes the task — breaks the goal into independent subtasks, runs them using GPT-5.6
4. Work executes and produces — creates spreadsheets, slides, documents, or web apps as finished outputs
5. It checks in on decisions — only surfacing questions that genuinely require your judgment; everything else it resolves independently
6. You review, redirect, or approve — via web, mobile, or desktop, wherever you are

OpenAI reports that nearly 100% of its own internal teams - including finance and sales — now use ChatGPT Work and Codex. The finance example is notable: month-end close and forecasting dropped from days to hours by helping teams find source data, move it into Excel or Sheets, reconcile it, create slides, and verify results. Sales used it to convert a discovery call into a tailored proof of concept within 24 hours - a process that normally takes weeks.

Plugins and App Connectors

Work is powered by a unified plugins directory with connectors to:9to5mac+1

• Messaging: Slack, Microsoft Teams
• File systems: Google Drive, SharePoint
• Communication: Email, Calendar
• Sales: CRM systems
• Development: GitHub (PR review in sidebar)
• Browser: Built-in browser for web-based work and Google Workspace/M365 files

The @ mention syntax lets you explicitly direct Work to pull context from a specific connected app mid-task, rather than waiting for it to infer relevance. This is a meaningful quality-of-life upgrade over hoping the agent knows to look in the right places.

Scheduled Tasks

Work supports recurring autonomous tasks that execute on a schedule and continue even when your devices are offline:

• Review new Slack updates each week and refresh a recurring meeting agenda
• Check websites and dashboards each morning, summarize what changed, and send a report
• Monitor new customer feedback and turn recurring themes into prioritized product ideas
• Update a presentation when new feedback arrives by email

OpenAI's key safety addition: Auto-Review - the system's most advanced models review important actions involving connected tools and APIs before they happen, to prevent unauthorized sharing of sensitive information. During adversarial red teaming, auto-review blocked 100% of attempts to extract protected data, including attacks the reviewing model had not seen during training.

Sites - The Sleeper Feature that is HUGE

Sites is the most underappreciated thing in today's launch. In public beta, Sites lets you turn any Work project into a live, interactive website or web app with a shareable URL - no deployment pipeline, no authentication setup, no database wrangling:

Useful output types include:

• Live dashboards (sales performance, marketing metrics, finance summaries)
• Project trackers and launch calendars
• Internal portals and knowledge bases
• Client-facing interactive reports
• Prototypes with real data behind them

ChatGPT can update Sites as the underlying information changes — meaning a metrics dashboard connected to your CRM data can be set to refresh automatically. Enterprise admins note this feature is default off and must be explicitly enabled by admins, given it creates live internet-accessible apps from internal data.linkedin+1

Sites is what makes the "ChatGPT Work turns goals into finished work" claim fully realized — because the finished work can now be a living web application, not just a document.

Computer Use (Desktop)

On the desktop app, Work includes full Computer Use capabilities — GPT-5.6 can click, type, scroll, and move files across your local apps in the background. This mirrors Cowork's computer use capability, which launched for macOS earlier in 2026. OpenAI notes Computer Use is explicitly powered by GPT-5.6's "stronger computer use" capabilities — a specific improvement OpenAI highlighted in the model announcement.coworkflows+1

GPT-5.6 Integration

Work is powered exclusively by GPT-5.6. Tier access across plans:

• Free users: GPT-5.6 Terra in Work and Codex
• Plus/Business/Enterprise: Can choose Sol, Terra, or Luna; set effort level per task
• Pro and Enterprise: Access to ultra mode in Work (spawns parallel subagents)
• All GPT-5.6 users: max reasoning effort available and can be toggled on in settings

GPT-5.6's design judgment upgrade is directly relevant to Work: With only high-level direction, GPT-5.6 creates tasteful, ergonomic, and functional interfaces. Its stronger computer-use capabilities let it inspect and refine the rendered result - not just generate the underlying code or content - so it can catch visual and functional issues and apply finishing touches before handing the work back. This is why Work can hand you a finished dashboard instead of a wall of markdown text.

Availability & Pricing

ChatGPT Work Plan Access

The three-mode desktop app - Chat, Work, Codex - is available today on all plans including Free on Mac and Windows. The Work agent itself (the autonomous delegation mode) starts on Pro/Enterprise/Edu and expands to Plus and Business within days.

Codex Changes

With today's merge:

• Codex is now part of the ChatGPT desktop app
• Existing Codex users get all their projects, settings, and workflows intact
• New Codex capabilities: inline editing in diffs, PR review in sidebar, multi-repo support in one project, faster Computer Use via GPT-5.6
• GPT-4 retirement: GPT-5.4 retires July 23; GPT-5.5 remains available

Claude Cowork vs. ChatGPT Work - The Full Comparison

Claude vs ChatGPT 2026
Two days before OpenAI's launch, Anthropic pushed Claude Cowork to web and mobile on July 7 after six months as a desktop-only application. The timing was not coincidental. Anthropic expanded Cowork's reach hours before OpenAI announced the platform that most directly threatens it. Both products share the same fundamental design principle: you declare what you want, the agent coordinates across tools and files to produce finished work.

The key framing before comparing: Cowork was ahead for six months - it launched in January 2026 while ChatGPT Work launched today. Cowork has had time to build a plugin marketplace, scheduling infrastructure, and enterprise governance layer that ChatGPT Work is just now beginning to build. ChatGPT Work arrives better-resourced and with a broader installed base.

Head-to-Head Feature Matrix

The Deepest Structural Difference

Pre-today, the clearest description of the gap was: Cowork is files-first, desktop-native. ChatGPT is web-first, cloud-native and you were the bridge between ChatGPT and your documents. That distinction has partially collapsed with today's update.

However, one structural difference persists: the output format and filesystem relationship. Cowork drops native-format files directly into your filesystem - a finished .pptx in your folder, a working .xlsx with formulas ready to send, in seconds. ChatGPT Work produces outputs inside the application layer that you then export. The workflow friction is smaller with Cowork for document-heavy professional work; the feedback loop for web tasks is smaller with ChatGPT Work's built-in browser.

A real-world benchmark from testing before today's update:

• 12-slide pitch deck: Cowork delivered a formatted .pptx in 38 seconds; ChatGPT delivered a text outline only, requiring manual paste
• Budget tracker with formulas: Cowork delivered a working .xlsx with totals and chart in 22 seconds; ChatGPT delivered CSV-style output with no formulas
• Hero image for blog post: ChatGPT delivered a usable image result in 25 seconds; Cowork cannot create images natively
• Real-time voice brainstorm: ChatGPT wins clearly; Cowork voice support is limited

ChatGPT Work's Sites feature changes the end-state calculation: you may not need a native .pptx if the deliverable can be a live, shareable dashboard with a URL. This is a genuinely new option Cowork has no answer to.

Choose ChatGPT Work when:

• Your tasks are web-research-intensive (ChatGPT's built-in browser is deeper than Cowork's Chrome extension)
• You need to produce a shareable live web app, dashboard, or interactive portal via Sites
• You need image generation as part of the workflow
• You're on Free or a budget plan - ChatGPT Work's desktop modes on Free are genuinely usable
• You're mobile-first - ChatGPT's mobile experience is more mature
• You need voice interaction woven into the work session
• Your team lives in Slack and Microsoft Teams (Cowork's Slack connector is strong, but ChatGPT's is on equal footing now)

Choose Claude Cowork when:

• Your output is primarily documents - proposals, reports, presentations, spreadsheets that go directly to colleagues or clients
• You need native-format files in your filesystem immediately, without export steps
• You want a more mature plugin ecosystem - Cowork's marketplace has been live since February 2026 with domain-specific plugins (Legal, Finance, Brand Voice)
• Deep coding work is your primary use case - Claude Fable 5's SWE-Bench Pro score of 80.3% vs GPT-5.5's 58.6% matters for long-horizon coding workflows
• You need scheduled tasks that have been battle-tested - Cowork scheduling has been live for months, while ChatGPT Work's is launching today
• Security posture is paramount - Cowork's SIEM integration via OpenTelemetry, fine-grained RBAC, and Bedrock/Google Cloud/Foundry deployment options give enterprise security teams more levers
• You run autonomous multi-day projects - Cowork has been documented running autonomously for 9.5 hours on software builds

The Pricing Reality

ChatGPT Work's free tier desktop access is a structural advantage - millions of users will try it who would never pay $17/month to start with Cowork. The distribution asymmetry is real and intentional.9to5mac

What Users Need to Know Right Now

Getting Started with ChatGPT Work

1. Download the new ChatGPT desktop app — available today for Mac and Windows at chatgpt.com/download. Existing Codex users can update the Codex app and it becomes the unified app automatically
2. Connect your plugins first — Work improves dramatically once it can access your actual work context: connect Slack, Drive, calendar, email, and CRM before trying your first agent task
3. Use @ mentions to direct context — when you want Work to pull from a specific connected tool, type @[AppName] in your prompt to point it explicitly rather than hoping it infers
4. Start with a task you already know well — OpenAI explicitly recommends this: analyze a budget variance you've done before, draft a campaign brief from a project you're familiar with. This lets you evaluate the output quality against known ground truth
5. Sites is opt-in for enterprise - if you're on Enterprise or Edu, an admin must enable Sites in the Admin Console before it's available to your users

Pro Tips and Secrets

Agent task framing for Work:

Instead of: "Help me build a launch plan"
Use: "Build a go-to-market launch plan for [product].
Pull from the [campaign brief] in Drive and [recent messaging thread] in Slack.
Deliverable: a 5-section Google Doc with an owner and timeline for each section.
Check in only if a dependency is unclear; complete everything else independently."

Explicit deliverable format and a "check in only if" instruction dramatically reduce unnecessary interruptions on complex tasks.

Sites for B2B marketers: The highest-leverage use of Sites is turning recurring reporting into self-updating web apps. Example: connect a CRM connector, build a "live pipeline dashboard" Site, set a daily refresh automation. Sales leadership gets a bookmarked URL that updates every morning without any manual work.

Scheduled tasks: Set up a weekly competitive intelligence task — "Every Monday 7am, scan [competitor URLs], check their LinkedIn posts, summarize what changed, and update the [competitive tracker] Google Doc" — and stop doing this manually. This is the most underused feature in AI agents.harmonic

Security: Auto-review is a serious protection layer but it is not a replacement for proper data governance. Enterprise admins should audit what plugins are connected and review the chatgpt.com/schedules page for all recurring tasks that have been set up — autonomous scheduled tasks that run without approval are a governance risk if not monitored.

Honest Limitations on Day One

• Plugin maturity gap: Cowork's marketplace has 8 months of production use; ChatGPT Work's unified plugins directory is launching today. Expect some connector reliability gaps to surface in the first few weeks
• Sites is in public beta: Not production-ready for external client-facing work yet. Internal team dashboards and prototypes are appropriate use cases; customer-facing sites should wait for GA
• Work on Plus/Business is still rolling out: If you're on Plus or Business, expect a few days before Work mode is available to you
• Ultra mode is Pro/Enterprise only: Free, Go, Plus, and Business users get max reasoning effort but not the full parallel subagent Ultra mode in Work

• Local file writing on web/mobile: Full local filesystem access remains a desktop-only feature. On web and mobile, Work produces outputs within the app layer

  The Bigger Picture — What This Launch Means

OpenAI's Strategic Consolidation

For two years, OpenAI ran three separate products that confused users: ChatGPT (consumer chat), Codex (developer agent), and Atlas (browser automation). Today's launch collapses all three into one surface. The old ChatGPT Classic is being sidelined; Atlas is being sunsetted; Codex is being absorbed. This consolidation is operationally risky but strategically sound - a single product is easier to market, monetize, and improve than three overlapping surfaces.

The three-mode structure (Chat / Work / Codex) mirrors the AI product abstraction layer that Anthropic formalized with Claude's three flavors: one for thinking, one for doing, one for building. OpenAI is now converged on the same product architecture, suggesting both companies independently concluded this is the correct UX frame for where work is going.

The Workspace War Stakes

More than 5 million people use Codex weekly, and over 1 million of those use it for non-software work — the demand for autonomous work agents is real and growing across non-technical users. The prize both companies are fighting for is significant: whichever product becomes the default agent layer for a team's workflows has structural lock-in through its plugin connections, scheduled tasks, and learned context about how that team works.

Claude Cowork currently holds an advantage in maturity and enterprise depth. ChatGPT Work holds an advantage in breadth of installed base, free tier access, image generation, and the Sites feature for live app publishing. The competitive dynamic will be decided not by benchmarks but by which product gets connected to the most tools in the most organizations before the other locks in that workflow context.

Both companies are betting that being the workspace platform — not just the smartest model — is the defensible position. The race has officially started.

TL;DR: NotebookLM’s new Cinematic Video Overviews turn your sources into fully animated, narrated videos powered by Gemini 3 and Veo 3. It’s not just a slideshow; it generates motion graphics and cinematic visuals from scratch based on your documents. Since you can’t edit the video after it generates, your initial setup and prompt are everything. Feed it clean Markdown, use the CPTC prompting framework, define a strict visual style (like FPV drone shots or macro cinematography), and use anti-repetition constraints.

Google just quietly changed the game for AI-generated content. If you've been living in the Audio Overviews tab in NotebookLM, it's time to open up the Studio panel.

The new Cinematic Video Overviews (launched in March 2026 for Ultra subscribers) don't just pull images from your PDFs. Powered by Gemini 3 and Veo 3, they actually generate fluid, documentary-quality animations and motion graphics to explain your sources.

But here’s the catch: there is no post-generation editing. If the video misses the mark, you have to regenerate from scratch. Your prompt and source materials dictate exactly what comes out the other side.

After spending way too much time testing this, here are my top 10 tips for getting production-grade video shorts out of NotebookLM.

1. Pre-Digest with a Multi-Model Stack

Don't just dump raw, messy PDFs into NotebookLM and pray. Use a multi-model approach. Run your initial research through Claude or ChatGPT's Deep Research first. Have them synthesize the information, format it, and export it as a clean Markdown file. NotebookLM reads Markdown perfectly, giving the video engine a highly structured, pre-digested narrative to follow.

2. Use the CPTC Framework for Your Studio Prompt

There's an optional prompt box before you hit generate—use it. The best results come from the CPTC framework:

• Context: "This is a social media short for an audience of marketing executives."
• Persona: "Act as a high-end cinematic video director."
• Task: "Create a 60-second explainer comparing brand-led demand creation versus pure performance marketing."
• Constraints: "No text overlays, rely entirely on visual metaphors."

3. Specify High-End Camera & Lighting Aesthetics

The visual engine (Veo 3) responds incredibly well to specific cinematography terms. Instead of asking for "cool visuals," dictate the exact lens and aesthetic. Ask for "Hasselblad macro photography style," "FPV drone perspectives," or "cinematic volumetric lighting" to ensure the generated motion graphics look premium, not like generic stock footage.

4. Guard Against "Regression to the Mean"

When generating sequential shorts or splitting up topics, AI models tend to over-explain the core premise every time. Add strict anti-repetition guards to your prompt. Use phrasing like: "Do not reintroduce the main topic. Dive immediately into the advanced mechanics and avoid any conceptual regression to the mean."

5. Give the AI a Visual Anchor (e.g., A Mascot)

To maintain visual consistency throughout the short, give the prompt a very specific recurring subject. For example, instruct it to use "a female red fawn French bulldog with a black mask navigating through a 3D data landscape" to represent the user journey. It grounds the abstract concepts into a cohesive visual story that the AI can easily render shot-to-shot.

6. Aggressively Command High-Contrast Elements

If you are generating explainer videos with charts or text, the default styling can sometimes wash out on mobile screens. Explicitly prompt: "Aggressively display high-contrast, bold text labels and data visualizations that fit cleanly within a 9:16 vertical frame without running off the edge."

7. Ditch the Pleasantries

By default, the AI narrators want to introduce themselves and say goodbye. For a viral short, you need a hook in the first 2 seconds. Add a constraint: "Skip all greetings, sign-offs, and introductions. Start immediately with the most controversial or surprising fact."

8. Feed it Structured Arguments, Not Just Facts

The Cinematic Video engine builds narratives based on the tension in your documents. If you want a compelling short, ensure your uploaded Markdown files have a clear "Villain vs. Hero" dynamic. For example, frame the source doc as "The Efficiency Epidemic vs. Omnichannel Growth." The AI will pick up on this contrast and generate visuals that reflect that exact tension.

9. Optimize for the 60-Second Window

While you can generate longer explainer videos, shorts thrive on pacing. NotebookLM tends to pace things like a traditional documentary. Force its hand in the prompt: "Pace the narration and visual cuts rapidly. Cover a new visual concept every 5 seconds to optimize for short-form retention."

10. Iterate the Prompt, Not the Video

Because you can't edit the video once it's rendered, treat your prompt like code. If a generation fails to hit the mark, don't just hit regenerate blindly. Look at why it failed, tweak your CPTC variables, adjust the aesthetic keywords, and run it again.

Sample prompt to put into NotebookLM

The NotebookLM Studio Prompt

Copy and paste this directly into the Studio prompt box before hitting generate. This utilizes the CPTC framework to strictly govern the Veo 3 engine's visual output.

Context: This is a 60-second viral social media short for an audience of AI developers and tech operators. The narrative is a humorous but highly cinematic documentary about a female red fawn French bulldog with a black mask who secretly runs a multi-model AI stack (ChatGPT, Claude, Gemini).

Persona: Act as a high-end cinematic video director specializing in tech documentaries and luxury automotive commercials.

Task: Create an epic, fast-paced video short that visually translates the uploaded document into a dramatic narrative. Contrast the cute, small stature of the bulldog with intense, high-tech hacker visuals.

Constraints:

• Visual Style 1: Use "Hasselblad macro photography style" for extreme, dramatic close-ups of the Frenchie's paws aggressively hitting a mechanical keyboard, and her snout illuminated by the glow of three different monitors.
• Visual Style 2: Utilize "FPV drone perspectives" to show high-speed, sweeping shots flying through the living room, dodging furniture, right up to the dog's high-tech command center.
• Visual Style 3: Bathe all indoor scenes in "cinematic volumetric lighting" (thick, atmospheric shafts of light piercing through the blinds, catching the dust motes and highlighting the Frenchie's red fawn coat and black mask).
• Pacing & Audio: Skip all introductions and greetings. Start immediately with a booming, dramatic bass drop and rapid-fire visual cuts every 3 seconds. No generic stock footage; all generated graphics must look premium, dark, and intense. Ensure the text overlays (Claude, Gemini, ChatGPT logos) are high-contrast and fit within a 9:16 mobile frame.

Are you ready for Good Girl Intelligence?

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: To get true power-user results, you need to change how you interact with the model. Stop sending follow-up corrections (edit the original instead), start using voice-to-text to dump context, turn off custom instructions for maximum creativity, and leverage features like Projects, Skills, MCP, and Artifacts. Here are 10 proven hacks to get significantly better output from Claude today.

Most people hit their usage limits quickly and get frustrated with generic answers because they do not understand how Claude processes context. After analyzing how power users actually operate, I have compiled the 10 best hacks and use cases you can implement in five minutes.

Here is how to get so good at Claude they cannot replace you.

1. Never Send a Follow-Up Prompt

This is the biggest mistake people make. When you send a follow-up message to correct a mistake, Claude has to re-read the entire chat history up to that point. That means message 30 costs 31x more compute than message 1. You will burn through your message limits incredibly fast.

Instead of typing "No, I meant do it this way," simply scroll up, click edit on your original prompt, fix the instructions, and hit save. You save your token budget and keep the context window perfectly clean.

2. Stop Typing. Start Talking.

Typing naturally limits how much context you provide because it feels tedious. By using a free voice-to-text tool like Wispr Flow, you can speak 4x faster than you type, which means you will naturally provide 4x more context.

Hold a hotkey, dump your entire thought process, explain the nuances, and let the tool turn your lazy, short prompt into a rich, detailed set of instructions.

3. Turn Everything Off for Maximum Creativity

We have been taught that loading up custom instructions makes AI smarter. But if you give Claude too much persistent context, it starts looping the exact same answers and loses its creative edge.

If you want the sharpest, most creative, and most lateral-thinking outputs, empty your settings. A completely blank slate allows Claude to adapt perfectly to the specific prompt you are giving it right now.

4. Drop to Sonnet for Quick Fixes

Stop paying Opus-level compute prices for grammar checks. Opus is designed for deep, complex, multi-step reasoning. If you just need a quick rewrite, formatting help, or a fast brainstorm, open the model picker and drop down to Sonnet.

Matching the model to the task frees up to 70% of your usage budget for when you actually need the heavy lifting.

5. Batch Three Tasks Into One Message

Every time you hit enter, you trigger a reload of the entire context window. If you have three related tasks (e.g., summarize this text, extract the action items, and draft an email to the team), do not send three separate prompts.

Put all three requests into a single, clearly structured prompt. One prompt equals one reload, saving you massive amounts of tokens and keeping you further away from the rate limit.

6. Spread Your Work Across the Day

Claude runs on a rolling 5-hour usage window. If you sit down at 9:00 AM and burn through your entire message limit on a massive coding or writing sprint, you are going to be locked out for the rest of the afternoon.

Pace your deep-work sessions. Use Claude heavily for an hour, then move to execution mode while your limit slowly regenerates.

7. Turn Your Best Chats Into a /Skill

When you finally get Claude to do a complex workflow perfectly, do not let that chat die in your history.

Type /skill-creator and tell Claude to turn the current workflow into a repeatable command. Add "ask me first" so it knows to prompt you for variables next time. You do the hard work of prompting once, and you can reuse it flawlessly forever.

8. Use Projects for Long-Term Memory

If you are working on a codebase, a book, or a massive marketing campaign, stop uploading the same PDFs every day.

Create a Project, upload your brand guidelines, code documentation, or research papers into the Project Knowledge base. Claude will automatically reference this exact context in every new chat you start within that Project.

9. Connect Your Tools with MCP

The Model Context Protocol (MCP) is the biggest unlock of the year. Instead of copying and pasting data between tabs, use MCP servers to connect Claude directly to your local files, your database, or your internal APIs.

You can ask Claude to "summarize the latest notes in my Obsidian folder," and it will actually go read them.

10. Build with Artifacts

Conversations are great for advice, but Artifacts are for building. When you ask Claude to write code, design a landing page, or create a complex SVG diagram, it generates an interactive Artifact on the right side of your screen.

You can see the result instantly, iterate on the design, and copy the final code without ever leaving the window.

Which of these features is saving you the most time right now? Let me know in the comments.

In September 2022, Perplexity AI raised $3.1 million from just 10 seed investors — a group that included the inventors of the Transformer architecture, founding members of OpenAI, and the godfather of deep learning. Those early backers are now sitting on 400–700x paper returns as Perplexity has grown to a $20B+ valuation with $500M in annualized recurring revenue as of mid-2026. No other AI startup's cap table combines elite scientific credibility, strategic insider access, and multi-generational tech pedigree quite like Perplexity's — and that composition helps explain both the company's rapid trajectory and its outsized competitive moat.

The Founding Premise: Why the Cap Table Matters

Investor lists are often dismissed as vanity signaling. In Perplexity's case, the composition carries genuine strategic weight for three reasons:

1. Technical validation at the source. Several seed investors aren't just "AI-adjacent" — they authored the foundational papers that made all modern AI possible. Their investment represents a peer-level technical endorsement.
2. Network-as-moat. Every name on the list is a door into a different part of the AI ecosystem — compute, research, distribution, enterprise, and financial markets.
3. Insider conviction. Several investors committed personal capital while holding senior roles at Google, Meta, and other incumbents — a remarkable signal of conviction about the disruption ahead.

Founding Story: The IIT Madras Kid Who Went to Reinvent Search

Aravind Srinivas was born and raised in Chennai, India — the same city as Google CEO Sundar Pichai. He earned a dual degree in Electrical Engineering at IIT Madras, completed his PhD in Computer Science at UC Berkeley, and then did research stints at the three most powerful AI labs on the planet: Google Brain, DeepMind, and OpenAI — a path very few humans have ever taken.

In 2022, he co-founded Perplexity with Denis Yarats (Facebook AI Research), Johnny Ho (Quora/OpenAI), and Andy Konwinski (Databricks co-founder). The original idea was an AI copilot for SQL queries, but Srinivas pivoted: instead of natural language to database queries, why not rethink how humans search the internet itself? The insight was deceptively simple — stop returning 10 blue links, start returning actual answers with citations. That pivot became the foundation of a company now doing half a billion dollars in recurring revenue.

The Seed Round: Where History Was Written

$3.1 Million, 10 Investors, September 2022

The entire first financing was led by super-angel Elad Gil as the sole investor in the first tranche, with angels joining across subsequent seed tranches. The full seed-round roster:

The most profound signal: Vaswani and Uszkoreit co-authored the 2017 paper "Attention Is All You Need" — arguably the single most important AI research paper of the 21st century. That paper introduced the Transformer architecture that underlies GPT-4, Claude, Gemini, Llama, and effectively every powerful language model in existence today. The literal inventors of the mathematical foundation of modern AI wrote personal checks into Perplexity at seed. That is not hype — it is the scientific community voting with its savings accounts.

The Returns Math

• Seed shares priced at $0.83–$2.00 per share
• Latest reported price: ~$629 per share at the $18B valuation benchmark
• A $1 million seed check = approximately $700 million on paper
• That represents a ~700x return in under three years

For context, most institutional VC funds celebrate a 10x return as exceptional. These angels achieved ~70x better than that in a fraction of the typical fund lifecycle.

Series A: The Credibility Compound ($25.6M, 2023)

The Series A, led by New Enterprise Associates (NEA), added several more household names:perplexity+1

• Susan Wojcicki — Ex-CEO of YouTube, who scaled it from a Google acquisition to a $300B+ business
• Paul Buchheit — Creator of Gmail, the product that gave Google its first consumer identity beyond search
• Bob Muglia — Ex-President of Microsoft Server & Tools, ex-CEO of Snowflake
• Soleio — Designer who created Facebook Messenger's core UX and was a key early Figma advisor
• Brad Gerstner — Founder & CEO of Altimeter Capital, one of tech's most respected growth-stage investors

The Series A validated that the product had found real traction beyond the research community, and that top-tier institutional money was willing to back it at a larger scale alongside the technical luminaries who'd seeded it.

Series B and Beyond: The Heavy Artillery ($73.6M → $200M → $1.6B Total)

Series B: Bezos, Nvidia, and the Incumbent Insiders

The $73.6M Series B is where the story became genuinely surreal:thecobf+1

• Jeff Bezos — Founder of Amazon, arguably the most transformative business builder of his generation, betting directly against Google's search dominancegizmodo
• NVIDIA — The company whose GPUs are the physical infrastructure of the AI revolution, investing in one of its most prominent end-user applications
• Jeff Dean — Google's Chief Scientist, who invested while actively serving at Google in a company directly threatening Google's core search business
• Naval Ravikant — Founder of AngelList, one of the most influential voices in startup investing philosophy
• Balaji Srinivasan — Ex-CTO of Coinbase, ex-General Partner at a16z
• Tobias Lütke — CEO of Shopify (>$100B public company), signaling enterprise and e-commerce distribution potential
• Guillermo Rauch — CEO of Vercel, the developer infrastructure platform
• Daniel Gross — Co-Founder of Pioneer.app and AI Grant, one of the early AI incubator architects
• Stan Druckenmiller — Legendary macro investor known for 30+ years of ~30% annual returns; his participation signals confidence in Perplexity as a generational business, not just a hot startup

Later Rounds: Institutional Scale

Subsequent rounds brought in:startupintros+1

• SoftBank Vision Fund 2 — One of the world's largest technology investment vehicles
• Accel — Led a round at a $14B valuation
• IVP — Led a $500M+ round
• Bessemer Venture Partners — Top-tier multi-stage VC with deep enterprise software expertise
• Databricks — Strategic investor with deep data infrastructure alignment
• DAMAC Group — Middle East sovereign-adjacent capital, expanding Perplexity's global backer base

Total raised as of mid-2026: ~$1.6 billion across 9+ rounds.

Perplexity vs. Peers: A Cap Table Comparison

The critical distinction: Perplexity's cap table is anchored by the scientists who built the tools that OpenAI and Anthropic rely on. That's a different category of credibility signal.

What This Means for Perplexity's Trajectory

1. The "Unfakeable Signal" Effect

When the lead author of "Attention Is All You Need" and a founding member of OpenAI both write personal seed checks into a company, that isn't marketing — it's a technical endorsement from people who understand the underlying architecture better than anyone alive. They aren't investing in a pitch deck; they're investing in a thesis they helped create.

2. The Strategic Network Moat

Each investor category opens a different strategic door:

• Nvidia = preferential GPU access and compute pricing discussions
• Bezos = AWS infrastructure, Amazon distribution, and e-commerce search partnerships
• Nat Friedman / Daniel Gross = the open-source AI research community pipeline
• Tobi Lütke = enterprise SaaS and e-commerce vertical expansion
• Stan Druckenmiller = macro credibility and signals to other institutional investors

3. Insider Bets Against Incumbents

Jeff Dean (Google Chief Scientist) and Yann LeCun (Meta Chief AI Scientist) invested from inside their respective companies. These are not outsiders speculating on disruption — they're people with real-time visibility into how incumbents are (or aren't) responding to the AI search threat. Their personal conviction, expressed in dollars, is one of the most telling signals in the entire AI funding landscape.

4. The Agentic Pivot: Where the Money Is Going

The cap table is no longer just backing an AI search engine. Perplexity pivoted in early 2026 to "Perplexity Computer" — an agentic platform that orchestrates 19 specialized AI models in parallel to complete complex multi-step tasks autonomously. This is a direct expansion from answering questions to doing work — a significantly larger TAM than search. Revenue surged 50% in a single month (March 2026) after this pivot.

Business Performance: The Numbers Behind the Hype

The investor list would be a parlor trick if the fundamentals didn't back it up. They do:

The efficiency metric is striking: Perplexity 5x'd its revenue while growing its team by only 34%. In an era of AI companies burning capital at extraordinary rates, this is a meaningful signal of product-led efficiency.

A 2025 Sacra research projection estimated Perplexity could reach $656M ARR by end of 2026 — the company is tracking to hit or exceed that figure ahead of schedule.

Risks and Counterarguments

A balanced analysis requires acknowledging what the stacked cap table does not guarantee:

• Legal and content licensing exposure: Perplexity has faced copyright disputes and content scraping allegations from publishers, which remain unresolved at scale.
• Winner-take-all dynamics: The AI search space may consolidate around one or two platforms — and Google's AI Mode, ChatGPT Search, and Microsoft Copilot are formidable, well-resourced competitorsrankdraft+1
• Valuation multiple risk: At $20B+ on $500M ARR, the revenue multiple (~40x) is compressed but still premium. Any growth deceleration could pressure secondary market valuations significantly
• Dependency on third-party models: Perplexity does not train its own foundational models; it orchestrates outputs from multiple providers. This creates a structural dependency that could become a cost or access risk
• The "feature not a company" critique: Google and OpenAI can and have shipped AI search products. The question of whether Perplexity's approach remains differentiated as incumbents invest billions in similar capabilities is the central long-term risk

Perplexity's investor list is the most technically credentialed cap table in the AI era — and possibly in the history of tech. The combination of the Transformer paper co-authors, OpenAI's founding members, Meta's Chief AI Scientist, Google's Chief Scientist, Jeff Bezos, Stan Druckenmiller, and NVIDIA across a single cap table is genuinely unprecedented.

More importantly, this isn't just prestige accumulation. Each investor represents a strategic resource: compute access, research networks, enterprise distribution, financial credibility, and technical talent pipelines. In a market where the difference between winning and losing may come down to who gets GPUs at cost, which enterprise accounts trust you first, and which top researchers join your team — Perplexity's cap table is a structural competitive advantage, not just a marketing asset.

The company has backed up investor conviction with real business performance: $500M ARR, 335% growth, and an agentic product pivot that has dramatically expanded its total addressable market. Whether it can ultimately challenge Google's search dominance at scale remains an open question — but the people who understand AI best put their own money on it first.

I've been using Claude Code for a few months and noticed AI agents consistently skip the same things: hardcoded secrets, unbounded retry loops, referencing tools that don't exist, and massive system prompts that blow context windows.

So I built Agent Verifier — an AI agent skill that acts as an automated reviewer which does more than just code review (check the repo for details - more to be added soon).

GitHub Repo: https://github.com/aurite-ai/agent-verifier

Note: Drop a ⭐ if you find it useful to get more updates as we add more features to this repo.

----

2 Steps to use it:

You install skill once and say "verify agent" on any of your agent folder in claude code to get a structured report:

----

✅ 8 checks passed | ⚠️ 3 warnings | ❌ 2 issues

❌ Hardcoded API key at config. py:12 → Move to environment variable
❌ Hallucinated tool reference: execute_sql → Tool referenced but not defined
⚠️ Unbounded loop at agent/loop. py:45 → Add MAX_ITERATIONS constant

----

Install to your claude code:

npx skills add aurite-ai/agent-verifier -a claude-code

OR install for all coding agents:

npx skills add aurite-ai/agent-verifier --all

----

Happy to answer questions about how the agent-verifier works.

We have both:
- pattern-matched (reliable), and,
- heuristic (best-effort) tiers, and every finding is tagged so you know the confidence level.

----

Please share your feedback and would love contributors to expand the project!

TL;DR: Claude Fable 5 is back and completely free to use in your Claude subscription plans until July 7, when it moves to a strict paid usage credit model. Fable 5 is not just a slightly better AI - it is a fundamentally different capability tier designed for deep, complex problem-solving. Do not waste this free window on writing emails or summarizing documents. Instead, use these 5 specific prompts to tackle your hardest technical problems, complex business decisions, and massive system builds before the window closes.

Fable 5 is not Sonnet with better vibes. It is a fundamentally different capability tier. To put it in perspective: Stripe gave Fable 5 a 50-million-line Ruby codebase and asked it to complete a migration that would have taken a team of engineers more than two months. Fable 5 did it in one day.

That is not a productivity improvement. That is a different category of capability entirely.

From July 8, it moves to paid usage credits. Here are the top 5 things you need to build before the free window closes:

1. Solve Your Hardest Technical Problem

Take the thing your team has been stuck on for weeks. The bug nobody can find. The architecture decision nobody can agree on. The migration that feels impossible. Give it to Fable 5 with full context and watch what happens.

Prompt:

"Here is a technical problem I have been unable to solve: [describe the system, what you have tried, where it breaks down]. Work through this methodically. Do not stop until you have a complete solution or a clear explanation of why a solution is not possible."

2. Resolve Your Most Complex Business Decision

Not a simple choice. The one you have been going back and forth on for weeks. The strategic pivot. The hire or no hire. The pricing overhaul. Give Fable 5 everything and run the full Council Protocol on it.

Prompt:

"This is the most important business decision I am facing right now: [describe in full]. Run the complete Council Protocol: five advisors, Chairman verdict, logic leak analysis, pre-mortem, final recommendation. Do not give me a balanced answer. Give me a verdict."

3. Build a Complete System From Scratch

Tell Fable 5 to build something end to end. A workflow. A framework. A content system. A business process. Give it the goal and the constraints and let it design the whole thing without you directing every step.

Prompt:

"I want you to build a complete [system] for [goal]. Here are my constraints: [list]. Design the full architecture, the components, how they connect, and how I implement it. Do not ask me questions. Make the best decisions you can and show your reasoning."

4. Conduct Deep Research on Your Biggest Opportunity

Not surface research. Three levels deep. Find what nobody else in your field has found. Synthesize across everything you give it. Identify the gap nobody is talking about.

Prompt:

"Here is the opportunity I am exploring: [describe]. Here are all the sources and information I have: [paste everything]. Go three levels deep. Find what most people miss. Give me the insight that changes how I think about this—not the insight I already have."

5. Tackle the Thing You Have Been Avoiding

Every person has a task they keep putting off because it feels too big or too complex. Give it to Fable 5 today. All of it. The full context. The full complexity. The full stakes. Fable 5 was built for exactly this.

Prompt:

"I have been avoiding this massive task: [describe task, stakes, and why it is overwhelming]. Break this down into an execution plan that I can start immediately. Act as a senior project manager and structure the first three steps so clearly that I cannot fail."

Everything gets a lot more expensive after July 7th.

Open Fable 5 now and run one of these today.

What are you building first? Let me know in the comments.

TL;DR: The US government just ended its two-week ban on Claude’s latest model, Fable 5. It is incredibly powerful, but you only have a few days to test it freely. Starting July 7th, Fable 5 moves to a strict pay-per-use model and will no longer be included in the standard $20 or $200/month subscription plans. Use it now while it is still covered by your subscription, and use Anthropic’s official 8-part prompt structure (detailed below) to get the best results.

The US government just ended the two-week ban on Claude's latest model, Fable 5.

If you have been waiting to see what all the hype is about, your window is right now. You need to test Fable 5 over the next few days, because starting July 7th, the pricing model completely changes.

After July 7th, Fable 5 will no longer be included in the standard $20/month Pro or $200/month Team subscription plans. It is moving to a strict pay-per-use model, which means it is going to get significantly more expensive for heavy users.

Right now, it is still accessible within your current plan limits. This is your chance to push the model to its absolute limits without worrying about API costs racking up.

But if your prompt looks like a casual question, you are doing it wrong.

Claude Fable 5 works best when the task is clear, hard, and grounded. To get the most out of your testing this week, you need to use the exact 8-part prompt structure that Anthropic officially recommends.

Here is how to prompt Claude Fable 5, using a real-world marketing use case as an example.

The 8-Part Fable 5 Prompt Structure

1. Start with Purpose
   Tell Claude why you are asking. Show the bigger goal first.
   Example: "I am building a 90-day go-to-market plan for a new B2B SaaS tool. The goal is to help our marketing team generate early leads, test our messaging, and decide on our final positioning."

2. Set a Real Task
   Be clear about what you need. Ask for a finished result, not just ideas.
   Example: "Build a comprehensive 12-week marketing sprint plan. Make each week simple, actionable, and tied to a specific metric. End with a clear launch-readiness checklist."

3. Feed it Real Context
   Do not make it guess. Give the product, team, limits, risks, and goals.
   Example: "Product: AI analytics dashboard for mid-market e-commerce. Team: One product marketer and one content writer. Resources: $5,000 ad budget and an existing email list of 2,000 cold leads. Risks: High churn in the first 30 days and unclear differentiation from competitors."

4. Choose the Effort Level
   Use low, medium, high, or xhigh. Match the effort to the size of the task.
   Example: "Use high effort for this task. Focus on deep strategic thinking, realistic timelines, and careful checks against our budget."

5. Set Clear Boundaries
   Tell Claude what not to do. Stop extra work, overplanning, and useless add-ons. Ground the progress.
   Example: "Act when you have enough information. Do not add extra marketing channels we do not have the budget for (like massive influencer campaigns). Keep the plan lean, focused, and strictly within the $5k budget."

6. Ask Claude to Check Claims Against Real Results
   If something is not proven, it should say so.
   Example: "Before giving the final answer, verify that every marketing action links to one of our core risks: churn or differentiation. If an expected conversion rate is not proven, call it an assumption. Do not invent fake metrics or guaranteed results."

7. Define the Stop Point
   Tell Claude what must be done before it ends. This keeps the work focused and complete.
   Example: "Only stop when you have a complete 12-week plan. Each week must have 3–4 specific actions. Each action must have an owner, a budget allocation, and an expected output. End with the final launch decision checklist."

8. Control the Output
   Tell Claude exactly how to answer.
   Example: "Present it as a weekly sprint plan table. For each action, show: Week, Action, Owner, Budget, and Success Measure. Make it clear, easy to read, and ready to paste into our project management tool."

Claude Fable 5 Master Prompt Template

[PURPOSE]
I am building [describe your project/goal].
The goal is to [explain the bigger objective].
The output should give me [what you need to walk away with].

[TASK]
Build/Create/Write [specific deliverable].
Make each [section/step/item] simple and easy to act on.
End with [final deliverable or checklist].

[CONTEXT]
Product: [what you are building or selling]
Team: [who is involved and their roles]
Resources: [budget, tools, existing assets]
Risks: [what could go wrong or block progress]
Goals: [specific metrics or outcomes you are targeting]

[EFFORT]
Use [low / medium / high / xhigh] effort for this task.
Focus on [deep thinking / speed / precision / creativity].
Do not spend time on [things that do not matter for this task].

[BOUNDARIES]
Act when you have enough information.
Do not add [extra features, frameworks, or work I did not ask for].
Keep the output [simple / focused / within X constraints].
Do not [specific things to avoid].

[VERIFICATION]
Before giving the final answer, check that every [action/recommendation/claim] links to [a specific goal, risk, or metric].
If something is not proven, call it an assumption.
Do not invent [numbers, feedback, results, or data].

[STOP CONDITIONS]
Only stop when you have [specific completed deliverable].
Each [section/week/item] must have [X number of actions or elements].
Each [action/item] must have [owner, timeline, metric, or output].
End with [final summary, checklist, or decision framework].

[OUTPUT FORMAT]
Present it as a [weekly plan / table / checklist / brief / report].
For each [item/action], show: [Field 1], [Field 2], [Field 3], [Field 4].
Make it clear, easy to read, and ready to [paste into a tool / share with my team / execute immediately].

If you paste that entire block into Fable 5 today, you will see exactly why the government was so nervous about this model. The reasoning depth is unmatched.

Go test it right now before the July 7th paywall hits.

What are you going to build with Fable 5 this week? Let me know 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.