plone-frontend-developer
Senior Plone Volto frontend engineering for debugging Volto add-ons, fixing UI bugs, adjusting blocks/components, and handling all Plone 6.1 + Volto 17 frontend tasks (theme, routing, tokens, build/test issues). Use when the request involves Volto/Plone frontend behavior, add-on code, or UI fixes.
📖 中文导读:Senior Plone Volto frontend engineering for debugging Volto add-ons, fixing UI bugs, adjusting blocks/components, and handling all Plone 6.1 + Volto 17 frontend tasks (theme, routing, tokens, build/test issues). Use when the request involves Volto/Plone frontend behavior, add-on code, or UI fixes. 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: plone-frontend-developer description: Senior Plone Volto frontend engineering for debugging Volto add-ons, fixing UI bugs, adjusting blocks/components, and handling all Plone 6.1 + Volto 17 frontend tasks (theme, routing, tokens, build/test issues). Use when the request involves Volto/Plone frontend behavior, add-on code, or UI fixes.
Plone Frontend Developer
Overview
Diagnose and fix Volto/Plone frontend issues with a production-grade workflow. Use repo-specific guidance from references/eea-website-frontend.md.
Core workflow
- Clarify the symptom, the affected URL, and the expected behavior. Note the language/locale if the site is multilingual.
- Locate the code path in
frontend/src/or a local add-on infrontend/src/addons/. Always checkfrontend/src/customizations/for overrides. - Reproduce and isolate: use minimal changes, add short-lived logs if needed, and confirm the exact component/block responsible.
- Implement the fix in the most appropriate layer (customization first, then add-on). Favor tokenized values and shared helpers when updating styles.
- Verify with the smallest relevant check (unit test, lint, or targeted runtime verification), and note any follow-ups.
Common tasks
- Debugging a Volto add-on: find the add-on entry in
frontend/package.jsonand trace the component infrontend/src/addons/ornode_modules/. - Fixing UI behavior: inspect the relevant component in
frontend/src/components/or its customization; adjust props/state and verify routing logic infrontend/src/routes.jsif needed. - Token updates: replace hard-coded values with design tokens and update shared theme/config entries to keep consistency.
- Multilingual links: check locale-aware routing and URL generation before hardcoding language paths.
Good practices
- For new features, add or update Cypress and/or Jest coverage.
- When modifying add-ons, run
make lintinside the add-on folder. - Add-ons live in
frontend/src/addons/; check each add-on'smake helpfor available targets. - After defining i18n messages, run
make i18n. - Use Playwright MCP for quick UI verification when needed; Volto hot reload covers most changes.
- If adding new shadow customizations, ask to restart the frontend server.
Repo context
Use references/eea-website-frontend.md for environment details, repo layout, and commands.
Notes
- Prefer readable, minimal diffs and avoid refactors unless they are required for the fix.
- Keep temporary logs out of the final patch.
- When unsure about conventions, inspect nearby code or similar components in this repo.