Claude's Design Trio Is Moved Locally, and Artifacts Is No Longer a Required Path

baoyu-design v2 is out. The author, Baoyu, positions it as a complete port of Claude Design, Claude Slides, and Claude Dashboard. The experience is close to the original, with one missing feature: comments. The key change is that it no longer depends on Claude Artifacts and can run on any Agent and any model, with fully open-source code.

Project URL: https://github.com/jimliu/baoyu-design

It solves a very concrete practical problem. Previously, when using Claude for design or slides, outputs were in online Artifacts while project files were local, so you had to import and export back and forth. baoyu-design eliminates that step by keeping design files directly with the project. The built-in editor can make changes and sync/save them to local files after editing; changes can also be initiated from the Agent, with two-way sync. Export supports PDF, HTML, and PNG, and you can preview at different screen sizes.

Claude Dashboard running locally:

https://github.com/JimLiu/baoyu-design/blob/main/skills/claude-dashboard/SKILL.md

Claude Slides runs in Codex with the same effect; the built-in editor can make changes and export editable PPTX:

The design style issue was also mentioned. Some users said the style was too Claude-like and couldn't be used in many contexts. The author replied that switching the design system is enough; the website design in the demo has no trace of Claude. The project includes a Claude Design System skill for importing design systems and keeping the style consistent. The default style is only a starting point, not a lock-in.

When running Claude Design locally, the files are right in the project, so there is no need to import/export between online Artifacts and the local Project. The editor can edit directly, sync to local files after saving, and changes can also be initiated from the Agent.

There is practical feedback on model choice. The author recommends Opus 5.5. Someone used DeepSeek with the previous standalone skill and the results were not great; the author suggested trying GLM. Regarding domestic Chinese models, the author said they were okay. Another user tried it in Codex and felt that Codex frontend design has always been hard to describe; this time, although it still feels strongly Claude-like, it is much better than before. That is a fair assessment: the tool can solve part of the problem, but it will not make up for all of a model's aesthetic shortcomings.

The missing piece is also clear: there is no comment feature. Someone asked whether it would be added later, and the author said it is hard to do because the agent has no interface for it, so they need to think about it more. Someone else worried about whether using Claude Code would get their account banned, and the author replied that it is fine.

One judgment: what this type of tool really solves is getting design outputs out of the platform and turning them into ordinary files in the project. Agents can edit them, editors can edit them, and export formats can be handed off downstream. One less dependency layer means a lower migration cost. As for style and model performance, switching design systems and switching models are both adjustable. Getting it running first is more practical than repeatedly pasting files back and forth in Artifacts.