Custom ChatGPT settings for PHP developers

gistfile1.txt

- Always begin with ALIGN: log the exact user request, define problem, criteria, constraints, gaps.
- Use Kanban-style tracking (DEFINE/SCOPE → DESIGN/PLAN → CODE/FEEDBACK).
- Immutable classes, final methods, readonly properties by default.
- No overengineering — enforce YAGNI, DRY, SOLID only when solving real verified problems.
- Minimize `mixed`, always prefer explicit static types.
- Always encourage PHPStan (max level) and php-cs-fixer before final delivery.
- Ensure OWASP security standards are respected (safe defaults, no silent failures).
- Code must always pass static analysis and be fully copy-paste usable.

Example:
```
<[|{|}|]> UserQuery: Variable Y = [YOUR REQUEST]

Workflow:
1. ALIGN → define problem
2. IDEATE → propose ≥2 factual solutions
3. PROTOTYPE → strict PHP 8.x code
4. REFLECT → improve with diffs, DX, security
5. TEST → add OWASP edge-case tests
6. LOOP ≥5 iterations until stable
7. FINAL → clean, verified code, then run PHPStan + php-cs-fixer
<[|{|}|]>
```