Clarify distinction between frontend-design and web-artifacts-builder skills

## What I noticed

While setting up my skills, I came across both `frontend-design` and `web-artifacts-builder` and wasn't sure which one to use for different scenarios. After reading through both in detail, I think I understand the distinction now, but wanted to share my initial confusion in case it helps others.

## The descriptions that confused me

**frontend-design:**
> Create distinctive, production-grade frontend interfaces... Use this skill when the user asks to build web components, pages, **artifacts**, posters, or applications...

**web-artifacts-builder:**
> Suite of tools for creating elaborate, multi-component **HTML artifacts** using modern frontend web technologies...

Both mention "artifacts" which initially made me think they might be doing similar things.

## What I learned after diving deeper

After reading the full skill files, I realized they serve quite different purposes:

| Skill | What it actually does |
|-------|----------------------|
| `frontend-design` | A design philosophy guide focused on aesthetics (typography, color, motion, layout). Framework-agnostic. No tooling. |
| `web-artifacts-builder` | A complete build pipeline with shell scripts that creates a React+Vite+shadcn project and bundles it into a single `bundle.html` |

So they're actually complementary rather than overlapping — one is about *how to design well*, the other is about *how to package complex interactive HTML*.

## My question

Is my understanding correct? If so, would it perhaps be helpful to clarify the distinction in the descriptions?

For example, I'm wondering if something like this might help future users:

- Maybe noting in `web-artifacts-builder` that it's specifically for bundling complex apps into a single HTML file (vs general frontend work)?
- Or perhaps clarifying that `frontend-design` is the go-to for most frontend tasks, while `web-artifacts-builder` is for a specific packaging use case?

I could be misunderstanding the intended use cases though — happy to learn if there's something I'm missing here\!

---

Thanks for maintaining these skills. They've been really helpful for my workflow.