4.5 ⏱ If there's time
Info
⏱ Optional block · Duration: ~10-15 min · 🎯 Objective: know Claude Design’s real limits (beta) and how to work around them, so nothing trips you up on demo day in front of the committee.
Claude Design is in beta: powerful, but with known rough edges. Anthropic documents them officially. Know them ahead of time and none will catch you off guard —each has a simple workaround.
The 5 known limitations (and their workaround)
| Limitation | What happens | How you work around it |
|---|---|---|
| Comments that don’t appear | Inline comments occasionally don’t show up on the canvas. | Open them in the comments view; if they’re still not picked up, paste the feedback directly into the chat. |
| Large repos | A huge codebase loaded in the browser causes lag or issues. | Link it from Claude Code instead of uploading the whole thing, to avoid the lag. |
| “Chat upstream error” | A chat error cuts off the conversation. | Start a new chat tab within the same project and continue. |
| Multi-person editing | Two or more people editing the same project at once is still basic and may not work reliably. | Take turns: one person edits at a time; the others comment. |
| Design-system garbage-in | Import is only as good as its source: a messy codebase or incomplete file shows up in the output. | Import a clean, complete design system; what goes in dirty comes out dirty. |
Note on usage history
Info
Claude Design used to have its own weekly allowance, separate from everything else. Not anymore: all Design activity counts toward your plan’s shared limit (Chat, Claude Code, Cowork). If last week you were tracking a separate “Design allowance,” that counter is gone —it’s a single pool now.
✅ Checkpoint
- You identified at least one known limit and its workaround before your demo.
- You know Design no longer has its own quota: it consumes the plan’s shared limit.
Claude Advanced Workshop · Grupo Salinas · v1.0 · 2026