Style terms
Consistency, readability, and the rules that make teams sane
Coding style is not about aesthetics — it is about communication. Consistent formatting, naming conventions, linting rules, and documentation standards reduce cognitive load and make code reviews faster and less painful. This category covers the conventions and tooling that help teams write code that reads as if one thoughtful person wrote it all.
More on Style
History
Code style emerged as a formal discipline in the 1980s and 1990s as software teams grew and version control systems became standard; early concerns centered on indentation, naming, and readability to reduce merge conflicts and maintenance costs. The PHP community formalized style guidance through the PHP Standards Recommendation (PSR) series starting in 2009, with PSR-1 and PSR-2 establishing baseline conventions that became widely adopted. Automated tooling—first PHP_CodeSniffer (2006), later PHP-CS-Fixer and Rector—shifted style enforcement from code review to CI/CD pipelines, eliminating manual bikeshedding and enabling consistent refactoring at scale. Modern practice has evolved to treat style as both a technical concern (linting, type hints, docblocks) and a team communication layer (commit messages, documentation standards, semantic versioning), with PSR-12 and static analysis tools like PHPStan becoming de facto standards in professional PHP development. Today style encompasses not just formatting but architectural clarity, making it foundational to code quality and team productivity.
Key concepts
- Naming Conventions
- PSR-1: Basic Coding Standard
- PSR-12 Coding Standard
- Code Documentation Standards
- Commit Message Best Practices
- Early Return Pattern
- Guard Clause Pattern
- PHP-CS-Fixer vs PHP_CodeSniffer
Best references
-
PSR Standards — PHP-FIG Official PHP Framework Interop Group specifications. Essential for understanding PSR-1, PSR-4, PSR-12, and other coding standards referenced throughout this category.
-
PHP-CS-Fixer Documentation Official reference for the most widely-used PHP code style fixer. Critical for implementing automated style enforcement in CI workflows.
-
PHPStan Documentation Canonical guide to PHPStan static analysis levels (0–9) and type checking. Directly supports understanding modern PHP type safety and code quality practices.
-
Conventional Commits Official specification for standardized commit message format. Foundation for commit message best practices and automated changelog generation.
✦ Latest in Style
Typed relationships here
Edges touching a Style term.
- PHPStan Levels 0–9 Explained Enables Dead Code Detection Sep 16
- Psalm Type Annotations Enforces Type Safety in PHP (strict_types & Static Analysis) Sep 16
- Fluent Naming for Boolean Methods Specializes Naming Conventions Sep 16
- Cognitive Complexity Measures Deep Nesting Sep 14
- Simplifying Complex Conditional Logic Complements Refactoring Boolean Flag Parameters Sep 14
🤖 AI Guestbook — Style educational data only
|
|
Last 30 days
Agents 0
No pings yet today
Amazonbot 7Google 6ChatGPT 6SEMrush 4Ahrefs 3PetalBot 3Bing 3Baidu 1Common Crawl 1
Amazonbot 720PetalBot 560Google 480Ahrefs 448SEMrush 431ChatGPT 417Perplexity 326Scrapy 300Bing 230Unknown AI 118Claude 112Applebot 103Twitter/X 95Brave Search 71Meta AI 47Majestic 35Common Crawl 34Sogou 34Yandex 31DuckDuckGo 24Baidu 15ShapBot 4Qwen 2NotebookLM 2
Most referenced — Style
No pings yet today
How they use it
crawler 4.4k
crawler_json 180
your_contextpost 3
pre-tracking 16
Category total4.6k pings
Terms pinged48 / 48
Distinct agents23
Loop Style Preferences
PHP 7.4+
Choose the clearest loop construct for the job: foreach for collections, for with index when position matters, while for condition-driven iteration.
5mo ago
Style beginner
Simplifying Complex Conditional Logic
6
Complex conditionals can be simplified with De Morgan's laws, guard clauses, decomposing into named predicates, and consolidating duplicate conditions.
7mo ago
Style intermediate
Branch Naming Conventions
Consistent branch names using type/description patterns — making branch purpose immediately clear and enabling automation based on branch name prefixes.
7mo ago
Style beginner
Class Naming Convention
PHP 5.0+
PHP classes must use PascalCase (UpperCamelCase) per PSR-1 — each word capitalised, no underscores, descriptive nouns or noun phrases.
7mo ago
Style beginner
Code Documentation Standards
PHP 5.0+
1
When, what, and how to document — the right balance between self-documenting code and explicit documentation for APIs, non-obvious decisions, and complex algorithms.
7mo ago
Style beginner
Commit Message Best Practices
Clear commit messages that explain why a change was made, not just what — enabling efficient git log navigation, automated changelog generation, and informed code archaeology.
7mo ago
Style beginner
Elvis Operator Not Used
PHP 5.3+
Writing $x ? $x : $y instead of $x ?: $y — the Elvis operator (?:) returns the left operand if truthy, otherwise the right, eliminating the repeated expression.
7mo ago
Style beginner
Excessive Blank Lines
PHP 5.0+
Multiple consecutive blank lines within a function or between statements — adding visual noise without improving readability.
7mo ago
Style beginner
Function & Method Naming Convention
PHP functions and methods use camelCase per PSR-1 — lowercase first word, each subsequent word capitalised, verb-noun pairs for actions.
7mo ago
Style beginner
Git Hooks in PHP Workflow
PHP 5.0+
Using pre-commit hooks to automatically run PHP-CS-Fixer, PHPStan, and security checks before every commit — preventing style violations and bugs from entering the repository.
7mo ago
Style intermediate
Inconsistent Indentation
Mixing tabs and spaces, or using varying numbers of spaces for indentation — causes visual misalignment across editors and makes diffs noisy.
7mo ago
Style beginner
Lines Too Long
Lines exceeding 120 characters force horizontal scrolling and break side-by-side diff views — PSR-12 recommends a soft limit of 120 and hard limit of no limit, but team conventions often enforce 120.
7mo ago
Style beginner
Missing Class Comments
PHP 5.0+
A class without a PHPDoc block lacks the docblock description, @package annotation, and context needed for IDE tooling, generated documentation, and new developers.
7mo ago
Style beginner
Missing Function Comments
PHP 5.0+
Functions without PHPDoc lose IDE parameter hints, inline documentation, and the opportunity to explain non-obvious behaviour, preconditions, and edge cases.
7mo ago
Style beginner
Null Coalescing Operator Not Used
PHP 7.0+
Using isset() + ternary or if/else chains when the null coalescing operator (??) or null coalescing assignment (??=) would be cleaner and more idiomatic.
7mo ago
Style beginner
Pull Request Description Templates
Structured PR templates in .github/PULL_REQUEST_TEMPLATE.md that prompt authors for context, testing evidence, and checklists — improving review quality and reducing reviewer cognitive load.
7mo ago
Style beginner
.gitignore for PHP Projects
PHP 5.0+
A well-structured PHP .gitignore excludes vendor/, generated files, IDE configs, .env secrets, and OS artifacts from version control.
7mo ago
Style beginner
Boolean Parameters (Flag Arguments Smell)
A boolean parameter that switches a function between two different behaviours — a sign the function should be split into two.
7mo ago
Style beginner
CHANGELOG — Keeping a Good One
2
A human-readable log of notable changes per release — distinct from git commit history — following Keep a Changelog conventions.
7mo ago
Style beginner
Conventional Commits
1
A commit message specification — type(scope): description — enabling automated changelogs, semantic versioning, and machine-readable history.
7mo ago
Style beginner