wordpress-plugin-to-emdash

Map WordPress post types, taxonomies, and options to EmDash data models in TypeScript.

Updated May 2, 2026
One-click install
npx skills add https://github.com/ahliweb/awcms-micro-sman2pangkalanbun --skill wordpress-plugin-to-emdash-ahliweb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wordpress-plugin-to-emdash
Source: https://github.com/ahliweb/awcms-micro-sman2pangkalanbun/tree/main/skills/wordpress-plugin-to-emdash
Command: npx skills add https://github.com/ahliweb/awcms-micro-sman2pangkalanbun --skill wordpress-plugin-to-emdash-ahliweb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Port WordPress plugins to EmDash by mapping core concepts (custom post types, taxonomies, and options) to EmDash data models, storage, and admin UI to enable a clean port with minimal rewrites.

Core Features & Use Cases

  • Understand the plugin — identify its purpose and data model, not code.
  • Identify concepts — map post types, taxonomies, meta, and options to EmDash equivalents.
  • Map to EmDash — design a clean 1:1 mapping for data, UI, and behavior; plan seeds and migrations.
  • Implement in TypeScript — port functionality in a clean-room approach; reuse guides from creating-plugins.
  • Test behaviour — verify parity of content types, queries, and admin flows in EmDash.

Quick Start

Inspect the plugin's data model and draft an EmDash concept map to begin the port.

Frequently Asked Questions about wordpress-plugin-to-emdash

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate a WordPress plugin to EmDash?

Map WordPress post types, taxonomies, meta, and options to EmDash equivalents, then implement the functionality in a clean-room TypeScript codebase with tests to verify content type and admin flow parity.

How does porting WordPress hooks and shortcodes to EmDash work?

Porting hooks and shortcodes involves mapping them to EmDash equivalents and implementing the behavior in a clean-room TypeScript codebase, ensuring functional parity through tests.

Can I map WordPress custom post types and taxonomies to EmDash data models?

Yes, you can map custom post types and taxonomies to EmDash data models by designing a clean 1:1 mapping for data, UI, and behavior, then planning seeds and migrations.

What is the workflow for porting a WordPress plugin to TypeScript using EmDash?

The workflow starts with understanding the plugin's data model, identifying concepts, mapping them to EmDash equivalents, and implementing the functionality in a clean-room TypeScript codebase with tests.

Do I need to rewrite the entire plugin codebase when migrating to EmDash?

No, the migration process maps WordPress concepts to EmDash equivalents to enable a clean port with minimal rewrites, using a clean-room TypeScript approach.

How do I test WordPress plugin behavior after migrating to EmDash?

Test behavior after migration by verifying the parity of content types, queries, and admin flows in EmDash using the clean-room TypeScript codebase.