Edition 348 | April 21, 2026 The Dyslexic AI Newsletter by LM Lab AI

Reading Time: 7 minutes Listening Time: 10 minutes

Happy Tuesday.

In Edition 347, I told you I was going to come back with a real experiment. Give Claude Design a proper brief. Build a real Cognitive Partner OS mockup. Share what happened honestly.

Here is what actually happened.

I gave it a very long, very specific prompt to recreate something I had already built in another project. I wanted to see how it would handle a real brief, not a throwaway one. And I wanted to compare its output to what I have been getting from other vibe coded tools.

Then I ran out of credits.

It did not even finish what I asked it to do.

But what it created before it stopped was enough to tell me something important.

First, the limits.

This was not a clean, isolated experiment. The prompt I used had a head start. Because I was asking Claude Design to recreate something I have already iterated on heavily in another vibe coding tool. So it was working with a clear, mature, well-tested idea. Not starting from scratch.

That is relevant. Because part of why the output was as good as it was, I think, is that the brief was refined. Multiple versions of this project already exist. The requirements are clean. The goals are clear.

A great prompt, built from months of iteration, is going to get a better result from any tool than a quick ad-hoc ask would. That is not news. But it is worth naming here, because I do not want to tell you "Claude Design is amazing" without also telling you what I gave it to work with.

Second, the credits.

I burned through my Claude credits faster than I expected, and the system stopped the build mid-project. I will not have more credits to keep testing until next week. So this edition is built on partial output, not a finished deliverable.

That said, partial output was enough.

What Claude Design produced before I hit the credit wall was, frankly, some of the best visual output I have seen from any vibe coded tool.

And I have tried a lot of them. Edition 346 walked through the six builders I have been evaluating for the Cognitive Partner OS: Claude Code, Cursor, Codex, Google AI Studio, Bolt.new, Lovable. Each one has strengths. Each one has a look and feel.

Claude Design is different. And not just in a "they all look slightly different" way. In a noticeable, has-its-own-identity way.

It has an aesthetic. A real one.

I noticed the color choices immediately. Softer tones. Pastel accents. Light, airy backgrounds. The kind of palette that feels like it came out of the same visual design language as Claude's own interface and marketing. There is a distinct Claude look.

Fonts leaned cleaner and more readable than what I usually get from Claude Code directly. Proportions felt considered. Hierarchy was present without me having to fight for it.

It looked like a designer had been in the room.

That is a big deal for someone like me. I do not want to become a designer. I want to ship products that do not embarrass me visually. And for ten minutes of work with a detailed prompt, what I got was already ahead of what most dyslexic founders I know can produce with traditional tools in an afternoon.

Let me dwell on this for a second because I think it matters.

Most vibe coding tools are neutral about visual style. They generate whatever you describe. If you do not describe it well, you get something generic. If you describe it carefully, you get something reasonable.

Claude Design seems to have a default taste.

Not overbearing. Not locking you into one look. But a baseline that tends toward calm, clean, legible, softer. Claude's own aesthetic, applied to whatever you are building.

I mentioned in Edition 347 that Claude Opus 4.7 (the model behind Claude Design) has developed something close to design judgment. Anthropic's own launch quotes talked about it making choices "I would actually ship."

After using it with a real brief, I believe it.

This does not mean every project should look like Claude. It means that the tool has a center of gravity. And for someone like me, who struggles to articulate visual preferences in precise design language, having a tool with its own tasteful default is genuinely useful.

I can start from its aesthetic and push outward, rather than starting from blank and trying to describe what "good" means.

That is a different kind of collaboration. And it fits the Cognitive Balance Model I wrote about in Edition 332 in an interesting way. The tool is contributing more than execution. It is contributing taste. I am contributing direction, context, and judgment about fit. We are building something together that neither of us would have produced alone.

Going back to the builder evaluation from Edition 346, this experiment gave me a clearer picture of where Claude Design fits.

It is not replacing Claude Code for me. Claude Code stays the backbone for complex logic, long-running builds, and iterative development.

It is not replacing Bolt.new either. Bolt is where most of my current websites live, and it has its own strengths for fast site builds.

Claude Design is the visual and prototyping layer sitting on top. The place I go when:

And because it hands off to Claude Code cleanly, the workflow I am starting to see is: design the vision in Claude Design, then build the engine in Claude Code, then polish the front-end in Bolt or Lovable if needed.

That is a stack. A real one. And it is starting to feel like a stack that actually fits the way my brain works.

One more honest note.

Running out of credits mid-build was frustrating. It is also a real part of the AI builder experience right now. Every one of these tools costs something. Claude Design is part of the Pro, Max, Team, or Enterprise Claude plans, but it uses credits the way other advanced features do.

For a solo builder iterating heavily, this matters.

In Edition 345, I argued that evaluation is the most important skill of the AI era. This is part of that. Understanding not just what a tool can do, but what it costs you to actually use it for real work.

I did not find out where the ceiling was on my plan until I hit it. Which is a small version of the bigger evaluation lesson: you only learn what a tool really fits for when you try to use it for something that matters.

I am going to budget for Claude Design deliberately going forward. Not just "try it." Actually plan the credits around a specific build I want to complete.

Two things. This week.

1. Test Claude Design With a Real Brief

If you have a paid Claude plan, do not waste your first session on a throwaway idea. Pick something you have been wanting to visualize. Something you have thought about enough to describe well. Feed it context. Upload a reference document. Give it a clear brief.

See what it does when you actually show up prepared.

You might still hit the credit wall like I did. But what you get before that wall will tell you whether this tool has a spot in your stack.

2. Notice the Default Aesthetic

When you do your first real build, pay attention to what the tool leans toward visually before you tell it otherwise. The fonts. The colors. The spacing. The visual energy.

Ask yourself: do I want to start from this aesthetic and push outward, or do I want to override it from the beginning?

Either answer is fine. But knowing which one fits your work helps you use the tool more intentionally.

I said in Edition 347 that Claude Design might matter more for dyslexic and neurodivergent creators than anyone has noticed yet. After actually using it with a real brief, I am more convinced of that than I was before.

Not because it is the best tool on the market. Not because it solves every design problem. Not because it is finished.

Because it reduces a specific kind of cognitive load that traditional design tools create for brains like ours. And it has taste. And it collaborates cleanly with the rest of the builder stack.

For ten minutes of real use with a strong brief, I saw enough to know this belongs in my workflow.

I will spend more time with it next week when my credits reset. When I do, I will tell you what I learn. What breaks. What surprises me. What does not live up to the hype.

Because that is the deal. Honest experiments. Real results. No inflated claims. Even when the tool is as impressive as this one is turning out to be.

Edition 349: A new academic paper just named something I have been writing about for three years. They call it the "LLM Fallacy." I have been calling it something else. The difference matters a lot for neurodivergent creators, and the Cognitive Balance Model is the answer the researchers did not know they needed.

Matt "Coach" Ivey Founder, LM Lab AI | Creator, The Dyslexic AI Newsletter

Dictated, not typed. Obviously.

🎨 Ran a real experiment with Claude Design using a detailed, iterated prompt. Hit my credit wall before the build finished. What I saw before the wall was enough to tell me this tool has real potential.

✨ Claude Design has a distinct aesthetic. Soft tones. Pastel accents. Light, airy backgrounds. The kind of default taste that helps a non-designer produce work that looks considered without having to describe every visual choice.

🏗️ It fits the stack from Edition 346 as the visual and prototyping layer. Sits alongside Claude Code, Bolt.new, and Lovable. Hands off cleanly. Not a replacement. A new layer.

💰 Credits matter. Running out mid-build was a real lesson in evaluating tools. Budget deliberately for the work you actually want to do, not just for "trying it out."

🧠 For dyslexic and neurodivergent creators, the default aesthetic doing some of the heavy lifting is a real accessibility benefit. Start from tasteful, push outward. Easier than starting from blank.

🧪 Two things to do this week: test with a real brief, not a throwaway one. And notice whether the default aesthetic is a starting point you want to build from or override.

🔒 Cognitive Partner Members get the live updates as I rebuild the Cognitive Partner OS mockup with Claude Design next week. 50 founding spots at $19/month, locked forever.