design
/design
Projektuje i poprawia interfejsy, animacje i strony lądowania, w tym ocenę ruchu w aplikacjach web i Expo, z testem skrajnych danych.
- Autor
- NathanColosimo ↗
- Repozytorium
- skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 24
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 2
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Projektuje i poprawia interfejsy, animacje i strony lądowania, w tym ocenę ruchu w aplikacjach web i Expo, z testem skrajnych danych.
Oryginalny opis (EN)
UI design, polish, motion, and landing pages. Use when building or redesigning UI, choosing an aesthetic, polishing components, adding or reviewing animation and motion (web or Expo/React Native), stress-testing UI with worst-case data, or building a landing or marketing page.
Jak działa
- Rules for every screen
- Which guide
- taste
Podgląd SKILL.md
---
name: design
description: UI design, polish, motion, and landing pages. Use when building or redesigning UI, choosing an aesthetic, polishing components, adding or reviewing animation and motion (web or Expo/React Native), stress-testing UI with worst-case data, or building a landing or marketing page.
---
# Design
This skill routes to detailed guides. Pick the guides that match the task,
read each one in full before you start, and follow it. Several can apply at
once, for example `frontend-design` with `animate`.
Paths below are relative to this skill's folder. Each guide lives in
`guides/<name>/GUIDE.md`, and the files it mentions sit next to it. When a
guide points to another guide by name, read `guides/<that name>/GUIDE.md`.
The animation values all guides share (frequency, easing, durations, springs)
are in `guides/review-animations/STANDARDS.md`.
The project's own design system, tokens, and components come first. A guide
shapes how you use them. It doesn't replace them.
## Rules for every screen
These apply whichever guide you use.
- **Every element earns its space.** Each heading, button, status line, and
border must help the user understand or do something. Remove headings that
repeat what's obvious, status text that says nothing new ("Viewing
computer"), and containers that only mark where one component ends.
- **One control per intent.** If two buttons do the same thing, merge them,
or make the difference clear in the user's words.
- **Keep secondary actions out of the way.** Admin and lifecycle actions (stop,
delete, reset) go somewhere deliberate, not permanently on the main screen.
Don't hide a truly essential action just to cut the button count.
- **Review the whole screen,** not each component alone. A page header, a
toolbar, and an embedded viewer's toolbar are one experience.
- **Loading looks like the loaded layout.** The pending state uses the same
frame, alignment, and markers as the content, so nothing jumps when data
arrives. Don't show fake data or enabled actions before it does.
- **Keep content on screen during a refresh,** including after a refresh
fails. Show the error next to it.
- **Progress shows on the trigger.** The button that started an action shows
its progress ("Save" → "Saving…") and keeps its size. Don't add a separate
"Saving…" row.
- **Errors appear next to what failed** and stay until resolved. Use a toast
only when there's no better place.
- **Test the transitions,** not just the final screenshot: loading to content,
error to retry to success, on desktop and narrow screens, with long text.
## Which guide
| Task | Guide |
| --- | --- |
| Build new UI or reshape an existing one; pick an aesthetic direction and typography | `frontend-design` |
| Polish components and the small details that make UI feel good; design critique | `emil-design-eng` |
| Build a landing page, marketing site, or company site, or fix a page that looks generic or "AI-made" | `taste` (see below) |
| Animate something on the web: transitions, motion, making a component feel alive | `animate` |
| Animate in Expo or React Native: gestures, sheets, screen transitions, press feedback, haptics | `animate-expo` |
| Critique existing animation or motion code | `review-animations` |
| Audit a whole codebase's motion and plan improvements | `improve-animations` |
| Find places that should animate but don't | `find-animation-opportunities` |
| Stress-test UI with worst-case data: long text, empty states, huge numbers, other scripts | `break-ui` |
## taste
`taste` is the [taste-skill](https://github.com/leonxlnx/taste-skill) kit for
landing and marketing pages. It is too large to copy here (about 40 MB of
assets), so fetch it when you need it:
```bash
cache="$HOME/.cache/taste-skill"
if [ -d "$cache/.git" ]; then git -C "$cache" pull -q --ff-only; else git clone -q --depth 1 https://github.com/leonxlnx/taste-skill "$cache"; fi
```
Then read `$HOME/.cache/taste-skill/skills/taste-skill/SKILL.md` and follow
it. Where it says `<skill>`, it means
`$HOME/.cache/taste-skill/skills/taste-skill`. It needs Node 22 or later and
a Chromium browser for its checks.
Use it for standalone marketing pages. Inside an existing product with its
own design system, use `frontend-design` and `emil-design-eng` instead.
Pliki w paczce (24)
- SKILL.md 4 KB
- agents/openai.yaml 1 KB
- guides/animate/GUIDE.md 10 KB
- guides/animate/LICENSE 1 KB
- guides/animate/RECIPES.md 7 KB
- guides/animate-expo/GUIDE.md 16 KB
- guides/animate-expo/LICENSE 1 KB
- guides/animate-expo/RECIPES.md 16 KB
- guides/break-ui/CATALOG.md 8 KB
- guides/break-ui/GUIDE.md 11 KB
- guides/break-ui/LICENSE 1 KB
- guides/emil-design-eng/GUIDE.md 9 KB
- guides/emil-design-eng/LICENSE 1 KB
- guides/find-animation-opportunities/GUIDE.md 6 KB
- guides/find-animation-opportunities/LICENSE 1 KB
- guides/frontend-design/GUIDE.md 5 KB
- guides/frontend-design/LICENSE.txt 10 KB
- guides/improve-animations/AUDIT.md 3 KB
- guides/improve-animations/GUIDE.md 5 KB
- guides/improve-animations/LICENSE 1 KB
- guides/improve-animations/PLAN-TEMPLATE.md 3 KB
- guides/review-animations/GUIDE.md 5 KB
- guides/review-animations/LICENSE 1 KB
- guides/review-animations/STANDARDS.md 10 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · NathanColosimo/skills | 100 | MIT |
| cihantopac/markilo | 100 | Apache-2.0 |
| NatikChhabra/claude-arsenal | 100 | MIT |
| AtlasScope/agent-kit | 100 | MIT |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| serpro69/claude-toolbox | 100 | Apache-2.0 |
| serpro69/claude-toolbox | 100 | Apache-2.0 |
| ouestlabs/audio-ui | 100 | MIT |
| Vamp-pire/hype-me | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 5d0c902f2d7e (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100ui-design
Projektuje i buduje UI w React, Next i Tailwind, audytuje defekty wizualne i interakcji oraz testuje komponenty na danych najgorszego przypadku, np. landing page, dark mode i responsywność. - 90frontend-design
Buduje strony, komponenty, strony lądowania, panele i układy interfejsu na żądanie, na przykład stronę albo panel do wdrożenia. - 90frontend-design
Ustala kierunek wizualny i estetykę interfejsów frontendowych: strony, landing page, dashboardy i komponenty serwerowe Next.js, gdy liczy się tożsamość wizualna. - 100ia-frontend-design
Ustala kierunek wizualny stron, landing pageów i dashboardów: układ, styl i tożsamość interfejsu aplikacji webowych. - 100nuxt-frontend-design
Buduje i dopracowuje strony oraz systemy projektowe w Nuxt UI v4+: landing page, dashboardy, tokeny, animacje i interfejsy, które wyglądają zbyt generycznie. - 90web-ui
Zmienia i sprawdza widoczne elementy strony: najpierw ogląda, planuje z tokenami projektu, buduje i testuje na skrajnych danych.