php-best-practices

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Use this skill as a rulebook for building and migrating PHP backend components following TreeNation's DDD architecture.

本技能作为遵循TreeNation的DDD架构构建和迁移PHP后端组件的规则手册使用。

Open
```
AGENTS.md
```
.
Identify which components need to be created or changed (controller, service, DTO, repository, response, test).
Load only the relevant rule files from
```
rules/
```
.
Implement the smallest correct change that satisfies the requirement.
Run PHP CS Fixer and PHPStan before finishing.

New PHP files go inside
```
src/
```
except controllers (which stay in
```
app/Http/Controllers/
```
).
Controllers must not contain business logic; delegate to a service.
Services must be unit-tested; mock all dependencies.
Always register new repository interfaces in
```
app/Providers/TreeNationProvider.php
```
.
Use strict typing (
```
declare(strict_types=1)
```
) in all new files.
Do not add comments unless the user explicitly asks.
Follow the Criteria pattern for all repository queries.
Access model data via getter methods, not direct property access (see
```
rules/model-getters.md
```
).
Commits follow pattern:
```
TNIT-####: description
```
.

Explain which rules were applied and why.
Generate all required files for the feature (controller, request, DTO if needed, service, response, repository interface, repository implementation, test).
Keep changes incremental; avoid broad rewrites unless asked.