craft-php-guidelines

# Craft CMS 5 PHP Guidelines Complete PHP coding standards and conventions for active coding sessions. ## Common Pitfalls - `addSelect()` is the convention in `beforePrepare()` — safely additive when multiple extensions contribute columns. Craft's `**` placeholder merges defaults regardless, but `addSelect()` prevents conflicts. - `$_instances` is not a Craft convention — private properties use underscore prefix but meaningful names like `$_items`, `$_sections`. - Records use the **same class name** as models (namespace distinguishes). Alias when importing both: `use ...\records\MyEntity as MyEntityRecord;`. - Queue jobs have **no "Job" suffix** — `ResaveElements`, not `ResaveElementsJob`. - `declare(strict_types=1)` is NOT used in plugin source files. Only in standalone config files like `ecs.php`. - `@author` goes on classes and methods only — never on properties. - Don't use `string|null` — use `?string` (short nullable notation). - Forget `parent::defineRules()` and you lose all inherited validation. - `DateTimeHelper` in elements/queries, `Carbon` in services — never mix in the same class. - Missing `@throws` chains — document exceptions from called methods too, not just your own throws. ## Documentation - Official coding guidelines: https://craftcms.com/docs/5.x/extend/coding-guidelines.html - Class reference: https://docs.craftcms.com/api/v5/ - Generator reference: https://craftcms.com/docs/5.x/extend/generator.html When unsure about a convention, `web_fetch` the...