AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Wordpress Mockups

skill-shaunandrews-agent-skills-wordpress-mockups · by shaunandrews

Build accurate WordPress/Gutenberg UI mockups using pre-extracted design tokens, icons, and components. Use when prototyping WordPress admin interfaces or Site Editor concepts.

No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-shaunandrews-agent-skills-wordpress-mockups

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-shaunandrews-agent-skills-wordpress-mockups)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
5mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Wordpress Mockups? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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:


  
  
  Mockup Name
  
    /* Paste tokens, base, and component CSS here */
  

  

2. Add Design Tokens

Copy the contents of tokens/wordpress-tokens.css into your `` 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 `` 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:


  
    
  

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 Text

Input with Label


  Label
  
    
    
  

Collapsible Panel


  
    Section Title
    ...
  
  Panel content...

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/

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.