Anthropic launched Claude for Small Business on May 13, 2026, packaging Claude Cowork with 15 ready-to-run agentic workflows, 15 reusable skills, and connectors to QuickBooks, PayPal, HubSpot, Canva, Docusign, Google Workspace, Microsoft 365, and Slack. This is not a new chatbot tier. It is Anthropic’s move to make Claude an operating layer inside the tools small businesses already use. Claude reads, drafts, and waits for approval before sending anything. The article includes a decision tree for choosing your first workflow, a trust-boundary table showing what Claude can and cannot touch, and a practical rollout plan for weeks one through four.

Anthropic launched Claude for Small Business on May 13, 2026, and arrived with the subtlety of a moving truck: Claude Cowork, 15 agentic workflows, 15 reusable skills, and connectors to QuickBooks, PayPal, HubSpot, Canva, Docusign, Google Workspace, Microsoft 365, and Slack.

That’s Anthropic’s move to make Claude an operating layer inside the tools small businesses already use.

Every launch article I read lists the 15 workflows.

But the SMB owners I talk to usually ask a more practical question when they experiment with agentic workflows: Where do I even start?

I suspect they’ll ask the same thing when they hear about this announcement too.

This article gives you a decision tree for picking your first workflow, a trust-boundary table for what Claude can and cannot touch, and a four-week rollout plan that doesn’t require a consultant.

Hey, I’m Karo Zieminski 🤗

AI Product Manager and builder.

I write Product with Attitude, an AI newsletter for thousands of subscribers developing critical AI literacy the only way it sticks: through practice.

We don’t just use AI. We build workflows, automations, and products with it, while studying how AI itself is built, positioned, and woven into our work.

If you’re new here, welcome! Here’s what you might have missed:

→ Build Animated Interactive Websites With Claude Design
→ Claude Cowork Guide for Power Users: 50+ Tested Tips

Learn with us.

What’s Inside

What Claude for Small Business is (not the press-release version). The 15 workflows mapped by category. A decision tree: which workflow to run first based on your actual pain. A trust-boundary table showing what Claude reads, what it writes, and where you must approve. Why Canva and PayPal are not random logos. A 4-week rollout plan you can start this week. And the five FAQ questions every SMB owner will ask.

What Anthropic Launched

Claude for Small Business launched on May 13, 2026.

The official framing is simple: Claude for Small Business packages connectors and agentic workflows to move Claude from “helpful AI assistant” into “the thing running inside your business tools.”

The package has three main components.

Connectors

The launch includes eight named integrations: Intuit QuickBooks, PayPal, HubSpot, Canva, Docusign, Google Workspace, Microsoft 365, and Slack.

Each connector links Claude Cowork to a live data source.

Claude can read, draft, and sometimes act inside these tools, depending on the workflow and the approval settings we choose.

Workflows

Claude for Small Business includes 15 ready-to-run agentic workflows for the tasks small businesses consistently hate: payroll planning, month-end close, invoice chasing, lead triage, contract review, campaign creation, cash-flow monitoring, and business pulse reporting.

They are structured task sequences with defined inputs, actions, and approval points. Very similar to Perplexity workflows.

Skills

The package also includes 15 reusable skills built around repeatable business tasks.

Skills are the reusable capability layer inside Claude Cowork: once configured, they run the same logic every time without making you rebuild the whole thing from scratch.

The whole thing runs through Claude Cowork, which is Anthropic’s agentic workspace product.

If you haven’t set up Claude Cowork yet, read this before anything else in this guide.

What Claude For Small Business Is Not

It’s not a standalone SMB app, not a replacement for QuickBooks, not an autonomous CFO or CMO. Claude doesn't decide things for your business. It reads, drafts, surfaces, and waits. You approve.

According to Anthropic’s own description, users must initiate tasks and approve sensitive actions before Claude sends, posts, or pays. Existing permissions carry through the connectors, so Claude can’t access data we can’t access.

I like that.

The Workflow Map

We’re watching Anthropic build the model that turns Claude Cowork into an SMB operating system, one connector and one workflow at a time.

Finance Workflows

Payroll planning

Claude reads QuickBooks payroll data, surfaces discrepancies, drafts the payment plan for approval. No payroll runs without human sign-off.

Month-end close

Claude pulls transaction data from QuickBooks and PayPal, flags reconciliation items, drafts the close summary. Cuts the accountant-prep time, not the accountant.

Cash-flow view

Claude reads account balances and upcoming obligations, generates a forward-looking cash position. Answers “do I have money for that?” without a spreadsheet session.

Invoice chaser

Claude reads open invoices from QuickBooks, checks payment status against PayPal settlements, drafts follow-up messages. You approve before anything sends.

Margin analyzer

Claude reads revenue and cost data, surfaces margin by product or service line. Most small business owners do not know their actual margins. This workflow changes that.

Tax-season organizer

Claude pulls categorized expenses, flags unusual items, drafts the summary your accountant wants. Lina Ochman, who leads SMB product at Anthropic, described this workflow category as addressing the most time-intensive recurring burden for small business owners.

Sales and marketing workflows

Lead triage

Claude reads HubSpot CRM data, scores and segments leads, and drafts outreach sequences for review.

Campaign analysis

Claude reads HubSpot campaign data, then generates attribution summaries and conversion breakdowns.

Canva asset generation

This workflow deserves a little context.

Canva exceeded $500M in B2B revenue and partnered with Anthropic specifically to build this workflow.

You give Claude the campaign brief. Canva generates fully editable, on-brand assets.

For a solo founder with no design budget, this may be the highest-leverage creative workflow in the bundle.

Content strategist

Claude reads your existing content and business context, then drafts a content calendar and topic recommendations.

Customer pulse

Claude reads HubSpot contact and deal data, surfaces trends in customer activity, flags at-risk accounts.

Ops and Legal Workflows

Contract reviewer

Claude reads documents through the Docusign integration, flags clauses by risk level, and drafts a plain-English summary for the business owner.

Note: This isn’t positioned as legal advice, but as a first-pass filter before the attorney reviews.

Business pulse

Claude pulls data across connected sources, generates a cross-functional business health summary. One of the safest “week one” workflows because it’s read-only and has no write risk.

Weekly commitments

Claude reads task and calendar data from Google Workspace and Microsoft 365, and drafts a prioritized weekly plan. This workflow has the lowest switching cost of any in the package.

Docusign follow-through

Claude tracks document status, chases signatures, surfaces stalled contracts. Anyone who has lost a deal because a contract sat in someone’s inbox for two weeks will understand why this exists.

Where to Start: A Decision Tree

This is the sequencing advice I didn’t see in launch coverage from TechCrunch, Axios, and Fast Company, or anyone else on my reading list.

• If your primary pain is revenue slump: Start with Campaign Analysis and Lead Triage. These are the fastest workflows for understanding what is working in your pipeline and where the drop-off is. Connect HubSpot. Don’t add Canva until you understand the data.

• If your primary pain is cash flow: Start with Invoice Chaser paired with Cash-Flow View. Both are read-heavy with minimal write actions, and both produce immediate visibility into where your money is stuck. Connect QuickBooks and PayPal. Run in approval-required mode.

• If your primary pain is ops chaos: Start with Business Pulse and Weekly Commitments. Business Pulse is read-only across all connected sources. Weekly Commitments is low-risk, low-stakes, and builds the habit of using Claude inside your daily flow.

• If your primary pain is legal bottlenecks: Start with Contract Reviewer and Docusign Follow-Through. Low action risk, high visibility value. Connect Docusign and run contract review on your top three recurring contract types.

• If your data is messy: Don’t connect QuickBooks yet. Messy data doesn’t become clean data when you add AI access. It becomes messy data with an audience. Clean the source first. Business Pulse on reliable data is better than Margin Analyzer on questionable data.

  

The Trust Boundary

Anthropic confirms it doesn’t train on Team and Enterprise customer data by default. This trust model isn’t blind faith in the vendor, but a specific permission architecture you configure and control.

It’s also the most important thing in this article for a small business owner considering deployment. Print it, pin it, share it with your team.

Share

The Product Strategy Behind Anthropic’s SMB Launch

TechCrunch framed this as Anthropic moving downmarket from enterprise. That’s accurate but undersells the product strategy.

Small businesses account for 44% of U.S. GDP and employ nearly half of the U.S. private-sector workforce. That’s not a niche. It’s the backbone of the economy, and it’s been almost entirely absent from the enterprise AI adoption wave.

The real move is distribution. Anthropic is not building QuickBooks 2.0. They are becoming the intelligence layer inside QuickBooks, PayPal, HubSpot, Canva, Docusign, Google Workspace, and Microsoft 365. Eight connectors means eight established distribution channels.

Canva and PayPal are not random logos on a launch slide. Canva has $500M+ in B2B revenue and millions of small business users already inside its product. PayPal processes payments for tens of millions of sellers. Anthropic is showing up inside the software small businesses already use every day.

The training play amplifies this. Anthropic launched AI Fluency for Small Business, a free course built with PayPal, to reduce the learning curve. The Claude SMB Tour adds in-person half-day workshops for 100 local business leaders per stop, with a Claude Max subscription included. That’s a ground-level adoption program.

This connects to a pattern I flagged in my two previous articles (Perplexity for Professional Finance, Context Engineering).

I explained a shift we’re seeing: model providers are increasingly wrapping common use cases into ready-made workflows.

That reduces the burden on users to master prompting or design context-engineering ecosystems themselves.

The 4-Week Rollout Plan For Beginners

This is the sequence I’d run if I was starting from zero today. The goal at week four is to have three workflows you trust enough to run weekly without thinking about them.

• Week 1: Read-only only. Take the free AI Fluency for Small Business course. Connect your first two data sources in Claude Cowork. Run Business Pulse and Cash-Flow View. Let Claude surface what it sees. Don’t approve any write actions yet. This week is about calibration, not automation.

• Week 2: First approval-gated actions. Run Invoice Chaser and Campaign Analysis. Review every draft before approving. You will catch the edge cases: unusual customer relationships, specific invoice terms Claude does not know about, campaign segments that should not receive automated outreach. Document what you override. That override list becomes your future customization.

• Week 3: Canva and Docusign. Add the creative and legal connectors. Run Canva Asset Generation on one campaign brief. Run Contract Reviewer on your three most common contract types. Check the summaries against your own reads.

• Week 4: Decision point. By this week, you have four to six weeks of data on which workflows saved time, which needed heavy editing, and which surfaced genuine insights. That data decides which workflows become recurring rituals and which get paused.

Key Takeaways

The coverage of this launch got the facts right. What it missed is the implementation sequence.

The decision tree and the trust table I shared above are the answers to that question. Bookmark them. Share them. And when you run your first workflow, come back and tell us what you found.

If you found this useful, forward it to SMB owners you know.

Share

FAQ

What is Claude for Small Business?

Claude for Small Business is a package of 15 ready-to-run agentic workflows, 15 reusable skills, and connectors to eight business tools, designed to integrate Claude Cowork into the daily operations of small businesses. It launched on May 13, 2026, and is available through a Claude Team or Enterprise plan.

How is Claude for Small Business different from Claude Team or Enterprise?

Claude Team and Enterprise give you access to Claude for individual and team use. Claude for Small Business layers a specific set of pre-built SMB workflows, skills, and named connector integrations on top of that foundation. It is not a separate product tier. It is a workflow and connector package for SMB use cases.

Which apps does Claude for Small Business connect to?

The named connectors at launch are Intuit QuickBooks, PayPal, HubSpot, Canva, Docusign, Google Workspace, Microsoft 365, and Slack. Each connector runs through Claude Cowork’s permission model.

Can Claude send invoices, post campaigns, or make payments automatically?

No. Per Anthropic’s own documentation, users must initiate tasks and approve sensitive actions before Claude sends, posts, or pays. Claude Cowork’s architecture requires explicit approval before any action with external consequences. This is not a setting you toggle off. It is a design principle of the product.

What should a small business automate first with Claude?

Start with read-only workflows: Business Pulse, Cash-Flow View, or Campaign Analysis. These produce output without any write risk, let you calibrate Claude’s accuracy against your data, and build team comfort with the tool before any approval-gated action workflows are added.

Sources: Anthropic: Introducing Claude for Small Business | Axios: Anthropic wants small businesses to use Claude | TechCrunch: Anthropic courts a new kind of customer | Inc.: Anthropic’s newest Claude feature | Canva/Morningstar: AI campaign creation in Claude for Small Business | Fast Company: Anthropic courts mom-and-pop shops

WHY SUBSCRIBE ・YOUR BENEFITS・ TOOLS I BUILT・CLAUDE HUB・PERPLEXITY HUB ・VIBE CODING HUB

SUBSCRIBE

TL;DR: Twelve tested guides on Claude covering Cowork, Code, Design, Skills, Opus 4.7, and CLAUDE.md. Every prompt is real and every failure is documented. Updated April 2026. Start with Cowork for autonomous workflows, Code for terminal control, and Design for UI from prompts.

What’s Inside

Claude Cowork vs Chat vs Design vs Code
Claude Opus 4.7
Claude Cowork
Claude Design
Claude Skills
Claude Prompts
Claude Code
Claude in Comparisons
Claude in Builder Stories
Cross-Tool Resources That Feature Claude
What Makes This Library Different

Claude Cowork vs Chat vs Design vs Code

Which One Do You Need?

Chat is a conversation. Cowork is a workflow engine. Design is a design partner. Code is a development partner.

That’s the simplest way we can frame the three modes for anyone deciding where to start.

Claude is Anthropic’s AI assistant.

Chat, Cowork, Design and Code are four different ways to use it. Choosing the right mode depends on what you’re trying to accomplish.

• Chat is for questions. Chat handles conversations, artifacts, and quick answers. No file access, no sub-agents, no plugins. It’s the baseline Claude experience.

• Cowork is for workflows. Cowork handles autonomous knowledge work: it plans tasks, spawns parallel sub-agents, reads and writes real files in a sandboxed environment. This is where Claude becomes a working partner, not just a chatbot.

• Design is for interfaces.
  Design turns prompts into editable UI. It generates layouts, components, and design systems, and produces a machine-readable spec that can be handed off to code. It’s built for shaping ideas into visual structure.

• Code is for code. Claude Code is Anthropic’s CLI tool that offers the same agentic power as Cowork with direct filesystem access and project-scoped configuration. It runs in the terminal, reads your codebase, and executes multi-step development tasks.

Claude Opus 4.7

I Mapped the Opus 4.7 Release to Your Role, Goals, and Real Workflows

In this article, I break down the release of Claude Opus 4.7, launched on April 16, 2026, including pricing changes, API breaking updates, benchmark results, and what actually changes for builders, writers, PMs, and vibe coders.

Why Claude Design Only Works Because of Opus 4.7

In this article, I explain why Claude Design works in the first place, and why that comes down to Claude Opus 4.7, whose jump in vision accuracy and self-checking behavior makes reliable UI interpretation possible.

Claude Cowork

Claude Cowork Guide for Power Users: 50+ Tested Tips on Plugins, Skills, Sub-Agents, and Memory

This is the big one. 50+ tested tips covering plugins, skills, sub-agents, memory, and the settings most people never touch. I spent nine days breaking Cowork before writing a single word.

What works, what breaks, and how to make Claude Cowork genuinely useful in 2026.

How I Turned Notion Into Claude’s Persistent Memory, and 10+ Connector Tips Most Guides Skip

In this guide, I walk through how I set up the Cowork-Notion Connector and share 10+ tips most guides skip. Connectors are what turn Cowork from a smart assistant into an integrated workflow engine.

Anthropic Shipped Cowork in 10 Days Using Its Own AI. Here’s Why That Changes Everything.

I introduced Cowork for the first time, broke down the product decisions behind it, and explained what it means for knowledge workers. Anthropic built Cowork using its own AI in 10 days. That kind of acceleration should make product leaders nervous.

Claude Just Unlocked 1 Million Tokens For Everyone. Here Is What That Means.

Claude vs ChatGPT vs Gemini at 1 million tokens. What context windows mean for real workflows, how context rot works, and what this changes if you’re considering a switch.

SUBSCRIBE

Claude Design

Launched in April 2026, it gives you a way to create clean, polished visual assets like website prototypes, slide decks, and marketing one-pagers just by describing what you want.

Claude Design Review: 48-Hour Builder’s Test + Hero Prompts

This article reviews Claude Design based on a 48-hour builder test on Opus 4.7, including production-ready prompts for hero sections, credit management strategies, and a clear breakdown of why it’s a first-draft tool, not a Figma replacement yet.

Claude Skills

What Are Claude Skills and How to Build Them

A step-by-step creation guide, a curated list of community skill repositories, and three ready-to-copy skills I built in under 90 minutes.

Alt Text for the AIO Era

This one is about SEO and AIO, but the Claude Skill inside it is the practical payoff. Google’s AI Overviews now parse alt text as a semantic unit alongside the image. New rules: 125-200 characters, entity-rich, describe purpose not appearance. The post includes a ready-to-copy Skill that generates optimized alt text and filenames automatically.

LinkedIn Teaser Generator Skill

Turns a Substack article into a brand-voice LinkedIn teaser post with a strong hook, a first-comment link, and ready-to-use posting metadata.

Claude Skill: The Context Window Hygiene Skill

This skill works in Claude Code and Claude Cowork, so you can use it both when coding and when managing longer agentic work sessions. It helps you keep an AI agent’s working space clean, focused, and useful.

SUBSCRIBE

Claude Prompts

Stunning Hero Prompts for Claude Design: Recreate the Exact Design

In this article, I share the exact prompts I used to create stunning hero section designs in Claude Design.

n8n AI Agent Builder for Claude Code

How to build production-grade n8n AI agent workflows without manual JSON editing. Includes a prompt that generates fully importable n8n workflow JSON from plain-language descriptions.

Claude Code

How Boris Cherny, Builder of Claude Code, Uses It, And Why That Should Change How You Think About AI

Boris built Claude Code itself. His workflow shows how to use Claude Code as a real development tool, not a toy. Nine practices that separate productive AI-assisted development from prompt-and-pray.

CLAUDE.md and Rules Files

Rules files encode conventions, guardrails, and product context so your AI stops improvising. The Agent Rules Generator prompt outputs platform-specific files for Replit, Cursor, Gemini, and Claude in one session, with build-now vs. build-later splits and plain-language explanations for every rule.

Claude in Comparisons

Perplexity Computer vs Claude Cowork vs OpenClaw

Perplexity Computer orchestrates 19+ frontier models (including Claude Opus 4.6 for reasoning) from a single prompt. The review includes head-to-head comparisons with Claude Cowork and OpenClaw.

Claude in Builder Stories

The Time Claude Said “Don’t” and the Builder Ignored It

A real case study in trusting your product judgment over AI advice. I documented every moment Claude suggested removing features, and Karen Spinner overruled it. Nobody else publishes these stories because they make the AI look fallible. That’s why I did.

Cross-Tool Resources That Feature Claude

The Ultimate Vibecoding Guide

A 16-step roadmap for building production-ready apps with AI, co-authored with Karen Spinner. Claude is one of the primary tools alongside Replit, Cursor, and ChatGPT. Covers mindset, validation, debugging, testing, and cost control.

10 Tools for Running a Bestselling Substack in 2026

Claude Code and Cowork are the backbone of my daily workflow. This post shows how they fit alongside Perplexity, Recraft, and the rest.

Self-Improving Prompt System

A Prompt Builder paired with a Prompt Evaluator that scores against a 35-criteria rubric. Works across ChatGPT, Claude, Gemini, and any LLM that accepts structured instructions.

What Makes This Library Different

Who is this for?

Anyone who uses Claude for real work: writers, PMs, builders, creators, knowledge workers. Whether you picked up Claude yesterday or you’ve been using it since Sonnet 3.5, you'll find a workflow you haven't tried.

How is this different from Anthropic’s documentation?

Anthropic explains what Claude can do. I show what works: the prompts, the failures, the workarounds they left out. I broke three workflows following the official docs before figuring out what was missing. That’s why these guides exist.

How often is this page updated?

Every time I publish a new Claude-related guide, it gets added here. The “Last updated” date at the top reflects the most recent addition. As of March 2026, this library covers 12 original guides across Cowork, Code, Skills, and CLAUDE.md configuration.

I barely finished drafting the Claude Opus 4.7 review before Anthropic introduced Claude Design.

In 48 hours, I test and publish; in the same 48 hours, Anthropic ships a product, then another, and moves on.

From a product strategy perspective, the real story is not the design tool itself, but the stack Anthropic is building around it. Design, code, research, and memory are no longer separate experiences.

Before, if you used Claude to build, you designed somewhere else.

The product workflow looked something like this:

Now, we don’t move from idea to production in stages with handoffs.
We move in one loop, within the same model and context.

Like Lovable and Replit, Anthropic no longer assumes a trained designer is in the loop.

For people who haven’t worked across these stages, this matters. It opens a new entry point into design and building.

This likely contributed to Figma stock dropping 7.28% within four hours of the Claude Design announcement.

What followed was a predictable wave of dramatic “Figma is dead” hot takes.

Today, we’re going to look at what this release means for beginners, the experiments I ran, the prompts I used, and why the “Figma is dead” storyline is a lot less binary than Twitter would like you to believe.

Hey, I’m Karo Zieminski 🤗

AI Product Manager and builder.

I write Product with Attitude, an AI newsletter for thousands of subscribers developing critical AI literacy the only way it sticks: through practice.

We don’t just use AI. We build workflows, automations, and products with it, while studying how AI itself is built, positioned, and woven into our work.

If you’re new here, welcome! Here’s what you might have missed:

• Opus 4.7 Cheat Sheet for AI Learners, Writers, Knowledge Workers, Vibe Coders & System Builders

• Claude Cowork Guide for Power Users

• Anthropic Launches Claude Cowork for Small Business

SUBSCRIBE

What’s Inside

• Why Claude Design only works because of Opus 4.7

• What Claude Design is and who it’s for

• My 48-hour hands-on review (what worked, what didn’t, credit traps)

• Claude Design vs Figma vs Figma Make vs Lovable

• Exact Claude Design prompts for portfolio-worthy hero sections

Part 1:
Why Claude Design Only Works Because of Opus 4.7

I focused only on updates that matter for the Opus + Design combo.
If you want a deeper analysis of Opus 4.7 and how it maps to other roles, goals, and workflows, my previous article is a great place to start.

Claude Design runs on Opus 4.7.

That release is the reason Design works at all.

• In benchmarks, vision jumped from 54.5% to 98.5%.

• It reads 3.75-megapixel images with near-perfect accuracy.

• Coding also got better (SWE-bench Pro: 53.4% → 64.3%), and Opus 4.7 now checks its own work before showing it to you.

A lot like opening a second eye, or realizing the first one was confabulating the entire time.

That means Opus 4.7 can read tiny UI labels, parse dense dashboards, and spot subtle icon differences.

Without that jump, a design tool built on top would hallucinate half of what it sees on your screen.

In a design tool, that means fewer broken screens and less cleanup.

That’s the engine. Now the product.

Part 2:
What Claude Design Is (and Who It's For)

What Claude Design Is

Claude Design is the second product Anthropic launched in that very busy 48-hour window starting April 16.

Claude Design is an AI design workspace where you describe what you want in chat, and Claude turns it into working visuals of all kinds, from slides to 3D visualizations.

This time, the name is refreshingly clear.

Claude Design designs.

I’m only speculating, but we might have Mike Krieger, co-founder of Instagram, to thank for that name. He co-led the project. He also left Figma’s board three days before Claude Design launched.

How to Start Using Claude Design

Claude Design runs on Opus 4.7, which is why we started there.

For now, it’s web-only, so don’t worry if you don’t see it in the desktop app. You can start playing with it at claude.ai/design. As always, I encourage you to do just that and decide if the hype matches the experience.

During onboarding, it reads your codebase and design files, extracts your brand system, and builds it automatically.

Then it applies it to every new project.

You can run multiple brand systems per workspace, so agencies and multi-product teams don’t have to keep re-training the same style from scratch.

What You Can Do With Claude Design

No matter what you do, there’s something on this list you’re either doing by hand or paying another tool to do for you.

If you’re a marketer

Landing pages, campaign assets and microsites, social assets across every format, email templates, banner ads, pitch decks, explainer videos, animated social clips, mood boards, style explorations and your brand system.

If you run a newsletter or blog

Post header illustrations, recurring column branding, subscribe block designs, archive page layouts, referral program pages, anniversary retrospectives, subscriber-only bonus PDFs, social share cards auto-generated per post.

If you’re a PM, designer, or builder

Design systems, token libraries, UI component catalogs. User flows. Onboarding sequences. Web capture of existing site elements. Interactive prototypes with voice, video, shaders, or built-in AI components. 3D prototypes. Mobile mockups in real device frames. Responsive layout variants. Empty states, error states, loading states. Dev handoff as HTML or React.

If you’re an educator

Lecture slides, interactive explainers, essays with custom diagrams, printable handouts.

If you’re an illustrator, or cartoonist

Character sheets, turnarounds, editorial covers, storyboards.

If you sell design assets on Etsy

Sticker packs, planner kits, and digital journal inserts.

If you work with data

Charts, dashboards, editorial charts, animated data videos. The visuals that used to require a designer or a week with D3.

If you work in local government or nonprofits

Public notices, program enrollment pages, event flyers in multiple languages, annual report layouts, volunteer dashboards, and grant application visuals.

And when you’re done, you can export it directly to Canva or as a PDF, PPTX, URL, or HTML.

What You Can’t Do With Claude Design

These are the current limitations. Keep in mind Claude Design is still in preview. And at the pace Anthropic is shipping, parts of this list might be outdated by the time I hit publish.

• You can’t generate photorealistic images directly, by using tools like Nano Banana, Midjourney, or DALL-E.

• No real-time collaboration. You can’t co-edit like in Figma.

• No public share link.

• No voice input. Google Stitch has it, Claude Design doesn’t.

• No infinite canvas. Figma has it, Claude Design doesn’t.

• No backend/database. Design produces the front-end only; Claude Code handles the rest.

• No parallel agents like in Perplexity Computer.

• No real-time consumption meter. At some point, the credits just run out.

• No precise vector control.

Help me spread the word and I’ll make it worth your while.
Share this with 3 friends or colleagues and you’ll get a free month of premium membership.

Share

Part 3:
The 48-Hour Claude Design Review

Things I Appreciated Most

The Claude Code Handoff

The real breakthrough is the combination of codebase awareness and Claude Code handoff.

Claude Design sits next to code. Code sits next to research. All of it sits on top of persistent memory.

Its work ends with a handoff bundle that goes straight to Claude Code.

To put this in context, Figma (even Figma Make) produces a spec handed to engineers.

Claude Design produces a machine-readable spec that Claude Code consumes directly to build the feature.

The Contextual Features

The days of generic, fixed sliders and knobs are over.

Tweaks Panel

Claude generates a custom tweaks panel with controls specific to your design, like a dark mode toggle or a font switcher.

When you select something, the knobs show the controls that matter, like spacing, color, typography.

I kept asking for more controls, and the tool just reshaped itself around my project.

Embedded Sliders & Pickers

Claude embeds sliders and color pickers directly into your prototype. Theme color, accent color, timing values; whatever Claude decided should be adjustable.

For engineers, this is business as usual. Variables in a UI.
For beginners, this is the part where design suddenly feels possible.

Things That Surprised Me

It picks up voice, not just style. After feeding it three Substack links, the copy sounded like me. Close enough to edit rather than rewrite.

Things That Got Under My Skin

Claude Design is token-intensive. Brutally so.

If Claude Design has a meta-skill, it is this: credit discipline.

Because it constantly renders and re-renders complex code behind the scenes, you can burn through a Pro weekly allowance in under 30 minutes of heavy use.

How To Save Credits In Claude Design

• Build the design system first. That way, you avoid rework on every screen.

• Don’t waste tokens on lengthy prompts, use the inline comments instead. Point. Comment.

• It helps to know the limits. It’s not the best tool for highly original, creative work. Don’t waste credits on that.

• During peak weekday hours (roughly 5–11am PT / 8am–2pm ET), your 5-hour session limit drains faster. Outside those hours, you get more room from the same five hours.

Part 4: Claude Design vs Figma

Is Claude Design a Figma Killer?

It’d be easy to call Claude Design a Figma killer, but in my opinion, we’re not there yet, stock move or not.

Some of the reasons are feature related, some are linked to how our brains work.

Design production ≠ Design thinking.

Blurring them produces the worst takes on both sides.

One camp shrugs it off, ignoring how much routine design work is on the line.

The other goes full doomsday, convinced the entire function is about to vanish.

Just as typing isn’t the hardest part of writing, building the first prototype isn’t the hardest part of design.

Design is taste, judgment, attitude, and the ability to build under uncertainty. The first three are personal.
The last relies on real-time collaboration - Figma’s sharpest edge - which is absent in Claude Design right now.

Waiting for AI to finish tasks breaks the creative flow

There's also a cognitive problem I see.

Even a 10–30 second delay is enough for my brain to drift to food, Substack, or any other convenient distraction.

When the AI finally responds, I have to rebuild the mental state I was just in.

That’s why manual manipulation of design still has the edge over prompting: superior tools are not just about output, but about keeping us locked into the work.

Claude Design is very good at accelerating draft creation. Figma is still better at sustained design work. And those are not the same job.

Claude Design vs Figma vs Figma Make vs Lovable

Here's how the four tools compare for a non-designer shipping a first mockup to working code.

Going Beyond Prompting

Similar to Replit and Lovable, Claude Design creates a list of to-dos for each project. It doesn’t ask for approval, which I suspect is the point.

We’re moving beyond prompts and context management.

We can simply adjust the design by chatting with it.

WHY SUBSCRIBE ・YOUR BENEFITS・ TOOLS I BUILT・CLAUDE HUB・PERPLEXITY HUB ・VIBE CODING HUB

Part 5:
Claude Design Prompts

The Exact Prompts I Used For My Projects

Prompt 1:
The “Hey, I’m Karo” Hero: Make Your Name Move

Copy the prompt below and paste it into a new Claude Design session.

To make it your own: Swap text for your name and the hex codes for your brand colors. everything else will re-compose around it.

Read more

While some Cowork Connectors are flaky at best, some are genuinely transformative.

In this article I’m walking you through how I set up my Cowork-Notion Connector to be the latter and share 10+ impactful tips you might not have heard of before.

Table of Contents
What Are Connectors
Top Tips For Combining Connectors
The Three Layer Architecture I Haven't Seen Explained Anywhere Else
Top Tips For Setting Permissions
Notion Connector As A Persistent Memory Layer
My Actual Notion + Cowork Setup
Top Tips For Building Custom Connectors
Top Tips For Running a Connector Health Check

Visit Claude Hub for more Claude-focused deep dives.

Read more

Anthropic shipped Claude Opus 4.7 on April 16, 2026. Same sticker price at $5/$25 per million tokens, but a new tokenizer makes the real cost up to 35% higher on code-heavy prompts. Three API changes can break existing code: thinking.budget_tokens, temperature, and top_p now return 400 errors, and reasoning traces default to hidden. A new xhigh effort tier sits between high and max, Claude Code defaults to it, and mobile push notifications arrived in Claude Code 2.1.110. SWE-bench Verified hit 87.6% in vendor tests, but Terminal-Bench 2.0 regressed versus GPT-5.4 and r/ClaudeAI users report consumer Claude.ai following instructions worse than 4.6. This post translates the marketing claims, the migration guide, and the Reddit rage into what changes for builders, writers, PMs, and vibe coders today.

I see three main problems with the post‑launch flood of newsletters and media on new Anthropic models:

1. It arrives in quantities no human can consume.

2. It’s framed from the model’s point of view (this is the benchmark) not the user’s (this is what that means for me)

3. It’s rarely based on deep testing - mostly on other media coverage.

Today we’re going to tackle #2 and #3.

I’ve already read the official docs, and like when Perplexity Computer first launched, I spent part of last night testing Opus 4.7 myself.

Here’s what this Anthropic model upgrade really means for your work (and mine).

Hey, I’m Karo Zieminski 🤗

AI Product Manager and builder.

I write Product with Attitude, an AI newsletter for thousands of subscribers developing critical AI literacy the only way it sticks: through practice.

We don’t just use AI. We build workflows, automations, and products with it, while studying how AI itself is built, positioned, and woven into our work.

If you’re new here, welcome! Here’s what you might have missed:

• Claude Cowork Guide for Power Users

• I Built a Claude Cowork Loop That Improves Itself

• The Only AI Prompting Guide That Works On Reasoning Models (And Our Cognition)

SUBSCRIBE

What’s Inside

Claude Opus 4.7. What It Means for You
The one-sentence version
Impact on your role, goals, and workflows (the quick version)
Impact on your role, goals, and workflows (the deep‑dive version)
- Learning AI
- Writing
- Building Systems
- Vibe coding
- Writing Scripts and Automations
- Doing Research & Financial Analysis
- Designing
- Prompting
- Using Skill files and Claude.md
Your Interfaces: Surface-by-surface & feature-by-feature impact
Security, privacy, enterprise
Pricing, credits, cost logic
Second-order effects I’ve been thinking about
Final Notes

Claude Opus 4.7. What It Means for You

The one-sentence version

Opus 4.7 is a careful tune-up of Opus 4.6, better at long, agentic work, dramatically better at seeing images, hipped at the same $5/$25 pricing BUT with a new tokenizer that makes the same text cost up to 35% more, and a new default that makes Claude follow instructions more literally than you may want.

Release date: April 16, 2026 (Thursday). Generally available across Claude.ai, API, Bedrock, Vertex, Foundry, Snowflake Cortex, and GitHub Copilot.

Impact on your role, goals, and workflows (the quick version)

Impact on your role, goals, and workflows (the deep‑dive version)

Learning AI

What Changed:

If you’ve been using Claude APIs to learn how it thinks through problems, you’ll notice this right away.

Now, after we prompt, there’s a long pause followed by the answer, with no visible working.

Why:

By default, 4.7 omits the reasoning summary from the response stream.

How to fix:

To fix this type this inside your prompt:

display: "summarized"

Writing

Anthropic’s own migration doc says the model “will not silently generalize an instruction from one item to another, and will not infer requests you didn’t make.”

In practice, the model is more literal now.

• If you’ve been counting on Claude to read between the lines, for example where you hint at tone and let it fill in the rest, the output will feel flatter.

• Your Skill files now do more of the voice‑matching work, so make sure they lean on your taste, not the model’s.

• The upside: archive‑QA flows (“feed it my archive and ask questions”) give fewer confident‑but‑wrong answers.

Read more

This guide is the full architecture, the setup, the Reflection Skill, and the guardrails, written for AI builders who want compounding workflows without a terminal.

By the end, you’ll be running a self-improving loop I built on top of Karpathy’s Auto-Research Pattern, adapted for Cowork.

So even if Claude Code feels intimidating, you’re covered.

Hey, I’m Karo Zieminski 🤗

AI Product Manager and builder.

I write Product with Attitude, an AI newsletter for thousands of subscribers developing critical AI literacy the only way it sticks: through practice.

We don’t just use AI. We build workflows, automations, and products with it, while studying how AI itself is built, positioned, and woven into our work.

If you’re new here, welcome! Here’s what you might have missed:

• Claude Cowork Guide for Power Users

• Claude Design and Interactive Hero Prompts

SUBSCRIBE

What’s Inside

• How to turn Anthropic’s Claude Cowork into a self-improving AI agent

• Step-by-step tutorial from project creation to a running automation loop

• Ready-to-use prompts and a complete Reflection Skill

• An evaluation rubric so you know the loop is improving, not just changing

• Risks, guardrails, and what happens after 20-30 runs.

AI Prompts & Skill Decay: The Problem Self-Improving Loops Fix

A workflow could sit at half its potential for months and we’d never know because we stopped looking.

Every AI workflow decays.

We set up an AI workflow. It works beautifully at first.

Then the world around it changes: files move, naming conventions change, things get re-organized, new edge cases pile up.

The instructions stay frozen. Our needs don’t.

The conventional fix would be to open the prompt or Skill, read through it, edit it, test it again. Rinse, repeat, lose a chunk of our busy week to maintenance.

And it has a blind spot:
we only improve what we've already seen go wrong.

New inputs, new edge cases, new failure modes, those slip through.

A self-improving loop changes that. It makes improvement part of the task, not something you remember to do when things go wrong.

What a Self-Improving Loop Is

A self-improving loop is a recurring task that rewrites its own execution instructions after every run.

Three components have to work together:

1. A context.md file - the evolving brain of the task
2. Folder instructions that tell Claude to read context.md at the start of every run
3. A Self-Improvement Directive inside context.md that tells Claude to update itself when the task finishes.

Without the directive, you don't have a loop. You have a recurring task.

With it, every run reviews what worked, rewrites the rules in-place, and logs the change. The next run starts from a sharper instruction set. Quality compounds.

This is the same pattern Karpathy open-sourced in March 2026 — adapted for Cowork instead of a code repository.

Claude Cowork vs Claude Code: Two Paths To The Same Pattern

Both Claude Code and Cowork support self-improving loops, but the implementation is different.

The Code path wins on depth of the optimization system. The Cowork path wins on accessibility. If “self-improving AI workflow without a terminal” describes what you need, this is the tutorial.

This guide covers the Cowork path exclusively: no terminal, no code repository.

And it requires only three things working together:

The Cowork Self-Improving Loop vs. the Karpathy Loop

This idea isn’t new.

Developers have been building self-improving AI loops in code-heavy tools for months, with Andrej Karpathy’s autoresearch loop going viral.

Karpathy's setup requires a terminal, scripting, and a Git repository. The agent edits training code, runs experiments, scores results, keeps what works.

What I’m proposing achieves the same result in Cowork, via a visual interface and one command. No code, no terminal.

Premium members get the complete playbook:
- the full architecture diagram,
- step-by-step setup
- the Reflection Skill that makes improvement passes surgical,
- my real before/after context.md showing 10 runs of evolution,
- the evaluation rubric that measures whether the loop is working,
- and a guardrail system that prevents instruction drift.

The Full Architecture

Each cycle tightens the Execution Instructions toward our specific workflow. Not a generic template.

After 10+ runs, context.md contains a playbook Claude wrote for itself.

Here is how every piece connects:

Read more

The news about Anthropic unlocking 1 million tokens landed at #1 on Hacker News with over 1,100 points and 485 comments. That’s significant traction.

The context window makes headlines, but the interesting part is what Anthropic did around it: pricing, benchmarks, and the strategic message underneath.

Today we’re going to look at what changed, why it matters, and what it means if you’re choosing between Claude and ChatGPT right now.

Hey, I’m Karo Zieminski 🤗

AI Product Manager and builder.

I write Product with Attitude, an AI newsletter for thousands of subscribers developing critical AI literacy the only way it sticks: through practice.

We don’t just use AI. We build workflows, automations, and products with it, while studying how AI itself is built, positioned, and woven into our work.

If you’re new here, welcome! Here’s what you might have missed:

• Claude Design and Interactive Hero Prompts

• I Built a Claude Cowork Loop That Improves Itself

SUBSCRIBE

What’s Inside

• What Anthropic announced on March 13, 2026

• What tokens are and why context windows matter

• The product strategy behind the pricing change

• What this means for builders and researchers

• Claude vs ChatGPT vs Gemini today

• What still doesn’t work

• Why this matters for critical AI literacy

What Changed On March 13

On March 13, 2026, Anthropic announced that the 1 million token context window is now generally available for Claude Opus 4.6 and Claude Sonnet 4.6.

What Tokens Are

If you’re not a developer, “1 million tokens” can feel abstract, so I want to translate it into something intuitive.

Every AI model has a context window. We can think of it like a whiteboard.

Read more

I’ve seen enough of shallow tutorials that simply rephrase the official docs to know I wanted to do something different.

So I rebuilt some of my workflows from scratch, tracked what failed, measured what saved time, and mapped 56 practical tips into the resource I wish existed when I started.

If you’ve already read the official docs, watched the first-wave YouTube tutorials, and still feel like the gap between “Cowork exists” and “Cowork is genuinely useful” is bigger than people admit, you’re in the right place.

Hey, I’m Karo Zieminski 🤗

AI Product Manager and builder.

I write Product with Attitude, an AI newsletter for thousands of subscribers developing critical AI literacy the only way it sticks: through practice.

We don’t just use AI. We build workflows, automations, and products with it, while studying how AI itself is built, positioned, and woven into our work.

If you’re new here, welcome! Here’s what you might have missed:

• Anthropic Shipped Cowork in 10 Days Using Its Own AI. Here’s Why That Changes Everything.

• I Built a Claude Cowork Loop That Improves Itself. Here’s the Exact Setup.

SUBSCRIBE

What’s inside

This guide covers the basics and the power user tips other Cowork tutorials tend to skip:

• What Cowork is, and where it fits vs Chat and Code

• The setup that matters more than your prompts

• How to delegate properly so Cowork doesn’t improvise your life away

• Pro tips for plugins, skills, and slash commands

• Scheduled tasks and when they’re worth using

• How sub-agents work, and where they break

• Memory workarounds that make Cowork usable across sessions

• Safety, credit management, and the limits that still matter in 2026

What is Cowork

Cowork is Anthropic’s autonomous desktop agent for knowledge work beyond coding.

It uses the same agentic architecture as Claude Code, wrapped in in an interface anyone can navigate.

That means it can plan multi-step tasks, work directly with your files, coordinate sub-agents, generate real deliverables, and now run scheduled tasks too.

Anthropic’s framing is simple: describe an outcome, step away, come back to finished work.

That’s the promise. The question is whether it holds up in real workflows.

Sometimes yes.
Sometimes not.

That’s why this guide exists.

Claude Cowork vs Chat vs Code

The rule is simple:

• Chat for questions.

• Cowork for workflows.

• Code for code.

If I’m asking a quick question, pressure-testing an idea, or editing a paragraph, I stay in Chat.

If I’m building software, debugging, or working directly inside a repo, I go to Claude Code.

If I’m writing, synthesizing research, organizing files, generating documents, or running a multi-step process that touches folders, tools, and output files, Cowork is the right choice.

Everything below is about making it work well.

What Makes Cowork Useful

Three capabilities set it apart from regular chat:

• Delegation. You describe an outcome, step away, and come back to finished work. Formatted documents. Organized files. Synthesized research. Done.

• Scheduled tasks. Scheduled tasks are one of the most useful Claude Cowork features in 2026.

  They let you describe a recurring job once, then have Cowork run it automatically on a schedule, as long as your computer is awake and Claude Desktop stays open (!).

  In practice, this is where Cowork’s delegation capabilities start to shine.

• Connectors. Cowork reaches beyond your local machine into apps you already use. Gmail, Notion, Calendar, Figma. I’ve previously shared some pro tips that don’t get talked about enough.

Put simply, Cowork brings Claude closer to a configurable, real-world agent runtime.

How Cowork Works With Files

Cowork reads file names and the contents.

It knows that an old image named IMG_4521.png is actually a Substack invoice sent via Stripe. It categorizes it correctly without being told.

It can also:

• Find and consolidate duplicates by content, without deleting originals

• Bulk rename files to follow a consistent naming convention

• Archive old files with a log showing what was moved and where

• Sort photos into organized album folders

• Convert between file formats

• Merge scattered CSVs into a single organized Excel file with proper headers

• Clean messy data exports (inconsistent formatting, missing fields, encoding issues)

A common first experiment: decluttering your Downloads folder. We'll cover that below.

Set Up Claude Cowork Like a Power User

Only two things are needed to get started: the Claude Desktop app and a paid plan. Pro at $20/month is a great start.

1. Open Claude Desktop.​

2. Find the mode selector and click the “Cowork” tab.

   

That's it for access. But the real setup happens next.

Before Your First Task

The two most important moves happen before your first task: creating a dedicated work folder and setting your global instructions.

Create a dedicated work folder

• Don’t use your Documents folder or Desktop. Create a dedicated folder for this project instead.

• Grant Claude access to only this folder. That’s your security boundary. Everything outside stays untouched.

• If you’re unsure how to structure the it, ask Cowork:

  I’m about to kick off [Project Name]. 
  Based on this brief/description, scaffold a complete folder structure, with relevant subfolders. 
  If relevant, pre-populate each with templates. 
  Output with a description and overview of how you structured it and why.

• The structure that works best for me:

  • thoughts/ - messy, unstructured thoughts

  • ideas/ - thoughts I want to explore deeper

  • todo/ - files and tasks to process

  • outputs/ - new files Claude creates

  • done/ - files of completed tasks

  • references/ - read-only context, things such as:

    • project’s CLAUDE.md,

    • branding.md,

    • change-log.md

    • memories.md

Set Up Global Instructions

• Global Instructions persist across sessions in Cowork. Use them for evergreen details: tone preferences, preferred tools, output formats.

  This is where you teach Claude how to work with you, not just for you.

• Set them up in Settings inside Cowork:

  

Keep project context files close

Cowork gets smarter when the project explains itself.

A lightweight CLAUDE.md file does a lot of work here.
Same with style docs, brief files, memory notes, and any project-specific instructions you want Claude to read before it starts improvising.

This is not glamorous advice.
It is also some of the highest ROI setup I’ve tested.

How to Delegate to Cowork

Almost no one delegates well the first time. I definitely didn’t.

We either give it instructions vague enough to confuse a barista, or we panic and hand over access to our entire Documents folder like, Sure! Take everything. Raise the child for me.

The Three-Question Framework

The goal is to describe the end state, then give Claude everything it can’t guess.

Before every task, answer these:

• What does "done" look like?

• What context does Claude need?

• What constraints can't it guess?

Cowork works asynchronously. We give it a task, it goes off and works, we come back to the result. So our prompt has to define the end state and fill in everything Claude can't infer.

Instead of this:

Clean up my Downloads folder.

Try this:

End state: My ~/Downloads folder only contains files from the last 7 days. Everything else is sorted into ~/Sorted/photos, ~/Sorted/documents, and ~/Sorted/other.

Context:
There are about 187 files in Downloads right now, going back months
Most are .jpg, .pdf, and .zip

Constraints:
Don't delete anything — only move.

Output: When done, create a short what-moved.md listing how many files went where.

7 More Delegation Tips

• Always ask for a change log.

  A what-changed.md or a change-log.md so you can review every decision Claude made.

• Try delegating with dummy files first.

  Run a quick test with non-critical files before processing the real stuff.
  You’ll learn how Claude interprets your instructions without any risk.

• Keep Claude Desktop open.

  If you close the app, the session ends.

• Ask for source tracing.
  If Cowork is synthesizing across files, make it cite filenames so you can trace where each claim came from.

• Track your token usage.

  Check Settings > Usage so you don’t hit limits mid-task:

  

• Use Cowork Ideas Dashboard.
  With the latest update, you can now use Ideas Dashboard, which provides pre-filled prompts and suggested Connectors for delegating tasks:

  

10 Tested Prompt Templates

Each one follows the same pattern:

Email triage:

Go through emails from the last 7 days. Categorize into: urgent, needs reply, FYI. Create triage.md listing each email with sender, subject, category, and suggested action. Draft replies for anything that only needs a confirmation or acknowledgment — save as drafts, don't send.

Content repurposing:

Take this text and identify the 3 strongest standalone insights. For each, create a script (60 seconds max, conversational tone, optimized for LinkedIn video). Output as video-scripts.md.

Expense tracker:

Read receipt photos in [folder name]. Create expense-tracker.xlsx for personal budgeting: Date, Vendor, Category, Amount. Add formulas for totals by category. Apply conditional formatting for anything over [amount].

Research synthesis:

Read all documents in [folder name]. Create a synthesis-report.docx with: exec summary (1 page), key themes with direct quotes and source file names, contradictions between sources, and unanswered questions. Audience: leadership team. Tone: formal.

Competitor research:

Research pricing pages for [Company A, B, C]. Create comparison.xlsx with columns: tier name, price, features included, limits. Add a tab with pros/cons for each. Audience: product team evaluating options.

Meeting prep:

Organize files in [folder name] into folders by workstream. Create progress.pptx (5 slides max, exec audience). Generate hours.xlsx from time logs. Draft agenda.md for a 10-min standup.

Cowork Skills

If Skills sound familiar, it’s because I’ve been writing about them.

Back when Anthropic first launched them, I wrote a deep dive into Claude Skills: how to create them, stack them, share them, and why Simon Willison called them “maybe a bigger deal than MCP.”

Everything I covered there still applies. But Cowork adds a crucial layer: Skills in Chat were useful. Skills in Cowork are operational. They shape autonomous work.

Your brand guidelines skill doesn't just influence a reply. It governs every file Claude creates. Your writing guidelines skill doesn't just shape a draft. It governs every article Claude writes autonomously.

If you haven’t read the original Skills guide yet, start there for the foundations. Then come back here, because what follows is how Skills compound when they have an agent runtime underneath them.

Built-In Skills

Cowork ships with built-in skills for pdf, docx, pptx, xlsx, and canvas-design. These load automatically when you ask for those file types. No setup required, you can try them right away.

But the real power is in custom skills.

Custom Skills

Custom skills are where Cowork goes from helpful to yours.

The easiest way to create them is through Claude's Skill Creator; a built-in tool that interviews you about what you want, then generates a properly structured skill file you can install and toggle on or off.

You can also build them manually, import community-shared ones from repositories, or copy some of mine.

Here are a few of the skills I use on a weekly basis:

• Alt Text Generator Skill - upload an image, and it returns an SEO and AIO-optimized ALT text for your Substack images, so you don’t have to do it manually.

• Linkedin Teaser Generator For Substack - Turns a Substack article into a brand-voice LinkedIn teaser post with a strong hook, a first-comment link, and ready-to-use posting metadata.

Every workflow you encode as a skill saves re-explanation time
in all future sessions.

Stacking Skills

You can have multiple skills active at once. Claude loads them using progressive disclosure: metadata first (around 100 tokens), full instructions only when needed. So having 15 skills enabled doesn’t flood the context window. Claude pulls in what’s relevant per task and ignores the rest.

This is where things get interesting: skills combine automatically when work crosses domains.

Upload a sales tracker and ask for insights. Your data analysis skill kicks in, processes the numbers, surfaces trends. In the same thread, say “turn this into a deck for leadership.” Now the presentation skill activates, following your slide template. Two skills, one conversation, no manual switching.

Additional Tips

• Chunk your skills instead of building one giant skill that tries to handle everything. I've tested both approaches and the results from one giant skill were much worse.

  For example, I use three separate writing skills instead of one: an overall voice skill, a corporate writing skill, and a newsletter writing skill. Each handles its own context. Claude never confuses who I’m writing for.

• One thing to watch: if you have a lot of skills, they share a context budget that scales at roughly 2% of the context window. In practice, I haven’t hit this ceiling yet. But if Claude starts behaving like it forgot a skill exists, that’s probably why.

Cowork Slash Commands

Skills operate in the background. Slash Commands are quick actions you trigger manually, whenever you need them.

Think of them as workflow shortcuts you call up mid-task.

For example, you might type:

• /summarize to condense a long thread into key takeaways,

• /translate to convert a message into another language, or

• /rewrite to rephrase a paragraph in a different tone.

The beauty of Slash Commands is that they keep you in flow; no switching tools, no context loss. You just type, trigger, and keep moving.

• How Cowork Sub-Agents Work, the shared state problem, and cross-referencing multiple files

• Cowork Plugins, and how to build your own

• Cowork Connectors

• Pro Tips For Saving Credits

• Pro Tips For Building Memory Layer That Works Across Sessions

• What to Watch Out For, and Safety Checklist

How Cowork Sub-Agents Work

Instead of processing your requests one at a time, Cowork can split the work across multiple sub-agents.

In my tests, processing 10 files in parallel instead of one-by-one turned a ~30 minute wait into about 4 minutes.

You even can make this ask explicit when you prompt Cowork:

Use sub-agents to process these 50 transcripts in parallel. Extract themes, then synthesize.

or

Read more

A year ago at Anthropic, it took weeks.

In January 2026, with AI building AI, it takes days.

This is a deep dive into the product decisions and product launch of Claude Cowork.

Hey, I’m Karo Zieminski 🤗

AI Product Manager and builder.

I write Product with Attitude, an AI newsletter for thousands of subscribers developing critical AI literacy the only way it sticks: through practice.

We don’t just use AI. We build workflows, automations, and products with it, while studying how AI itself is built, positioned, and woven into our work.

If you’re new here, welcome! Here’s what you might have missed:

• I Built a Claude Cowork Loop That Improves Itself

• Claude Cowork Guide for Power Users: 50+ Tested Tips on Plugins, Skills, Sub-Agents, and Memory

SUBSCRIBE

SUBSCRIBE 🤗

User Behavior That Started Everything

When users bend a tool into something it was never meant to be, they’re telling you what problem they’re really trying to solve.

• When they use ChatGPT as a therapist → they want a way to think out loud without being judged

• When they use a calendar as a calorie tracker → they want to see the rhythm of eating across a week

• When they use a chair as a clothes drop zone → they want a temporary state between clean and dirty

Boris Cherny, Anthropic engineer, documented the pattern for Claude Code:

Since we launched Claude Code, we saw people using it for all sorts of non-coding work: conducting vacation research, creating slide presentations, organizing emails, cancelling subscriptions, retrieving wedding photos from hard drives, tracking plant growth, and controlling ovens.

Most product teams would see this data and panic.

• That’s off-label use!

• Let’s write a blog post clarifying intended use cases.

• Let’s steer them back to the core value prop.

And while I’m still digesting the oven control use case, Anthropic did something different.

They recognized that users understood their product’s real value better than they did.

Claude Code’s power was never about coding. It was about agency and automation. The ability to execute real tasks on your computer without having to do it manually.

So instead of fighting the behavior, they removed the friction:

• They stripped out the terminal interface.

• They simplified the sandbox setup.

• They gave it a name that doesn’t scream “not for you” to non-developers.

Ten days later, Cowork shipped.

The Mechanics Are Straightforward

You give Claude access to a folder on your computer. You tell it what you want done in plain language. It reads, edits, and creates files in that folder. No terminal. No command line. No coding knowledge required.

• Turn a pile of receipt screenshots into a formatted expense spreadsheet

• Organize a chaotic downloads folder by sorting and intelligently renaming files

• Draft a report from scattered notes across multiple documents

• Create presentations with proper formatting from meeting recordings

Unlike chat interfaces where you get suggestions, Cowork executes. You queue tasks. Claude processes them in parallel. It loops back when it needs clarification.

Anthropic describes the experience as feeling “less like back-and-forth communication and more like leaving messages for a colleague.”

Hence the name.​​​​​​​​​​​​​​​​

If You Still Doubt AI-Assisted Coding

Here’s the part that should make product leaders sit up.

According to reports from Anthropic’s launch livestream, the team built Cowork in approximately a week and a half. Using Claude Code itself.

An AI coding agent built its own non-technical sibling. And it shipped to production. Can we agree that AI-assisted development isn’t theoretical anymore?

We have concrete evidence that:

1. AI coding agents can build production-quality AI agent features

2. Development timelines compress by orders of magnitude when AI builds AI

3. The gap between companies using AI internally and those that don’t is becoming… unbridgeable

Anthropic’s internal research backs this up:

• Engineers there now use Claude in 60% of their work, up from 28% a year ago.

• They report 50% productivity gains, up from 20%.

• The team ships 60-100 internal releases per day for Claude Code.

And most significantly: roughly 90% of Claude Code’s codebase was written by Claude Code itself.

This is what acceleration looks like in 2026.

The Name Is the Strategy

Claude Code’s main flaw was the positioning.

“Code” screams “tech expert only” to anyone who doesn’t see themselves as one. The terminal interface reinforced that signal. The setup complexity confirmed it.

nailed this observation:

Claude Code is a general agent disguised as a developer tool.

What it really needs is a UI that doesn’t involve the terminal and a name that doesn’t scare away non-developers.

Cowork solves that. It says: I’m your colleague, point me at work and I’ll handle it.

The underlying Agent SDK is largely the same, so is the powerful agentic architecture. But the packaging is different.

Good product work isn’t always about building new capabilities. Sometimes it’s about making existing capabilities accessible to people who couldn’t use them before.

The Security Architecture Worth Understanding

I’d be doing you a disservice if I didn’t address the risks.

To their credit, Anthropic is refreshingly honest about them. From their announcement:

You should also be aware of the risk of ‘prompt injections’: attempts by attackers to alter Claude’s plans through content it might encounter on the internet. We’ve built sophisticated defenses against prompt injections, but agent safety is still an active area of development in the industry.

The architecture matters here.

did some reverse engineering and found Anthropic is using Apple’s VZVirtualMachine framework, downloading and booting a custom Linux root filesystem for sandboxing.

That’s serious infrastructure. When you grant folder access, your files mount into a containerized environment. Cowork literally cannot touch anything outside what you’ve explicitly shared. It’s structural isolation.

Still, no one can guarantee perfect safety for agentic systems that execute real actions on your computer. Anthropic deserves credit for saying so directly rather than hiding behind marketing language.

The Product Instinct That Most Teams Lack

Three implications stand out from this launch.

#1: The Bottleneck Moves From Intelligence to Trust.

Cowork’s biggest challenge isn’t whether Claude is smart enough. It’s whether users will grant folder access and trust autonomous execution.

That means that model capability isn’t the limiting factor anymore; workflow integration and user trust are.

#2: Agentic Architecture Beats Retrofitted Capabilities.

Anthropic didn’t build a chatbot and retrofit agent capabilities later.

They built a powerful coding agent first, then abstracted those capabilities for wider audiences.

That technical lineage gives Cowork more robust agentic behavior from day one.

#3: Watching User Behavior Beats Asking User Opinions

Anthropic didn’t run a survey asking “would you like a non-technical version of Claude Code?”

They watched what users were already doing. They saw people bending a coding tool to do non-coding work. Then they built what the behavior demanded.

That’s the difference between companies that ship what the market wants and companies that ship what internal roadmaps say the market should want.

The Competitive Landscape

Cowork is Anthropic’s clearest move yet against the broader productivity AI space.

Claude Code already generates over $500 million in annualized revenue by some estimates. By removing technical barriers, Cowork targets knowledge workers who need automation but lack coding skills. That market is orders of magnitude larger than developers.

One commenter on X called it “AI lock-in for the entire office." Probably accurate.

ChatGPT can’t do what Cowork does. Gemini can’t either. Microsoft Copilot operates in a different paradigm entirely. Anthropic is positioning to own the “autonomous execution on your computer” category before anyone else claims it.

The announcement generated 5 million views on X within 3 hours. That’s not normal product launch engagement. That’s pent-up demand finding an outlet.

What You Should Do Now

• If you want to use Cowork:

  • Claude Max Mac users can try Cowork today (in research preview).

  • Click “Cowork” in the sidebar of the macOS desktop app.

  • Start with something low-stakes: ask it to rename a bunch of messy PDFs in a folder. Feel what autonomous execution actually feels like.

• If you’re building products:

  • Study this launch carefully.

  • Anthropic productized user behaviour. In ten days. Using their own AI to build it. That’s product instinct operating at a speed most teams can’t match.

The Bottom Line

The recursive loop is running. AI systems are building AI systems. Development timelines are compressing from months to weeks to days. The companies that figure this out first will operate at velocity their competitors literally cannot comprehend.

We’re not in the “what if” phase anymore.

We’re in the “what now” phase.

You Might Also Enjoy

My other deep dives into Anthropic and Claude:

• How Boris Cherny, Builder of Claude Code, Uses It

• Claude Skills Are Taking the AI Community by Storm

• n8n AI Agent Builder for Claude Code

• Claude Cowork: What it is, How to Use it by

WHY SUBSCRIBE ・PREMIUM RESOURCES・TOOLS I BUILT・TESTIMONIALS ・CLAUDE HUB ・PERPLEXITY HUB

I’ve been testing Claude Skills myself, and it’s not your usual “neat feature” energy.
It’s the kind of chaotic, 3 a.m., look-what-it-can-do excitement that only happens when something fundamentally shifts.

called it “maybe a bigger deal than MCP.”
said it’s “both an easy path for workable agents and a step forward in what AI can do.”

Today, we’re going to look at:

• What Claude Skills are (and what makes them actually special)

• How to Give Your Claude New Skills

• Build on Top of a Growing Skill Library

• What I built with Claude Skills in <90min

  • Infographics Maker

  • Messy Notes Organizer

  • Substack SEO Internal Linking Strategy

• Using Claude Skills with ChatGPT

• How to Stack Skills

• How to Share Skills

• When to use Skills, and when to stick to MCP or external tools

• The not-so-perfect reality and you need to know

Hey, I’m Karo Zieminski 🤗

AI Product Manager and builder.

I write Product with Attitude, an AI newsletter for thousands of subscribers developing critical AI literacy the only way it sticks: through practice.

We don’t just use AI. We build workflows, automations, and products with it, while studying how AI itself is built, positioned, and woven into our work.

If you’re new here, welcome! Here’s what you might have missed:

SUBSCRIBE

What Are Claude Skills And Why Are They Special

Skills, like most great inventions, are deceptively simple. They’re just a set of instructions you teach Claude to follow.

• The old Claude couldn’t fetch YouTube transcripts ➜ the new one can (if you give him the skill).

• The old Claude couldn’t keep every visual on brand ➜ the new one can (if you give him the skill).

And that part - the giving Claude the skill part - is the real shift. Anthropic made skill-building something anyone can do. No API keys. No SDKs. Just Markdown and curiosity.

You can teach Claude without any code.
(It even rhymes! I didn’t plan it. Probably.)

The tech behind Skills isn’t new. Tools like Manus AI have been doing text extraction and on-brand visuals for a while.
What’s new is how accessible it is.

Before Skills, you had three options:

• Option 1 — MCP servers: complex setup, infrastructure overhead, token management, mostly aimed at engineers.

• Option 2 — Custom tools: build API integrations, maintain auth flows, debug constantly — the cognitive equivalent of bringing a moving truck to buy groceries.

• Option 3 — Advanced context engineering & system prompts: powerful but brittle, and not for everyone (or every occasion).

With skills you have a folder with some markdown and maybe a script. That’s it.

How To Give Your Claude New Skills

• Enable Skill Creator
  Go to Settings → Skills → Skill Creator → Enable.

• Describe your workflow in plain English

  Build a skill that saves my blog posts in Notion.

• Answer Claude’s follow-ups.
  It will ask about inputs, outputs, edge cases, and constraints.

• Review the generated files.

  You’ll get SKILL.md (+ optional resources/scripts). The files may look intimidating at first, but it’s easier than it seems:

  • SKILL.md → the brain: where understanding lives.

  • /resources → the study notes: cheat sheets, and examples

  • /scripts → the muscle memory: what turns knowledge into action.

• Download the ZIP file and go to Settings → Skills → Upload. Toggle it on.

• Test in a new chat. Prompt naturally to see if Claude can recall the skill.

Build on Top of a Growing Skill Library

You don’t have to start from scratch, the Claude community is already doing the heavy lifting. Developers are curating public GitHub repositories packed with Skills for every niche imaginable: text cleaning, automation, design, analysis, and more.

Here are a few of the best places to start:

• anthropics/skills
  Official examples from Anthropic (great for studying structure and naming conventions).

• BehiSecc/awesome-claude-skills
  Community-curated collection of practical and experimental Skills.

  • docx - Create, edit, analyze Word docs with tracked changes, comments, formatting.

  • pdf - Extract text, tables, metadata, merge & annotate PDFs.

  • pptx - Read, generate, and adjust slides, layouts, templates.

  • xlsx - Spreadsheet manipulation: formulas, charts, data transformations.

  • markdown - Parse, generate, and format Markdown documents.

• michalparkola/tapestry-skills-for-claude-code
  A creative repo focused on Claude Code workflows and integrations.

• PleasePrompto/notebooklm-skill

  Connect Claude Code to your NotebookLM.

• adrianpuiu/claude-skills-marketplace

  Turn Claude into a professional Project Architect.

• awesome-claude-skills-gist

  👉 A list of all Skills and repos I know of (approx. 120 skills!)

Companies are building too. Rakuten automated their management accounting. “What once took a day, we can now accomplish in an hour,” said their AI general manager. Real company. Real savings. Not a demo.

If you’d rather skip the browsing, feel free to copy the Skills I built 👇

What I built with Claude Skills in <90min

Read more