DashKit
One call inside a session, and the mini app stops looking like a prototype.
The question I was chasing
What would it take to rebuild how an Artifact looks without touching what it does?
People build real things in Claude Artifacts, including trackers, dashboards, calculators and documents that update mid-conversation. Then the thing renders like a prototype. Fine while an idea is being tried out. Awkward the moment it has to be shared or handed to someone else. The capability was there and the look never caught up. I kept running into it.
The constraints
Nothing about the Artifact's behaviour could change. Logic, data, interactions: whatever went in had to come out identical, because the thing already worked and only looked wrong.
There could be no configuration step. A skill that asks which components to use, or wants CSS back, has handed the job to the person who wanted it done.
And it had to run inside a Claude session, where there is nowhere to put a build step. Whatever came out had to be something Claude could write directly.
The decisions that mattered
Rebuild the visual layer, leave the logic alone. The skill reconstructs the look and puts the data structure and the interactions back exactly as it found them. That is also the limit of what the skill can fix. An Artifact whose real problem is what it does needs that fixed first.
I targeted a known off-the-shelf component library (shadcn) rather than invent a house style. It is accessible by default, and opinionated enough that everything it touches comes out coherent. Claude knows it well too, which is what makes a one-step rewrite reliable instead of a lottery.
One call, no arguments, installed once. It drops into Claude for Desktop and then works from inside any Artifact session. Anything that needed setting up first would not get reached for in the middle of building something.
Built with: Claude Code skills, shadcn UI, Tailwind CSS, Radix primitives
Where it landed
DashKit costs nothing, the code is open on GitHub, and it drops into Claude for Desktop in under a minute. After that it runs from inside any Artifact session, and what comes back has proper spacing, readable type and a hierarchy that makes sense.
I gave it no arguments on purpose. An Artifact that wants a look other than that library gets the library look, and that is the whole deal.
Part of the Rolling Waves work archive.