Claude Code plugin for Plooma — install, upgrade, deploy via SSH, manage remote content, and convert static templates into Plooma themes. Six skills covering the full lifecycle of a Plooma project.
Install Plooma (formerly Plooma CMS) (elleven-digital/plooma) into the current directory FROM SCRATCH. Downloads the latest released version as a tarball, gathers DB and admin credentials interactively, writes `.env`, runs the bundled installer (migrations + initial user + per-project files), and records the installed version in `.plooma-version` so future upgrades work without depending on git. Use this skill whenever the user wants a fresh install — phrases like "instala o plooma aqui", "set up plooma-cms in this folder", "bootstrap plooma", "create a new plooma project", "i just want a working plooma-cms here", "instalar o plooma nessa pasta". Triggers in Portuguese and English. Do NOT use when: (a) converting static HTML/PHP into a theme — that's plooma:theme-convert, (b) updating/upgrading an existing Plooma install to a newer version, (c) running specific CLI commands like `bin/plooma migrate` or `page:sync` on a project that's already installed, (d) answering reference questions about Plooma's schema, helpers, fields, options, or features. Mentioning Plooma-specific keywords like "plooma", "site.json", or "field()" alone does NOT trigger this skill — only explicit setup/install/bootstrap intent does.
Update content on a Plooma (formerly Plooma CMS) site that's deployed on a remote server, via SSH. Creates/edits/publishes posts, services, pages, and any other content type defined in the site's `theme/site.json` — schema-aware, so it works on ANY Plooma site without knowing fields ahead of time. Reuses `.deploy/ssh.json` from plooma:ssh-deploy/plooma:ssh-download. Backs up the affected database tables before any write. Triggers whenever the user wants to manage live content remotely — phrases like "cria um post no blog do site X", "publica esse draft", "muda o texto do hero da home", "atualiza a página de serviços", "lista os drafts", "edita o post sobre Y", "altera o eyebrow do site", "create a blog post on the deployed site", "publish all drafts", "edit the about page on production". Triggers in Portuguese and English. The skill discovers types and fields at runtime by calling `bin/plooma item:types` and `bin/plooma <kind>:schema` on the remote, so it adapts to whatever the site has — posts, services, cases, events, team members, pages with custom fields, etc. Do NOT use for: (a) bulk media uploads (out of scope — use admin), (b) changing the schema itself / adding new content types (that's `theme/site.json`, edit locally and deploy), (c) editing templates or theme code (use a code editor + plooma:ssh-deploy), (d) sites that are NOT deployed remotely yet (use the local admin or a local-only content skill).
Deploy Plooma (formerly Plooma CMS) to ANY host with SSH access via three actions — (1) `init` for first-time deploy of a complete Plooma project (files + database + storage + theme + robots.txt with the correct production URL); (2) `update-cms` for pushing core/Plooma changes and running pending DB migrations remotely; (3) `update-theme` for pushing theme-only changes and running schema:validate + page:sync remotely. Works on Hostinger, cPanel-based hosts (Locaweb, HostGator, KingHost, A2, SiteGround, Bluehost), DreamHost, VPS providers (DigitalOcean, Linode, Hetzner, Vultr), cloud VMs (AWS Lightsail/EC2, GCP, Azure) — anywhere with SSH + key auth + MySQL/MariaDB. ALWAYS inspects the target hosting path FIRST and refuses to overwrite an existing Plooma install — if `core/Bootstrap.php` is present at the target, only `update-cms` and `update-theme` are offered. On first run asks the user for SSH credentials, the absolute remote path where Plooma will live, the canonical site URL, and DB credentials, then saves them to `.deploy/ssh.json` (chmod 0600, gitignored) so subsequent deploys are fully automated. Use this skill whenever the user wants to push, deploy, ship, send, upload, or sincronizar their Plooma project to a remote server — phrases like "sobe esse projeto na hostinger", "deploy do plooma", "publica na locaweb", "atualiza o tema em prod", "push do cms", "send to my VPS", "publish plooma", "sobe pro DigitalOcean", "deploy plooma via ssh". Triggers in Portuguese and English. Do NOT trigger for: deploys to PaaS without SSH (Vercel/Netlify/Heroku/Cloud Run), creating a Plooma install from scratch (that's plooma:install), converting templates to a Plooma theme (that's plooma:theme-convert), or local-only Plooma work (editing site.json, running migrations locally). The signal is "Plooma" + a deploy verb (deploy/sobe/atualiza/push/publish) targeting a server reachable by SSH.
Pull a deployed Plooma (formerly Plooma CMS) project from a remote server down to the current local folder — files + database + media uploads — for local debugging, dev parity, or moving a site to a new machine. Inverse of plooma:ssh-deploy. Two modes detected automatically: (A) **first-time** when current folder is empty, asks SSH + remote path + local DB credentials, downloads, configures `.env` for localhost, saves config to `.deploy/ssh.json`; (B) **refresh** when the current folder already has a Plooma install with `.deploy/ssh.json`, reuses everything, then DESTRUCTIVELY replaces the local copy with an exact mirror of the remote (drops + recreates local DB, deletes ALL local files including `theme/`, `storage/`, `.git/`, the live `.env` and `.htaccess`), bringing back only environment variables adjusted to the local context. Always backs up the local state to `/tmp/plooma-download-backup-<timestamp>/` before any destructive operation, so the user has a recovery window. Use this skill whenever the user wants to bring production down to local — phrases like "baixa o plooma da hostinger", "pull do servidor pro meu pc", "baixa o site de produção", "clona o plooma que tá no servidor pra cá", "preciso debugar local com os dados de produção", "sync from server to local", "mirror prod locally", "download my plooma site from VPS". Triggers in Portuguese and English. Do NOT use for: (a) deploying TO a server (that's plooma:ssh-deploy), (b) installing fresh Plooma with no remote source (that's plooma:install), (c) downloading just the database (user can run `mysqldump` over SSH directly for that), (d) syncing only files without the DB (this skill is all-or-nothing — full mirror).
Convert a folder of static HTML/PHP templates into a Plooma (formerly Plooma CMS) theme. Reads pages in the current directory, extracts shared header/footer into partials, identifies editable fields (titles, hero copy, images, repeating blocks), proposes a `site.json` schema with pages and item types, then generates Plooma-compatible PHP templates with `field()`, `option()`, `image_url()`, and other Plooma helpers wired in. Also pre-populates the admin panel with the same content that was hardcoded in the source — pages, items, taxonomy terms, and global options — via a one-shot seed script, so the user opens admin to a populated site, not empty fields. If the current directory is NOT inside an existing Plooma install, this skill creates `./theme/`, moves the source files there, then auto-installs Plooma (delegates to plooma:install) before doing the conversion. Use this skill whenever the user has static HTML/PHP files (a downloaded template, a static site, a design mockup with markup) and wants to turn them into a Plooma theme — phrases like "transforma esses html em tema do plooma", "converte essa pasta de templates para plooma", "vira isso aqui em theme", "tenho um modelo estático e quero usar no plooma cms", "build a plooma theme from these html files". Triggers in Portuguese and English. Always operates in plan-then-execute mode: produces a full mapping (files → pages, blocks → fields, partials, options) for user approval before generating any output. Do NOT use for: (a) installing a fresh Plooma without conversion (that's plooma:install), (b) modifying an already-converted theme, (c) editing site.json schema in an established project, (d) answering questions about Plooma helpers/syntax. Mentioning HTML, PHP, or themes alone does NOT trigger — only explicit conversion intent does.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Six skills covering the full lifecycle of a Plooma project: install, upgrade, deploy via SSH, manage remote content, download a deployed site back to local, and convert static templates into Plooma themes.
Triggers in Portuguese and English.
Clone into ~/.claude/skills/ so Claude Code picks up the skills:
cd ~/.claude/skills
git clone https://github.com/elleven-digital/plooma-plugin.git plooma
find plooma/skills -name "*.sh" -exec chmod +x {} \;
Restart your Claude Code session (or start a new one) and the skills will be available as plooma:install, plooma:upgrade, etc.
To update later: cd ~/.claude/skills/plooma && git pull.
| Skill | What it does |
|---|---|
plooma:install | Fresh install of Plooma into the current directory. Downloads latest release tarball, gathers DB + admin credentials, writes .env, runs installer, records version in .plooma-version. |
plooma:upgrade | Upgrade an existing Plooma install. Reads .plooma-version, fetches latest tag from GitHub, replaces only engine paths declared in engine-manifest.json, runs new migrations. Preserves theme/, storage/, .env, .deploy/, .claude/, etc. |
plooma:theme-convert | Convert a folder of static HTML/PHP templates into a Plooma theme. Extracts shared header/footer, identifies editable fields, proposes a site.json schema, generates Plooma-compatible templates with field()/option()/image_url() wired in, seeds the admin panel with the original content. |
plooma:ssh-deploy | Deploy to any host with SSH access (Hostinger, cPanel hosts, DigitalOcean, AWS, etc). Three actions: init (first-time deploy of files + DB + storage + theme), update-cms (push core + run migrations remotely), update-theme (push theme + run schema:validate and page:sync remotely). Saves config to .deploy/ssh.json. |
plooma:ssh-download | Pull a deployed Plooma project back to local — files + DB + media. Inverse of ssh-deploy. Two modes: first-time (asks SSH + local DB credentials) and refresh (destructively mirrors remote into existing local install, backing up first). |
plooma:ssh-content | Manage live content on a deployed Plooma site via SSH. Schema-aware via bin/plooma item:types/item:schema — works on any Plooma site without hard-coding field names. Backs up tables before any write. |
plooma:install ← create a fresh Plooma project locally
plooma:theme-convert ← (optional) bring a static template in as the theme
plooma:ssh-deploy ← init: first deploy to your server
plooma:ssh-content ← create/edit posts, services, pages on prod
plooma:ssh-download ← later: pull prod back to local to debug
plooma:upgrade ← keep the engine current
plooma:ssh-deploy ← update-cms: push the upgrade to prod
php, mysql client, rsync, ssh, curl, jq, tarssh-* skills): SSH with key-based auth, MySQL/MariaDB, PHP ≥ 8.2plooma-plugin/
├── .claude-plugin/
│ └── plugin.json
├── README.md
├── shared/
│ └── ssh-lib.sh ← SSH/rsync/MySQL helpers used by all ssh-* skills
└── skills/
├── install/
├── upgrade/
├── theme-convert/
├── ssh-deploy/ ← scripts/_lib.sh is a thin shim that sources shared/
├── ssh-download/ ← scripts/_lib.sh is a thin shim that sources shared/
└── ssh-content/ ← scripts/_lib.sh is a thin shim that sources shared/
Each skill has its own SKILL.md (the instructions Claude reads) and, where applicable, a scripts/ folder with the bash helpers it runs.
The three ssh-* skills all read the same .deploy/ssh.json and share SSH command building, rsync/scp targeting, DB credentials parsing, and remote-path resolution. Those helpers live in shared/ssh-lib.sh. Each skill's scripts/_lib.sh is a short shim that sources the shared lib and defines a skill-specific parse_args() (since each skill accepts a different set of flags). A bug fix or feature in the shared layer benefits all three skills at once.
The plugin version tracks Plooma releases: plugin v1.x.y is tested against Plooma v1.x.y. The skills are forward-compatible with patch releases of Plooma, but you may want to upgrade the plugin alongside major/minor releases of Plooma itself.
npx claudepluginhub elleven-digital/claude-marketplace --plugin ploomaComprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Permanent coding companion for Claude Code — survives any update. MCP-based terminal pet with ASCII art, stats, reactions, and personality.
UI/UX design intelligence. 67 styles, 161 palettes, 57 font pairings, 25 charts, 15 stacks (React, Next.js, Vue, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Nuxt, Jetpack Compose). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
This skill should be used when users need to generate ideas, explore creative solutions, or systematically brainstorm approaches to problems. Use when users request help with ideation, content planning, product features, marketing campaigns, strategic planning, creative writing, or any task requiring structured idea generation. The skill provides 30+ research-validated prompt patterns across 14 categories with exact templates, success metrics, and domain-specific applications.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.