Skip to content
AI Primer
update

Claude Design limits weekly quota to 77% after two tasks, users report

Users report Claude Design consumed 63%-77% of weekly limits after an app and a deck. Fresh export posts also show HTML and JSX handoff into Claude Code, but the Claude look still remains visible.

6 min read
Claude Design limits weekly quota to 77% after two tasks, users report
Claude Design limits weekly quota to 77% after two tasks, users report

TL;DR

You can read Anthropic's launch post, scan the giant Hacker News thread, and even jump straight to the HN comment about exporting a zip into Claude Code. The weirdly useful detail is that the product story is not just "AI makes mockups," it is HTML export, JSX handoff, and design-system import all landing at once. The weirdly limiting detail is that several users burned through quota almost immediately, including ozansihay's screenshot showing 77% usage after an app and a deck.

Research preview

Claude Design is a new Anthropic Labs surface inside Claude. According to shannholmberg's launch summary, it generates wireframes, app designs, slide decks, and one-pagers from plain text, runs on Opus 4.7, and is shipping in research preview.

The launch pitch has two concrete hooks. First, Anthropic's announcement positions it as a design tool built into the chat product instead of a separate canvas app. Second, shannholmberg's launch summary says it can read codebases and design files to build a team design system and apply that style across outputs.

HTML exports

The most interesting feature is not the mockup itself, it is the export path. AIandDesign's first test says Claude Design imported an existing design system and produced a fully interactive HTML prototype in 10 minutes.

shannholmberg's export note adds the full export list: Canva, PDF, PPTX, and HTML, plus a direct handoff into Claude Code. That matches the Hacker News thread, where one commenter described exporting a zip with one HTML file and several JSX files, then using Claude Code to turn the prototype into TSX and server-side TypeScript inside an existing stack.

The workflow emerging from the evidence looks like this:

  1. Import or infer a design system.
  2. Prompt Claude Design for screens, decks, or one-pagers.
  3. Export HTML or a zip project.
  4. Hand the prototype to Claude Code for production cleanup, according to the fresh HN discussion.

The Claude look

The outputs are good enough that people are posting one-shot wins as proof. Lukeedesigner's one-shot mockup claims the prompt was just "hire me 😜," and om_patel5's screenshots frames Claude Design as the difference between a generic dashboard and a polished app in under 15 minutes.

The catch is stylistic sameness. shannholmberg's caveat list says users are already spotting a recognizable "Claude Design look" unless they give very specific direction, and shannholmberg's token follow-up says the best results came from feeding the model brand systems, visual references, and constraints before generation.

That lines up with the skeptical side of the HN thread, where one commenter argued that most users want predictable interfaces rather than surprising ones. The creative upside is speed. The creative risk is converging on a house style fast.

Token burn

Quota pain showed up almost immediately. In ozansihay's quota screenshot, one app design and one presentation consumed 77% of the Claude Design weekly limit, while the shared all-model meter sat at 63%.

AIandDesign's Max-plan complaint reports a similar pattern on the $100 Max plan, saying a single task used 67% of the available allowance. ozansihay's usage-limit screenshot adds another clue: the usage warning says limits are shared with Claude Code.

The complaint is not just price, it is volatility. shannholmberg's caveat list says users reported daily limits disappearing in 30 minutes to two hours, and shannholmberg's token follow-up says even an hour-long live session on Max felt like "walking on eggshells."

Wireframes versus video

The strongest early use cases are conventional design tasks. shannholmberg's Greg Isenberg recap scores wireframing at 9/10, mobile app design at 8.5/10, and deck research and design at 8.7/10.

The weakest one is motion. The same Greg Isenberg scorecard puts video creation at 4.5/10, and shannholmberg's caveat list bluntly says to use something else for video.

That split matters because the demos can look broader than the practical workflow. minchoi's escape-game demo shows Claude Design crossing into simple interactive Three.js territory, but the repeated hands-on reports still center on wireframes, screens, and decks as the reliable outputs.

Designers on control

r/UXDesign

Designing less, deciding more

0 comments

r/UXDesign

I do not care about any of these vibe prompt-to-design tools

0 comments

The most useful outside reaction came from designers who are not posting launch hype. In I do not care about any of these vibe prompt-to-design tools, one UXDesign poster said they will care when canvas-based design can use real components from a real design system, turn into a prototype with little effort, and share cleanly for user testing.

A second UXDesign post, Designing less, deciding more, describes the job shift more clearly: the work is moving from drawing and arranging toward reviewing, filtering, and deciding what survives. That is probably the sharpest summary of Claude Design's first weekend, a tool that compresses execution hard while making judgment more visible.

Further reading

Discussion across the web

Where this story is being discussed, in original context.

On X· 4 threads
TL;DR1 post
The Claude look2 posts
Token burn3 posts
Wireframes versus video1 post