SkillsAdd

emdash-cms/emdash

wordpress-theme-to-emdash

Port WordPress themes to EmDash CMS. Use when asked to convert, migrate, or port a WordPress theme to EmDash, or when creating an EmDash site that should match an existing WordPress site's design. Handles design extraction, template conversion, and EmDash-specific features like menus, taxonomies, and widgets.

First seen Apr 2, 2026

Installation

$ npx skills add emdash-cms/emdash --skill wordpress-theme-to-emdash
View on skills.sh ↗ GitHub repository ↗

Summary

  • Port WordPress themes to EmDash CMS.
  • Use when asked to convert, migrate, or port a WordPress theme to EmDash, or when creating an EmDash site that should match an existing WordPress site's design.
  • Handles design extraction, template conversion, and EmDash-specific features like menus, taxonomies, and widgets.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from emdash-cms/emdash.

npx skills add emdash-cms/emdash
building-emdash-site 98 emdash-cli 94 adversarial-reviewer 93 creating-plugins 78 wordpress-plugin-to-emdash 52 agent-browser 48 writing-emdash-docs 6 ux-acceptance-coordinator 3

Browse all from emdash-cms/emdash

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 12.3K
License LICENSE
Default branch main
Open issues 168
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,444 B
  • docs SUMMARY.md 343 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 46 installs

SKILL.md

WordPress Theme to EmDash

Port WordPress themes to EmDash in six phases. Read the phase file before starting each phase.

Critical Rules

  1. Copy scaffold first - Start every theme by copying scaffold/ from this skill
  2. Take screenshots of demo - Identify the demo URL and capture all page types using agent-browser before starting work
  3. No hard-coded content - Use getSiteSettings() for title/tagline, getMenu() for navigation
  4. Server-rendered pages - Never use getStaticPaths() for EmDash content
  5. Astro 6 - Use ClientRouter not ViewTransitions, Zod 4 syntax, Node 22+
  6. Use emdash Image component - For all images, import Image from "emdash/ui"

Phases

Phase File Summary
1 phases/1-discovery.md Download theme, screenshot demo, capture images
2 phases/2-design.md Extract CSS variables, fonts, colors
3 phases/3-templates.md Convert PHP templates to Astro
4 phases/4-dynamic.md Site settings, menus, taxonomies, widgets
5 phases/5-seed.md Create seed file with demo content
6 phases/6-verify.md Screenshot, compare, iterate, build

Checklist

Setup

  • Copy scaffold/ to new theme directory. Unless otherwise specified by the user, make this a subdirectory of themes/ and name it after the WordPress theme (e.g., themes/twentytwentyfour/).
  • Rename folder, update package.json
  • Verify build: pnpm build

Phase 1: Discovery

  • Theme source downloaded
  • Demo site identified
  • discovery/ folder created with screenshots/, images/, notes.md
  • All page types screenshotted
  • Sample images downloaded

Phase 2: Design

  • CSS variables in global.css
  • Fonts loading
  • Colors match demo

Phase 3: Templates

  • Homepage, single post, archive, category, tag, page, 404
  • Components extracted (PostCard, etc.)

Phase 4: Dynamic

  • Site settings (title, tagline, logo from CMS)
  • Navigation menus (from CMS, not hard-coded)
  • Taxonomies
  • Widget areas (if applicable)

Phase 5: Seed

  • Seed file created with demo images at .emdash/seed.json (or wired up via package.json#emdash.seed)

Phase 6: Verify

  • Dev server applied seed cleanly on first request (no validation errors in logs)
  • Output screenshots captured
  • Visual comparison done
  • Build succeeds: pnpm build
  • LICENSE file downloaded (GPL-2.0 in most cases)
  • README credits original theme

Reference Documents

  • references/astro-essentials.md - Astro 6 patterns
  • references/template-patterns.md - PHP → Astro conversion
  • references/concept-mapping.md - WP → EmDash concepts
  • references/emdash-api.md - Full API reference
  • references/design-extraction.md - CSS extraction techniques