DashKit
One call inside a session, and the mini app stops looking like a prototype.
Useful work that deserved to look better
I wanted to create DashKit because Claude Artifacts were becoming increasingly useful from a technical perspective, but I really, really didn't like how they looked out of the box. I felt they never visually did justice to the dashboards I was creating.
Artifacts as part of the workflow
Artifacts make visualising and sharing work much easier. With MCPs connecting Claude to live data across different apps and services, those dashboards and trackers were becoming an increasingly useful way to keep on top of projects and workflows.
The functionality was there. I wanted a simple way to make the things I was building look good too, without having to redesign each one myself.
A single command to restyle it
I built DashKit as a skill that takes the dashboard or artifact you've been working on and applies shadcn UI styling throughout. You run it from inside the Claude session, with one command.
It focuses on the appearance, keeping the existing logic, data and interactions in place. That means I can keep working on what the artifact does and call on DashKit when I want to improve how it looks.
Light and dark
Light and dark mode were part of that from the start, for those of us who don't enjoy staring at bright, shiny screens all day. I wanted the result to be something I'd enjoy using as well as sharing.
DashKit is free and open source, so other people can use it on the artifacts they're making too.
Built with: Claude Code skills, shadcn UI, Tailwind CSS, Radix primitives
Part of the Rolling Waves work archive.