Przejdź do treści
Biblioteka skilli
Projektowanie i UX · Budowanie i kod

web-design

/web-design

Projektuje stronę, ekran aplikacji lub portfolio: koncepcje, tokeny, hierarchię wizualną, responsywność i sprawdzenie dostępności.

Repozytorium
ondra ↗
Licencja
MIT
Ostatnia zmiana repozytorium
14.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 14.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Projektuje stronę, ekran aplikacji lub portfolio: koncepcje, tokeny, hierarchię wizualną, responsywność i sprawdzenie dostępności.

Oryginalny opis (EN)

Designing a site, web app screen, landing page or portfolio that should look made by a good designer, not by AI. Use for concepts, design directions, mockups and building or refining the chosen design. Covers real references, live concept prototypes, design-system notes in DESIGN.md, design tokens, visual hierarchy, responsive layouts, UI states and accessibility checks. Use for 웹 디자인, 디자인 시스템, 디자인 토큰, 디자인 규칙, 랜딩 페이지 and 포트폴리오. Not for a quick opinion.

Jak działa

  1. 0. Read the project and the brief
  2. 1. References first (before a new layout)
  3. 2. Concepts as live prototypes, not boards
  4. 3. Keep the chosen design reusable
  5. 4. Avoid generic defaults
  6. 5. Build with the project's pieces
  7. 6. Check the rendered result
Sekcje z nagłówków SKILL.md, w oryginale · 161 linii, 1 593 słów
Podgląd SKILL.md
---
name: web-design
description: >
  Designing a site, web app screen, landing page or portfolio that should look made
  by a good designer, not by AI. Use for concepts, design directions, mockups and
  building or refining the chosen design. Covers real references, live concept
  prototypes, design-system notes in DESIGN.md, design tokens, visual hierarchy,
  responsive layouts, UI states and accessibility checks. Use for 웹 디자인,
  디자인 시스템, 디자인 토큰, 디자인 규칙, 랜딩 페이지 and 포트폴리오. Not for
  a quick opinion.
---

# Web design

For implementing a supplied design (a Figma link, 피그마 그대로, 디자인 그대로),
read and follow the `mimikyu` skill instead. Do not run concept selection or
redesign a reference the user already chose. This skill is for creating a new
design direction and carrying an approved direction into later work.

## 0. Read the project and the brief

- Establish the page's purpose, audience, main action, real content and existing
  brand assets. Say your interpretation briefly in the report, not on the page.
- Read repository instructions, existing design notes (including `DESIGN.md`
  when present), tokens, components and nearby screens before proposing changes.
  Keep the project's stack, icon family and design system; do not install a new
  framework, font or animation library just to follow a style example.
- User choices and established project rules outrank aesthetic heuristics here.
  Do not guess a new direction or ask the user to choose one they already chose.
  For a focused change in an established design, go to steps 3, 5 and 6; do not
  restart reference gathering or produce concepts for an unchanged direction.
- Ask only when missing intent or content would materially change the result.
  Do not infer permission to rewrite supplied copy, invent facts or replace a
  brand. A design-system documentation task does not require a new UI prototype.

## 1. References first (before a new layout)

- Open what the user pointed at and a handful of the best real examples of the
  same kind (personal sites the user named, awwwards / siteinspire / godly.website
  winners, the products they admire). Use the browser; take screenshots.
- For each, write down the concrete moves that make it good: the type pairing
  and sizes, the grid, a signature interaction, how motion responds to the
  user, what is real content (video, photos, product) vs decoration.
- Use brand names and style catalogs as search leads, not authoritative rules.
  Inspect the current site or official guidelines before describing its design.
  Extract useful principles rather than copying branding or a whole page.
- Save screenshots and notes in the project's existing reference location, or
  in `$APP_ARTIFACTS_DIR/refs/` when it has none. Record source URLs and what
  each reference informs.
  Show the most telling ones as `shot` blocks so the user sees what you saw.

## 2. Concepts as live prototypes, not boards

- A few directions (two or three is usually enough), each a real page (real
  fonts, real motion, the user's content and photos), not a labelled sketch:
  people judge a design by using it. Where interaction matters, give each
  something to try (scroll scene, drag, hover reveal).
- Directions that differ in idea, not just color, are worth comparing:
  e.g. "desktop/scrapbook", "editorial typography", "single 3D/canvas scene".
- Screenshot each at desktop and phone width, record a short clip of its
  interaction, and send: `shot` blocks + a `link` to the file to open live.
- Ask with options `{label, note}` (note = the feeling in one line) and the shots
  as `context`, then wait for the pick before building further.

## 3. Keep the chosen design reusable

After the user chooses, update the project's existing design document. If none
exists and the work establishes reusable rules, create a concise `DESIGN.md`
in the project root. For a one-off artifact or a small fix, do not add a design
system or extra exports merely to fill a template.

Record only decisions supported by the approved design or existing code:

- Purpose, audience, visual direction and reference links with their rationale.
- Semantic color roles, actual values and existing token names/source paths;
  distinguish brand accents from success, warning and error colors.
- Typography roles, font families, sizes, weights and line heights; spacing,
  content widths, breakpoints, radius, border and elevation rules.
- Component variants and relevant hover, focus, pressed, disabled, loading,
  empty and error states; responsive behavior and reduced-motion alternatives.
- Asset provenance, usage constraints and a short list of project-specific
  do's and don'ts. Record unknowns as unknowns, not invented exact values.

Keep existing token files authoritative; reference them instead of introducing
an independently maintained second token set. Use the project's document format,
not an assumed external schema or CLI. Export tokens only when the task needs it
and the project has a consumer. Before later work, read these notes again; update
only decisions changed by the user or implementation, without erasing unrelated
rules. Resolve a conflict with the approved direction before changing its look.

## 4. Avoid generic defaults

- The brief leaking into the page: the concept's name or option label
  ("편집형 프로젝트 전시", "A · 간결한 소개문"), the reference sites' names,
  the user's direction words ("차분한", "인터랙티브") printed as copy.
- Explanatory captions inside the design ("사례 전시 도판 · 실제 제품 화면 아님",
  "왜 추천하나요?", "작은 화면" panels). The page is the product, not a pitch.
  In an app, the same goes for standing text that explains how it works inside;
  a needed warning sits briefly next to its action.
- Beige/cream + serif numerals + one orange accent by default; purple gradients;
  glassmorphism cards; emoji icons.
- Everything centered in equal boxes; three identical cards in a row; every
  section the same height and rhythm.
- Generic headlines ("불편을 발견하고, 작동하는 흐름으로."), filler copy, fake
  metrics. Use the user's real words, projects, numbers, photos.
- Motion that loops by itself or decorates; fade-up on every block. Motion
  that answers the user (scroll, cursor, click) reads as designed.
- An arbitrary font pairing or a default font stack chosen without context.
  Keep the brand's fonts, including system fonts when intentional; for a new
  direction, choose typography from the references and verify language coverage.

These are warnings against unthinking defaults, not bans on a user's palette,
font or layout. Do not replace one formula with another: no mandatory asymmetry,
hero line count, card quota, single accent, dark mode or motion intensity.
Hierarchy and density should serve the content; repeated layouts can be right
for comparable data. Keep meaning and readability ahead of novelty.

## 5. Build with the project's pieces

- Use the approved design notes and existing tokens/components. Keep spacing,
  radii, icons, color roles and typography consistent across sections and states.
- Adding to an existing screen: render it first and keep its layout, changing
  only what the feature needs. Reused tokens and components alone don't keep a
  design; say it is kept only after comparing with that first shot side by side.
- Make the primary action and reading order clear. Use whitespace, alignment,
  scale and grouping deliberately; don't wrap every item in a card. Keep labels
  for the same action consistent without changing the user's supplied wording.
- Plan each section's small-screen layout, including navigation, dense content,
  long labels and text expansion. Prevent accidental overflow and clipped text;
  do not hide content or shrink it into illegibility to make it fit.
- Use real photos, product screenshots and videos. Ask for missing factual
  assets rather than fabricating products, endorsements or customer logos.
  If illustration is in scope, choose its purpose and placement first, then use
  available tools to produce or source it with appropriate usage rights. Never
  present a generated illustration as a real product screenshot. For charts or
  infographics, follow `visual-report` and use sourced data, not decorative numbers.
- Implement relevant UI states, not just a successful static screen. Forms need
  persistent labels, useful errors and visible focus. Links navigate and controls
  perform the advertised action; do not add fake interactions to fill a concept.
- Motion should explain an action, transition or hierarchy. Use existing motion
  tools or simple CSS; don't introduce a dependency for ornament. Preserve content
  and operation with reduced motion and without hover on touch devices. Reserve
  media space to avoid layout shifts; keep expensive effects out of routine input.

## 6. Check the rendered result

`browser-use` covers driving the browser. Reuse the project's existing checks and
capture the real page, not just source or a successful build. For a native app,
run the real app (`computer-use`) at its window sizes instead of a phone width.

- Compare the approved direction and implementation side by side at desktop and
  a phone width (around 390px), plus requested widths. Inspect hierarchy, alignment,
  wrapping, navigation, asset loading and consistent tokens across sections.
- Exercise the primary action and the states the changed flow can enter. Check
  keyboard order, visible focus, labels and touch access; essential information
  must not depend on color or hover alone. Check reduced motion, and both themes
  only if the project supports them or the task asks for them.
- Measure text and control contrast with an available checker against the actual
  backgrounds, including images and overlays. Report the measured result and
  scope; an attractive screenshot or one contrast check is not an accessibility
  conformance claim. If no checker is available, mark contrast unverified.
- Read visible copy, labels, alt text and errors: remove brief/option labels,
  filler, invented facts and awkward generated wording. Keep the user's content
  and voice intact. Do not add explanatory production notes inside the product.
- Check changed-file tests, types and lint required by the repository. If a
  performance claim is in scope, measure the same workload before and after;
  never invent scores or add a broad audit for a small design change.
- Fix observed defects and recheck only affected paths. Finish with screenshots
  covering the changed sections and a clip when interaction is part of the work.
  Report the design-note path, actual checks and anything unverified separately.
  Updating a skill or design document alone does not prove a rendered UI works.

Wersje

RepozytoriumWynikLicencja
Ta strona · 3x-haust/ondra100MIT
DanielC000/loom100MIT
ADWilkinson/astack100MIT
akillness/jeo-skills100MIT
travnie/twojstar100ISC
vkirill/claude-lane-stack100MIT
countbot-ai/countbot100MIT
xiaopu-ai/web-design100MIT
zenobi-us/dotfiles90MIT

Migawka bazy z 13.11.2026 · wersja paczki 655b3d0ea567 (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

  • 100workflow
    Pomaga w pracy z przestrzenią specyfikacji projektu i plikiem Figma: tokenami, planowaniem UC i FR oraz synchronizacją.
  • 100web-design-essence
    Analizuje stronę, ekran lub brief, wyciągając hierarchię wizualną, układy, przepływy użytkownika i intencję projektu.
  • 100ui-design
    Podpowiada podstawowe wzorce UI: tokeny, hierarchię wizualną, stany, formularze, nawigację i dostępność.
  • 100apply
    Stosuje projekt z Figmy (komponenty, shell, UI czatu) w kodzie aplikacji, Storybooku i bieżących ekranach, także gdy trzeba rozstrzygnąć konflikt projektu lub dotrzymać terminu.
  • 91master-ui-skill
    Prowadzi projektowanie, poprawki i weryfikację interfejsów web i aplikacji: dostępność, responsywność, animacje i system designu.
  • 90figma-page-qa
    Sprawdza zgodność całej strony z ramką Figmy, zwracając uwagę na kolory tła sekcji oraz brakujące lub zamienione ikony.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.