Agent skill · writing content · github
content-management-systems
Workflow for building and modifying content management systems across WordPress, Shopify, Wix, Squarespace, Drupal, WooCommerce, Joomla, HubSpot CMS Hub, Webflow, Adobe Experience Manager, and similar platforms. Use when working on CMS themes, plugins, apps, modules, admin panels, media uploads, content models, editors, markdown pipelines, or static export workflows.
Why this skill is useful
Provides domain-specific workflows and best practices for managing various content management systems that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Content Management Systems Use this skill when the user is working on a content management system or on software that behaves like one. This skill focuses on the seams that matter in CMS work: themes and templates plugins, apps, modules, and extensions admin and editor interfaces media and upload handling content models, taxonomy, and metadata render pipelines and static export flows When to Use This Skill The user mentions a CMS platform such as WordPress, Shopify, Drupal, Joomla, Webflow, Squarespace, Wix, WooCommerce, HubSpot CMS Hub, or Adobe Experience Manager. The task is about theme development, template changes, or design system work inside a CMS. The task is about plugins, modules, apps, or extension points. The task touches editor UX, previews, taxonomy, slugs, SEO fields, or publishing behavior. The task involves uploads, media libraries, authored assets, markdown rendering, or static export. First Pass 1. Identify the platform category: self-hosted CMS, SaaS site builder, commerce platform, or hybrid/headless system. 2. Find the owning implementation seam before editing: theme or template layer plugin, app, module, or extension layer admin or editor surface content model or storage layer media pipeline export, deploy, or rendering pipeline 3. Check platform constraints before choosing an approach: what is editable locally what is authored content versus code where media belongs whether the final site is server-rendered, static-exported, or hosted remotely CMS Rules Follow the platform's naming and folder conventions for themes, modules, template parts, or sections. Keep theme assets separate from user-uploaded media unless the platform explicitly combines them. Prefer structured content fields over storing important metadata inside presentation markup. Treat previews, slugs, taxonomy, excerpts, meta fields, and publish states as first-class CMS concerns. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/content-management-systems