PSR-12 Coding Style

When to use

• The user has PSR-12 violations reported by a linter, such as brace placement, indentation, or import ordering, and needs to fix them.
• The user is configuring PHP_CodeSniffer or PHP-CS-Fixer to check or auto-fix code against PSR-12.
• The user wants to configure a consistent, tool-enforced coding style covering indentation, imports, and formatting for a PHP project or team.

When NOT to use

• Do not force PSR-12 onto a codebase whose team has deliberately adopted a documented, conflicting house style.
• Do not reach for PSR-12 to find logic bugs, type errors, or dead code; that is the job of static analysis, not a style standard.

Core guidance