Bangun dan modifikasi theme, plugin, content model, serta admin interface di berbagai platform CMS seperti WordPress, Shopify, dan Webflow.
- Bintang GitHub
- 41.038
- File
- 2
- Commit terakhir
- 11 Nov 2026
- Lisensi
- MIT
- Tool yang diizinkan
- —
Apa fungsi skill content-management-systems?
content-management-systems adalah agent skill. Bangun dan modifikasi theme, plugin, content model, serta admin interface di berbagai platform CMS seperti WordPress, Shopify, dan Webflow.
Ringkasan dibuat dari SKILL.md skill ini.
Tentang skill content-management-systems
Skill ini memungkinkan Anda untuk mengembangkan theme, plugin, dan content model untuk platform seperti WordPress, Shopify, dan Webflow. Skill ini menyediakan workflow terstruktur bagi developer yang bekerja di berbagai lingkungan, termasuk sistem self-hosted, SaaS site builder, dan arsitektur headless. Agent harus memuat skill ini ketika tugas melibatkan modifikasi admin interface, pengelolaan upload media, atau penyesuaian taksonomi dan metadata di dalam content management system.
Skill ini berfokus pada identifikasi implementation seam yang tepat, seperti template layer, plugin extension point, atau content storage layer. Skill ini membantu menjaga konvensi spesifik platform untuk struktur folder dan penamaan, sambil memastikan logika presentasi tetap terpisah dari konten yang dibuat. Dengan mengikuti panduan ini, developer dapat mengelola tugas kompleks seperti markdown rendering pipeline, workflow static export, dan schema migration tanpa merusak batasan platform yang mendasarinya.
Apa yang bisa dilakukan agent dengannya
- 1Modifikasi template theme CMSPerbarui tata letak visual sebuah website dengan bekerja di dalam hierarki template spesifik platform tersebut.
- 2Kembangkan ekstensi platform kustomBuat fungsionalitas baru dengan menambahkan logika ke layer plugin, app, atau module yang sesuai.
- 3Kelola content model dan schemaDefinisikan dan migrasikan entitas konten terstruktur seperti produk, postingan, atau koleksi.
- 4Konfigurasi media dan path uploadAtur bagaimana aset yang dibuat dan gambar theme disimpan serta diakses.
Ditulis dari SKILL.md milik skill tersebut. Setiap use case diverifikasi dengan kutipan darinya.
Cara install skill content-management-systems
Setiap perintah menyalin folder skill ke direktori skills client. Restart client atau mulai sesi baru untuk memuatnya.Install skill content-management-systems di Claude Code
~/.claude/skills/content-management-systems/SKILL.md
$ npx degit github/awesome-copilot/skills/content-management-systems ~/.claude/skills/content-management-systemsInstall skill content-management-systems di Claude Code (project)
.claude/skills/content-management-systems/SKILL.md
$ npx degit github/awesome-copilot/skills/content-management-systems .claude/skills/content-management-systemsInstall skill content-management-systems di Codex
~/.agents/skills/content-management-systems/SKILL.md
$ npx degit github/awesome-copilot/skills/content-management-systems ~/.agents/skills/content-management-systemsInstall skill content-management-systems di Gemini CLI
~/.gemini/skills/content-management-systems/SKILL.md
$ npx degit github/awesome-copilot/skills/content-management-systems ~/.gemini/skills/content-management-systemsInstall skill content-management-systems di Claude.ai
npx degit github/awesome-copilot/skills/content-management-systems content-management-systems && zip -r content-management-systems.zip content-management-systems # claude.ai → Customize → Skills → + → Create skill → Upload a skill → content-management-systems.zip
Pengecekan otomatis
Berjalan 15 Nov 2026Laporan lengkap →Lolos cek otomatis kami. Ini bukan audit keamanan: baca skripnya sebelum membiarkan agent menjalankannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkaugithub/awesome-copilot/skills/content-management-systems is public and reachablegithub.com/github/awesome-copilot/tree/HEAD/skills/content-m ↗Lolos
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit 2026-11-11github.com/github/awesome-copilot/commits ↗Lolos
- Skrip tanpa unduh-lalu-jalankan atau pencurian kredensialNo scripts in the skill folderLolos
- Tidak ada instruksi tersembunyi di SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/github/awesome-copilot/blob/HEAD/skills/content-m ↗Lolos
- Tool yang diizinkan otomatis dibatasiNo pre-approved tools; the agent asks before using onegithub.com/github/awesome-copilot/blob/HEAD/skills/content-m ↗Lolos
- SKILL.md mengikuti format Agent SkillsValid name and description; says when to use it; 107 linesgithub.com/github/awesome-copilot/blob/HEAD/skills/content-m ↗Lolos
SKILL.md
Lihat di GitHubContent 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
- Identify the platform category: self-hosted CMS, SaaS site builder, commerce platform, or hybrid/headless system.
- 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
- 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.
- Prefer safe defaults and graceful fallback behavior when config, theme selection, or content input is invalid.
- When changing editor or admin behavior, trace the stored field, validation rules, preview path, and final render path together.
Common Workflows
Themes and Templates
- Start at the template loader or theme runtime, not at a downstream include.
- Preserve the platform's template hierarchy and partial naming conventions.
- Keep presentation changes close to templates and shared theme helpers.
Plugins, Apps, and Modules
- Add behavior at the platform's extension seam instead of scattering logic into templates.
- Keep migrations, seed data, and configuration updates explicit and versioned.
- Document the extension's setup assumptions when the platform requires activation or registration.
Admin and Editor UX
- Keep forms aligned with the stored content model.
- Prefer author-facing previews when content transformations are non-trivial.
- Keep validation, CSRF or equivalent safeguards, and permissions consistent with the surrounding admin code.
Media and Uploads
- Use a dedicated upload path for authored media.
- Keep decorative or theme-owned imagery in the active theme folder.
- Default to conventional locations like
uploads/for authored media andimg/for theme assets unless the platform dictates a stronger convention. - When a CMS supports configurable media directories, expose the setting with a safe fallback.
Content Models and Migrations
- Distinguish content entities clearly: pages, posts, products, entries, collections, taxonomies, and settings.
- Prefer migration files or exportable schema definitions over ad hoc runtime mutations.
- Keep slugs, publish dates, excerpts, canonical metadata, and taxonomy relations structured.
Markdown, HTML, and Static Export
- Decide whether markdown is authored input, intermediate content, or build output before changing the renderer.
- Pair renderer changes with preview or validation when feasible.
- For static-exported CMS systems, validate rewritten permalinks and asset paths after build changes.
Identifying the Owning Seam
Regardless of platform, locate the owning seam before editing by mapping the codebase to these CMS roles:
- Runtime bootstrap and request routing
- Admin or editor controllers and their view templates
- Theme loading, template hierarchy, and shared template helpers
- Repositories, models, or schema/migration files for content, taxonomy, and settings
- Markdown or content transformation utilities
- Static export, deploy, or render pipeline entry points
Step to the owning seam first, then make the smallest change that preserves the CMS structure.
Platform Notes
See references/cms-platform-workflows.md for a compact mapping of common CMS platforms, extension surfaces, and media conventions.
Berkas dalam skill ini
2Pertanyaan seputar skill content-management-systems
Bagaimana cara install skill content-management-systems di Claude Code?
Jalankan npx degit github/awesome-copilot/skills/content-management-systems ~/.claude/skills/content-management-systems. Claude Code memuat skill dari ~/.claude/skills (semua proyek) atau .claude/skills (satu proyek) dan menggunakan skill saat deskripsinya cocok dengan tugas.
Client mana saja yang bisa menggunakan skill content-management-systems?
Client apa pun yang membaca format Agent Skills: Claude Code, Codex, Gemini CLI, dan claude.ai (unggah sebagai ZIP). Script dalam skill hanya berjalan di client yang mengizinkan eksekusi kode.
Jenis platform CMS apa saja yang didukung oleh skill ini?
Skill ini bekerja dengan berbagai platform termasuk WordPress, Shopify, Wix, Squarespace, Drupal, WooCommerce, Joomla, HubSpot CMS Hub, Webflow, dan Adobe Experience Manager.
Bagaimana cara menangani aset media di dalam CMS?
Anda harus menggunakan path upload khusus untuk media yang dibuat (authored media) dan menyimpan gambar dekoratif atau milik theme di dalam folder theme yang aktif.
Apa pendekatan yang direkomendasikan untuk menambahkan fungsionalitas baru ke CMS?
Tambahkan perilaku pada extension seam platform alih-alih menyebarkan logika ke dalam template, dan pastikan migrasi serta pembaruan konfigurasi dilakukan secara eksplisit dan terversi.