wordpress-mockups

작성자: automattic

사전 추출된 디자인 토큰, 아이콘 및 컴포넌트를 사용하여 정확한 WordPress/Gutenberg UI 목업을 구축합니다. WordPress 관리자 인터페이스 또는 사이트… 프로토타이핑 시 사용합니다.

npx skills add https://github.com/automattic/design-skills --skill wordpress-mockups

WordPress Mockups Skill

Build accurate WordPress/Gutenberg UI mockups using pre-extracted design tokens, icons, and components.

When to Use

Use this skill when building HTML/CSS mockups of WordPress admin UI, the Site Editor, or any Gutenberg-based interface.

Directory Structure

skill/
├── SKILL.md                    # This file
├── base.css                    # Reset + base typography
├── tokens/
│   ├── TOKENS.md               # Token documentation
│   └── wordpress-tokens.css    # CSS custom properties
├── icons/
│   ├── ICONS.md                # Icon documentation + full list
│   └── svg/                    # 321 SVG icon files
├── components/
│   ├── COMPONENTS.md           # Component documentation
│   └── *.html                  # 12 component files
└── patterns/
    ├── PATTERNS.md             # Pattern documentation + composition rules
    └── *.html                  # Layout patterns (Site Editor header, etc.)

Workflow

0. Check for Patterns First

Before building from scratch, check patterns/ for a pre-built layout:

  • Building a Site Editor mockup? Start with patterns/site-editor-header.html
  • Building a modal? Start with components/modal.html

Patterns > Components > Custom CSS

Patterns are complete, correct layouts. Components are building blocks. Only write custom CSS for things not covered by either.

1. Start a New Mockup

Create an HTML file with the basic structure:

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>Mockup Name</title>
  <style>
    /* Paste tokens, base, and component CSS here */
  </style>
</head>
<body>
  <!-- Mockup content -->
</body>
</html>

2. Add Design Tokens

Copy the contents of tokens/wordpress-tokens.css into your <style> block. This gives you all the CSS custom properties:

  • Colors: var(--wp-gray-900), var(--wp-admin-theme-color)
  • Spacing: var(--wp-grid-unit-20), var(--wp-grid-unit-05)
  • Typography: var(--wp-font-size-medium), var(--wp-font-weight-medium)
  • Dimensions: var(--wp-button-size), var(--wp-header-height)
  • Shadows: var(--wp-elevation-medium)
  • Radii: var(--wp-radius-small)

3. Add Base Styles

Copy the contents of base.css after the tokens. This sets up:

  • Box-sizing reset
  • Default font family and size
  • Focus styles
  • Link styles

4. Add Components

For each UI element you need:

  1. Open the relevant component file (e.g., components/button.html)
  2. Copy the CSS from the <style> block
  3. Copy the HTML markup you need from the examples
  4. Customize the content

5. Add Icons

To include an icon:

  1. Check icons/ICONS.md for the icon name
  2. Read the SVG: cat skill/icons/svg/{name}.svg
  3. Paste the SVG inline in your markup

Example:

<button class="components-button has-icon" aria-label="Settings">
  <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24">
    <path d="..."/>
  </svg>
</button>

6. Build Layout

Compose components into your mockup layout. Add custom CSS for:

  • Page structure
  • Component arrangement
  • Mockup-specific styling

Key References

Patterns

  • See patterns/PATTERNS.md for available layouts and composition rules
  • Composition rules tell you how WordPress UIs are assembled (what goes where, which buttons are primary, etc.)
  • Always check patterns before building a layout from scratch

Tokens

  • See tokens/TOKENS.md for where values come from
  • All spacing is based on 8px grid (--wp-grid-unit)
  • Use --wp-admin-theme-color for accent/interactive elements

Icons

  • 321 icons available in icons/svg/
  • All use viewBox="0 0 24 24"
  • Add fill="currentColor" to inherit text color

Components

  • See components/COMPONENTS.md for available components
  • Class naming: .components-{name}, .components-{name}__{element}
  • Modifiers: .is-primary, .is-compact, .is-pressed, etc.

Common Patterns

Button with Icon

<button class="components-button has-icon has-text">
  <svg>...</svg>
  Button Text
</button>

Input with Label

<div class="components-input-control">
  <label class="components-input-control__label">Label</label>
  <div class="components-input-control__container">
    <input type="text" class="components-input-control__input">
    <div class="components-input-control__backdrop"></div>
  </div>
</div>

Collapsible Panel

<div class="components-panel__body is-opened">
  <button class="components-panel__body-toggle">
    Section Title
    <svg class="components-panel__arrow">...</svg>
  </button>
  <div>Panel content...</div>
</div>

Tips

  1. Always use tokens — Don't hardcode colors or spacing
  2. Copy, don't reference — Each mockup should be self-contained
  3. Check component variants — Most components have multiple states/sizes
  4. Use semantic modifiers.is-primary, not custom color classes

Source

Design tokens, icons, and component styles extracted from:

  • Gutenbergpackages/base-styles/ and packages/components/

automattic의 다른 스킬

wp-phpstan
automattic
WordPress 프로젝트(플러그인/테마/사이트)에서 PHPStan 정적 분석을 설정, 실행 또는 수정할 때 사용: phpstan.neon 설정, 기준선,…
official
wp-playground
automattic
WordPress Playground 워크플로우에 사용: 브라우저 또는 @wp-playground/cli(서버, run-blueprint, build-snapshot)를 통해 로컬에서 빠르게 일회용 WP 인스턴스를 실행합니다.
official
wp-plugin-development
automattic
WordPress 플러그인 개발 시 사용: 아키텍처 및 훅, 활성화/비활성화/제거, 관리자 UI 및 설정 API, 데이터 저장, 크론/작업, 보안…
official
wp-project-triage
automattic
WordPress 저장소(플러그인/테마/블록 테마/WP 코어/Gutenberg/전체 사이트)의 도구/테스트/버전 등을 포함한 결정론적 검사가 필요할 때 사용합니다.
official
wp-rest-api
automattic
WordPress REST API 엔드포인트/라우트를 구축, 확장 또는 디버깅할 때 사용: register_rest_route, WP_REST_Controller/컨트롤러 클래스, 스키마/인수…
official
wp-wpcli-and-ops
automattic
WP-CLI(wp)를 사용하여 WordPress 작업을 수행할 때 사용: 안전한 검색-바꾸기, DB 내보내기/가져오기, 플러그인/테마/사용자/콘텐츠 관리, 크론, 캐시 플러싱 등
official
wpds
automattic
WordPress 디자인 시스템(WPDS)과 그 컴포넌트, 토큰, 패턴 등을 활용하여 UI를 구축할 때 사용합니다.
official
woocommerce-finalize
automattic
WooCommerce 플러그인을 위한 사전 릴리스 코드 건강 및 추적성 감사. 코드 리뷰 후 실행되며, 죽은 코드, 중복, 구조적 복잡성 등을 중점적으로 확인합니다…
official