# Wordpress Plugin To Emdash

Analyze and port WordPress plugin behavior, custom post types, shortcodes, admin...

- Repository: https://github.com/emdash-cms/emdash (14094 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add emdash-cms/emdash --skill wordpress-plugin-to-emdash -g -a claude-code -y`
Codex: `npx skills add emdash-cms/emdash --skill wordpress-plugin-to-emdash -g -a codex -y`
Cursor: `npx skills add emdash-cms/emdash --skill wordpress-plugin-to-emdash -g -a cursor -y`
Gemini CLI: `npx skills add emdash-cms/emdash --skill wordpress-plugin-to-emdash -g -a gemini-cli -y`

## Description

Analyze and port WordPress plugin behavior, custom post types, shortcodes, admin workflows, and stored data to current EmDash extension points. Use for WordPress-plugin migrations or when deciding which behavior belongs in an EmDash plugin, site schema, seed, or Astro code. Do not use for visual theme ports without plugin functionality.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Port a WordPress plugin to EmDash

Preserve the plugin's user-visible behavior and data model without translating PHP line by line. WordPress and EmDash divide responsibilities differently, so first decide whether each feature belongs in site schema, Astro code, a sandboxed plugin, or a trusted native plugin.

Load [creating-plugins](../creating-plugins/SKILL.md) before implementing plugin code. Load [building-emdash-site](../building-emdash-site/SKILL.md) when the port changes collections, seeds, queries, or frontend templates. Those skills define the current APIs; this skill covers migration decisions.

## Understand the source

Inspect the plugin source, installation behavior, database changes, hooks, REST endpoints, scheduled work, admin screens, shortcodes or blocks, frontend output, permissions, and external services. Identify behavior that users rely on separately from WordPress-specific implementation.

Record:

- required content and configuration data;
- actions that mutate or publish data;
- authorization and trust boundaries;
- background or retry behavior;
- frontend and administrator interactions;
- import, migration, and rollback needs;
- license obligations for copied assets or code.

If the source, expected behavior, or target EmDash environment is missing, report the gap instead of inventing an equivalent.

## Assign each responsibility

The rest: https://github.com/emdash-cms/emdash/blob/HEAD/skills/wordpress-plugin-to-emdash/SKILL.md