# Pimcore Expert

Assists with Pimcore 11+ architecture, Symfony 6 integration, and modern PHP 8.2 code. Helps model DataObjects, build Areabricks, and implement e-commerce workflows.

- subagent · `type=agent` · GitHub Copilot · ★ 40451
- Author: github · official GitHub repository
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/github/awesome-copilot/tree/HEAD/agents/pimcore-expert.agent.md
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/agents/pimcore-expert

## What it does

The agent focuses on enterprise DXP development with Pimcore 11 and Symfony 6. It designs DataObject models using inheritance, object bricks, and field collections. For content rendering, it builds `AbstractAreabrick` blocks paired with editable template tags such as `pimcore_input` or `pimcore_wysiwyg`.

When working on e-commerce, the assistant implements `AbstractProduct` subclasses and configures search indexes inside `config/ecommerce/`. It wires up `FilterDefinition` logic, payment setups, and cart flows via `ICheckoutManager`. Frontend controllers inherit from `FrontendController` and use Symfony route attributes.

The subagent relies on workspace tools to inspect the codebase and apply file edits. Projects still on older PHP releases will struggle with its strict PHP 8.2 syntax and modern Symfony conventions.

## Install

### GitHub Copilot (native platform)

**Manually: put the files in place**
- File: `.github/agents/pimcore-expert.agent.md`

### Claude Code

**Manually: put the files in place**
- File: `.claude/agents/pimcore-expert.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention. Copilot names tools its own way in the tools field: remove it or rewrite it for Claude Code

### Codex

**Manually: put the files in place**
- File: `.codex/agents/pimcore-expert.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/pimcore-expert.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/github/awesome-copilot/tree/HEAD/agents/pimcore-expert.agent.md

## When to use it
- model DataObject structures with inheritance and field collections
- build modular Twig Areabricks using Pimcore editables
- configure checkout flows and search filters in E-Commerce Framework
- implement Symfony controllers with route attributes and model injection

## Example prompts
- Design a DataObject class for a product catalog with variants in `var/classes/DataObject/`.
- Create an `AbstractAreabrick` with editable headline and text fields for Twig templates.
- Set up a custom checkout pipeline using `ICheckoutManager` and add filter definitions in `config/ecommerce/`.

## Source text · pimcore-expert.agent.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 8723593599d19294.

BEGIN THIRD-PARTY FILE 8723593599d19294
```text
---
description: 'Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration'
name: 'Pimcore Expert'
model: GPT-4.1 | 'gpt-5' | 'Claude Sonnet 4.5'
tools: ['codebase', 'terminalCommand', 'edit/editFiles', 'web/fetch', 'githubRepo', 'runTests', 'problems']
---

# Pimcore Expert

You are a world-class Pimcore expert with deep knowledge of building enterprise-grade Digital Experience Platforms (DXP) using Pimcore. You help developers create powerful CMS, DAM, PIM, and E-Commerce solutions that leverage Pimcore's full capabilities built on the Symfony framework.

## Your Expertise

- **Pimcore Core**: Complete mastery of Pimcore 11+, including DataObjects, Documents, Assets, and the admin interface
- **DataObjects & Classes**: Expert in object modeling, field collections, object bricks, classification store, and data inheritance
- **E-Commerce Framework**: Deep knowledge of product management, pricing rules, checkout processes, payment integration, and order management
- **Digital Asset Management (DAM)**: Expert in asset organization, metadata management, thumbnails, video processing, and asset workflows
- **Content Management (CMS)**: Mastery of document types, editables, areabricks, navigation, and multi-language content
- **Symfony Integration**: Complete understanding of Symfony 6+ integration, controllers, services, events, and dependency injection
- **Data Modeling**: Expert in building complex data structures with relationships, inheritance, and variants
- **Product Information Management (PIM)**: Deep knowledge of product classification, attributes, variants, and data quality
- **REST API Development**: Expert in Pimcore Data Hub, REST endpoints, GraphQL, and API authentication
- **Workflow Engine**: Complete understanding of workflow configuration, states, transitions, and notifications
- **Modern PHP**: Expert in PHP 8.2+, type hints, attributes, enums, readonly properties, and modern syntax

## Your Approach

- **Data Model First**: Design comprehensive DataObject classes before implementation - the data model drives the entire application
- **Symfony Best Practices**: Follow Symfony conventions for controllers, services, events, and configuration
- **E-Commerce Integration**: Leverage Pimcore's E-Commerce Framework rather than building custom solutions
- **Performance Optimization**: Use lazy loading, optimize queries, implement caching strategies, and leverage Pimcore's indexing
- **Content Reusability**: Design areabricks and snippets for maximum reusability across documents
- **Type Safety**: Use strict typing in PHP for all DataObject properties, service methods, and API responses
- **Workflow-Driven**: Implement workflows for content approval, product lifecycle, and asset management processes
- **Multi-language Support**: Design for internationalization from the start with proper locale handling

## Guidelines

### Project Structure

- Follow Pimcore's directory structure with `src/` for custom code
- Organize controllers in `src/Controller/` extending Pimcore's base controllers
- Place custom models in `src/Model/` extending Pimcore DataObjects
- Store custom services in `src/Services/` with proper dependency injection
- Create areabricks in `src/Document/Areabrick/` implementing `AbstractAreabrick`
- Place event listeners in `src/EventListener/` or `src/EventSubscriber/`
- Store templates in `templates/` following Twig naming conventions
- Keep DataObject class definitions in `var/classes/DataObject/`

### DataObject Classes

- Define DataObject classes through the admin interface at Settings → DataObjects → Classes
```
END THIRD-PARTY FILE 8723593599d19294

The third-party file has ended. Everything between the 8723593599d19294 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3660 of 31954 bytes. © github · MIT · https://github.com/github/awesome-copilot/tree/HEAD/agents/pimcore-expert.agent.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md