agentleFS
Sign inStart free
eeaeea/eea.agent.skills/skills/plone-backend-developer/SKILL.md

plone-backend-developer

Skill7 starsChanged 6 months agoMITView on GitHub

Senior Plone backend development for EEA projects. Use when working on Plone 6 server behavior, backend add-ons, Python code, configuration, debugging, or tests in any EEA Plone project.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Read the project AGENTS.md for project-specific commands.

    line 24
  2. Very specific:

    Read the Makefile (make help) and the build configuration (sources.ini, requirements.txt, constraints.txt, or pyproject.toml).

    line 25
  3. Very specific:

    Check whether a develop/ directory exists.

    line 28
  4. Distinctive:

    Add or update a backend add-on and refresh the dev sources with the project's develop target.

    line 45
  5. Distinctive:

    Keep changes small and add targeted tests for regressions.

    line 57
  6. Distinctive:

    Prefer configuration and existing add-ons over fork-and-patch.

    line 58
  7. Distinctive:

    Do not edit generated build artifacts.

    line 59
  8. Very specific:

    Use references/plone-project-layouts.md for the known EEA backend layouts, commands, and how to discover them.

    line 63
  9. Very specific:

    Run the project's targeted test command, typically bin/zope-testrunner --test-path sources/<package> from the dev environment root, or the …

    line 68

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Plone Backend Developer

Overview

Implement and debug Plone 6 backend changes in EEA projects. EEA backends are built and started in different ways depending on the project generation, so discover the project's build system before running or editing anything.

Discover the project first

  • Read the project AGENTS.md for project-specific commands.
  • Read the Makefile (make help) and the build configuration (sources.ini, requirements.txt, constraints.txt, or pyproject.toml).
  • Identify how the dev environment is created and how the app is started.
  • Check whether a develop/ directory exists; if not, the backend is likely container-based.

See references/plone-project-layouts.md for the known EEA layouts.

Core workflow

  1. Confirm the failing endpoint, request path, and expected behavior.
  2. Locate the relevant package in the project's sources list or installed add-ons.
  3. Reproduce locally; add minimal logging only when needed.
  4. Apply the fix in the add-on or configuration.
  5. Restart Plone after Python changes; hot reload is not available.
  6. Validate with a targeted zope-testrunner invocation or manual verification.

Common tasks

  • Add or update a backend add-on and refresh the dev sources with the project's develop target.
  • Adjust Plone configuration and verify the app starts.
  • Investigate errors from the WSGI process and trace back to the relevant add-on module.
  • Work with REST API behavior used by the Volto frontend; confirm the exact endpoint contract before changing serializers.

Good practices

  • Restart Plone after Python changes; use the reload endpoint (@@reload) only for quick iteration, then restart to confirm.
  • Keep changes small and add targeted tests for regressions.
  • Prefer configuration and existing add-ons over fork-and-patch.
  • Do not edit generated build artifacts; edit sources and re-run bootstrap.

Repo context

Use references/plone-project-layouts.md for the known EEA backend layouts, commands, and how to discover them.

Verification

Run the project's targeted test command, typically bin/zope-testrunner --test-path sources/<package> from the dev environment root, or the equivalent documented by the project. Report what you ran.

<!-- BEGIN EEA-OVERRIDES -->

EEA-Specific Overrides

<!-- EEA-Overrides-Version: 1.0 --><!-- Last-Sync: 2026-09-18 -->

EEA-wide backend policy

Plone version

EEA projects run Plone 6.x. Read the exact version from the project's pins (constraints.txt, requirements.txt, or pyproject.toml) instead of assuming.

Persistence

Production EEA Plone deployments use RelStorage (PostgreSQL) rather than the default ZODB file storage. When reproducing production behavior, prefer the project's RelStorage target when it exists.

Release and CI

Backend releases and quality gates run through Jenkins. See jenkins-pipeline, code-quality, and testing for the CI contract and command parity.

Handoff to other EEA skills

  • Frontend/Volto behavior → plone-frontend-developer, volto-cypress-writer
  • CI and quality gates → jenkins-pipeline, code-quality, testing
<!-- END EEA-OVERRIDES --><!-- Merged Build: upstream SKILL.md + EEA-OVERRIDES.md --><!-- Auto-generated by scripts/build.sh - DO NOT EDIT DIRECTLY --><!-- Source: https://github.com/eea/eea.agent.skills -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free