Nice to see a CLI turning a design system into a skill.md so the agent + UI share the same token set. We throw tree-sitter dumps plus a dependency graph at Claude and tag the package with a matching token manifest so the chat widgets, docs, and dashboards all pull the same palette.
Would it make sense to add an export command that emits JSON/CSS variable files so the dashboards and telemetry tooling can consume those specs without any copy/paste?
this could go in many directions, but based on my experience, a thinner skill file with good instructions fares better than a huge file of very atomic configurations
Needed something like this 2 months ago for a project, happy to see it published
Nice to see a CLI turning a design system into a skill.md so the agent + UI share the same token set. We throw tree-sitter dumps plus a dependency graph at Claude and tag the package with a matching token manifest so the chat widgets, docs, and dashboards all pull the same palette. Would it make sense to add an export command that emits JSON/CSS variable files so the dashboards and telemetry tooling can consume those specs without any copy/paste?
this could go in many directions, but based on my experience, a thinner skill file with good instructions fares better than a huge file of very atomic configurations
Can't wait to test this with my next lovable project.