component-context-generator

PrestaShop Component CONTEXT.md Generator

Purpose

Generate a lean, accurate CONTEXT.md for a PrestaShop shared component (src/Core/{Name}/ + src/Adapter/{Name}/) by exploring the real codebase.

Components are not business domains — they have no CQRS structure. They provide shared infrastructure consumed by many domains.

Output format

Principle: paths not inventories. Class names are greppable on demand. What earns tokens is:

• The layer table (where to look)
• Non-obvious patterns (things that would surprise a competent PHP developer)

# {Component Name} Component

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

## Purpose

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

## Layers

| Layer | Path |
|-------|------|
| {layer name} | {path} |

## Non-obvious patterns

- {bullet: surprising architectural decision, gotcha, or non-obvious constraint}

## Canonical examples

- {file path — 1-line role}

## Skills

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

## Related

- [{Component}]({path}) — {why related}

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

Do NOT include: ## Coding standards, ## Do, ## Don't, ## Testing expectations, ## Architecture overview with verbose subsections. These inflate token cost without adding value.

Target size: 20–35 lines.

---

Step-by-step process

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

• Component → src/Core/{Name}/ with NO Command/, Query/, Handler/ subdirectories at root
• Domain → src/Core/Domain/{Name}/ — use domain-context-generator instead

2. Explore the codebase

Use the Explore agent (thoroughness: very thorough) to map:

• src/Core/{Name}/ — interfaces, abstract classes, key concrete classes
• src/Adapter/{Name}/ — concrete implementations, legacy bridges
• Grep for the component's main interface across src/Core/Domain/ and src/PrestaShopBundle/ — identify 2–3 representative consumers
• Note any sub-patterns with a non-obvious design decision