domain-context-generator

PrestaShop Domain CONTEXT.md Generator

Purpose

Generate a minimal, accurate CONTEXT.md for a PrestaShop business domain (src/Core/Domain/{Name}/). The goal is the smallest file that gives an AI agent enough orientation to work in the domain — not an inventory of every class.

Output format

# {Domain} Domain

> **Status:** Draft — this context file is a starting point and should be refined by domain experts.

## Purpose

{1–2 sentences: what this domain does and what it does NOT do}

## Layers

| Layer | Path |
|-------|------|
| Core CQRS | `src/Core/Domain/{Name}/` — Commands, Queries, QueryResults, ValueObjects, Exceptions |
| Adapter | `src/Adapter/{Name}/` — handler implementations, repositories |
| Legacy ObjectModel | `classes/{Name}.php` ({N} lines) — do not add logic here |
| Back-office UI | controller path, grid factory name, TS frontend path |

## Non-obvious patterns

- {Things that aren't discoverable by reading the directory structure}
- {Surprising abstractions, delegation chains, cross-domain flows, legacy gotchas}

## Canonical examples

- `path/to/Command.php` + `path/to/Handler.php`
- `path/to/Query.php` + `path/to/ResultDTO.php`

## Skills

- [`skill-name`](../../skills/skill-name/SKILL.md) — one-line description

## Related

- [Component/Domain](path) — one-line reason

## Skills is optional — only include it if a skill in .ai/skills/ targets this domain. Omit the section entirely if no relevant skill exists.

Do NOT include: class name inventories (command names, exception names, value object names, handler names). These are greppable on demand and waste context tokens.

Do NOT include: ## Coding standards, ## Do, ## Don't, ## Testing expectations — project-wide, live in .ai/CONTEXT.md.

---

Step-by-step process

0. Confirm the target is a Domain, not a Component

Check that src/Core/Domain/{Name}/ exists and contains a CQRS structure (Command/, Query/, or handler interfaces). If you don't find a dedicated CQRS layer or a Controller for this domain, it is probably a Component — use the component-context-generator skill instead.