php

ACTIVATE when writing PHP classes, DTOs, or value objects in a PHP 8.2+ project. Covers: mandatory readonly class usage (class-level, not per-property). DO NOT use for: general PHP syntax, PHP 8.3 features (see php-8.3).

ACTIVATE when writing PHP class constants in a PHP 8.3+ project. Covers: mandatory typed class constants. DO NOT use for: general PHP syntax, PHP 8.2 features (see php-8.2).

ACTIVATE whenever writing or modifying PHP code in src/, creating controllers, services, repositories, specifications, or any production PHP class. ACTIVATE for code review, formatting questions, or 'coding standards'. Covers: project-specific spacing rules around control structures, early return patterns, no empty() policy, constructor parameter ordering, nowdoc conventions. These rules go BEYOND PSR-12/PER. DO NOT use for: test code conventions (see php-test-conventions), SQL formatting (see php-sql-conventions).

ACTIVATE when modifying composer.json, adding/updating dependencies, or running composer commands. ACTIVATE for 'composer require', 'composer update', version constraints. Covers: caret versioning policy, forbidden patterns (*, dev-master, exact versions), internal package exception (dev-main as x.y.z), update strategy. DO NOT use for: autoloading, PHP code, Symfony configuration.

ACTIVATE when writing or modifying domain layer code, creating value objects, specifications, domain services, or domain interfaces. ACTIVATE when 'domain', 'DDD', 'hexagonal', 'ports and adapters', or 'domain purity' appears. Covers: strict domain layer purity rules — what is forbidden vs allowed in the domain layer, SPI interface pattern. DO NOT use for: infrastructure/controller code, Doctrine mapping, general architecture questions.

ACTIVATE when designing PHP classes, value objects, collections, or when the user asks about object design, encapsulation, or 'Tell Don't Ask'. Covers: Tell Don't Ask with concrete PHP examples, collection over named properties, Whole Object pattern, IteratorAggregate, self-describing value objects. DO NOT use for: refactoring methodology (see php-refactoring), DDD domain modeling (see php-ddd-conventions).

ACTIVATE when implementing form handling, POST endpoints, or any controller that modifies data. ACTIVATE for 'form submission', 'POST redirect', 'PRG', 'duplicate submission'. Covers: POST success -> always redirect, POST error -> re-render (no redirect), flash messages after redirect. DO NOT use for: FormType design (see php-symfony-form), API endpoints returning JSON.

ACTIVATE when the user wants to refactor, redesign, extract classes/value objects, or restructure PHP code. ACTIVATE for 'refactor', 'extract', 'redesign', 'simplify', or 'clean up' requests. Covers: mandatory end-to-end flow analysis before refactoring, consumer-driven value object design, imports as coupling signals. DO NOT use for: writing new features from scratch (see php-tdd-workflow), general OOP principles (see php-oop).

ACTIVATE when writing SQL queries in PHP code, using Doctrine DBAL, or formatting database queries. ACTIVATE for 'SQL', 'query', 'DBAL', 'JOIN', 'SELECT'. Covers: query direction convention (start from known entity), nowdoc formatting for SQL, column listing, JOIN ordering. DO NOT use for: Doctrine ORM/DQL, database migrations, general PHP code conventions.

ACTIVATE when working with Symfony FormTypes, form handling, data_class, DataTransformers, form options, or property_path. ACTIVATE when creating or modifying any FormType class. Covers: data_class as single source of truth (no data in options), DataTransformer placement (not controller), property_path for collection mapping. DO NOT use for: form submission flow/PRG (see php-prg-pattern), form validation rules, general Symfony questions.

ACTIVATE when the user wants to build, implement, or develop any new feature, endpoint, or user story using TDD, test-first, or red-green-refactor methodology. ACTIVATE for the '/feature-dev' command. ACTIVATE whenever 'TDD', 'test first', 'red-green-refactor', or 'itérations' appears alongside building something new. Covers: breaking features into small cross-layer TDD iterations, the red-green-refactor cycle, keeping the app working after each step, bug-fix-first-test workflow. DO NOT use for: writing a single test for existing code, test naming conventions (see php-test-conventions), general PHP/Symfony questions.

ACTIVATE when writing or modifying PHPUnit tests, creating test classes, using Prophecy, test factories, or data providers. ACTIVATE for 'test naming', 'test doubles', 'DAMP', 'spy vs mock', 'test organization'. Covers: DAMP over DRY, Spy over Mock (AAA), exception test naming, what NOT to test, factory methods, assertion patterns. DO NOT use for: TDD workflow/iteration process (see php-tdd-workflow), Symfony form testing setup.

ACTIVATE when writing or modifying Twig templates, using Twig components (twig:*), handling translations in Twig, or debugging translation issues. ACTIVATE whenever 'trans_default_domain', 'twig component', or 'translation not working' appears. Covers: trans_default_domain isolation in Twig components (critical pitfall), ClockInterface for dates in templates. DO NOT use for: Twig syntax basics, Symfony controller rendering, CSS/HTML questions.