What's this about?
Baoyu tried the `/design` skill that shipped earlier this week and gave a hands-on verdict: it's noticeably better than using Claude Design on the website, because it's connected to your local project — no switching back and forth between browser and editor. Usage is just `/design` followed by what you want designed. His practical conclusion for other users: if you're on Claude Code, you no longer need third-party design skills, including his own baoyu-design.
What exactly does "connected to your local project" change?
A design tool in a browser produces an artifact you then have to describe or transfer to whatever is writing your code. That handoff is where fidelity is lost — the agent implementing it is working from a description or a screenshot rather than the thing itself. When the design step happens inside the same session that will write the implementation, the agent has the actual artifact, your existing components, and your conventions in context simultaneously. The gain isn't the design being better; it's the translation step disappearing.
Why is this worth noticing?
- A developer recommending against his own tool is unusually credible, and the clearest signal that the built-in version is genuinely better.
- It's evidence for the built-in-versus-skill question that ran through yesterday's Demystifying Agent Skills discussion: some capabilities work better integrated than packaged.
- It also implies a pattern for skill authors: the useful third-party skills are the ones filling gaps the vendor hasn't closed, and those gaps close without warning.