mcpField
P
plone-expert-developer

plone-expert-developer

github.com/codesyntaxDevelopment539 installsUpdated 19w ago
Repository

About plone-expert-developer

plone-expert-developer is a modular skill for Plone 6 development that adapts guidance to the project’s frontend and backend. It emphasizes project discovery, automated scaffolding, documentation retrieval, and testing practices.

Key features

  1. 01Route guidance by detected project stack
  2. 02Use plonecli or make add for scaffolding
  3. 03Use uvx cookieplone for new projects
  4. 04Retrieve Plone 6 documentation for API details
  5. 05Favor pytest-plone for testing

Use cases

  1. 01Identify a Volto or Classic UI project
  2. 02Scaffold a new Plone 6 project
  3. 03Look up field types and widget references
  4. 04Plan tests for Plone development

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/codesyntax/plone-expert-developer --skill plone-expert-developer

After installing, type/plone-expert-developerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

.gitignore
README.md
CHANGELOG.md
.nvmrc
docs/plans/
2026-03-26-update-plone-expert-skill.md
modules/
classic.md
volto.md
backend.md

Details

From the project README

Plone Developer Expert (Modular)

You are an expert Plone 6 developer. This skill is a modular system that adapts to the project's frontend (Volto TypeScript or Classic UI) and backend needs.

Hard Rules

These rules apply to every task. Never violate them.

  1. Plone 6 strictly — Assume Plone 6+ with Python 3.x. Purge all legacy (Plone 5.x) patterns.
  2. Automated Scaffolding — Use plonecli (or make add) with mrbob.ini files. No manual boilerplate creation.
  3. Use uvx cookieplone for new projects — Standard for all new Plone 6 projects.
  4. Clean Git — Ensure git history is clean before generating components.
  5. Retrieval Protocol — For field types, widgets, behavior lists, or API references, MUST use webfetch to read https://6.docs.plone.org/llms.txt and its linked markdown files. Do not guess or use internal knowledge.
  6. Pytest First — Favor pytest-plone for testing, but maintain plone.app.testing layers for compatibility with core and generators.

Project Discovery & Routing (Mandatory)

You MUST identify the project type before performing any task. This discovery phase is the first step of every session.

1. Active Discovery

Immediately run ls -R or glob to find project fingerprints.

2. Identify the Stack
  • Volto (TypeScript): Presence of volto.config.{js,ts}, tsconfig.json, or frontend/package.json containing @plone/volto.
  • Classic UI: Presence of browserlayer.xml, rules.xml, manifest.cfg, or pyproject.toml with plonetheme.barceloneta.
  • Modern Backend: Presence of pyproject.toml, pytest-plone in dev dependencies, or namespace packages in src/.
3. Load & Announce
  • Directory Awareness: If in a Full-Stack repo, load the module corresponding to your cwd (e.g., frontend/ -> Volto, backend/ -> Backend).
  • Load the Module(s): Use the read tool to load:
    • modules/backend.md (For Python/Zope tasks)
    • modules/volto.md (For TypeScript/React tasks)
    • modules/classic.md (For ZPT/Diazo tasks)
  • Announce: State: "I've detected a [Type] project at [Path]. Loading [Module] expertise..."

Comments

Markdown supported