vibe-designlisted
Install: claude install-skill ZEST-im/vibe-engineering
# Vibe Design — See the Screen Before You Build It
Building a screen you have never seen is how work gets thrown away. This skill puts one
gate in front of implementation: the screen exists as HTML, it opened in a browser, and
the user approved it.
## What this skill is and is not
**This skill owns three things:** the *ordering rule* (nothing gets implemented before the
screen has been seen and approved), the *artifact format* (self-contained HTML on disk),
and *where the design language comes from*.
That third one is the difference between a usable mockup and AI slop.
## Do not invent a design language
Generated design looks generic for a specific reason: **the model invents a color ramp, a
type scale, and a spacing rhythm from nothing on every run.** Invented-from-nothing
converges on the average — that is what "AI slop" is.
The fix is not to try harder. It is to **start from something that already exists**, take
its token layer, and then make one deliberate move that belongs to this product.
### Ask where the starting point comes from — first, before anything else
This question decides everything downstream, so ask it before the three-second message,
before screens, before tone. **There are two paths, and both end in real values.**
| Path | What you get |
|---|---|
| **A. Catalog** *(default)* | A system from `references/design-systems.md`, picked by what the product is. Real token files, checked licenses |
| **A′. House system** | If the org has one — e.g. `refe