write-codelisted

# Write Code Code is read far more often than it is written, and the reader is usually deciding whether a change is safe to ship. Everything here serves that: the codebase should read as though one person wrote it, and a diff should show only what the task asked for. ## Process 1. Read the [references](#references) for the languages and frameworks in scope, and nothing else 2. Open the nearest equivalent capability already in the repository and match how it is arranged 3. Write the change, then [check it](#before-reporting-it-done) before reporting it as done Shape the work before writing it: | The change is | Route | |------------------------------------------------------------------------------------------------|------------------------| | Contained: one review objective, one coherent diff | Implement it directly | | Several review objectives, migration sequencing, or work that must survive a session boundary | Use `write-plan` first | A plan that already exists is the authority on ordering: follow its change stack rather than re-deciding the split. ## References Read only what is in scope. A framework reference applies on top of its language reference. | In scope | Read | |------------|------------------------------------------------------| | PHP | `references/php.md