chore(config): add Claude Code lint command configuration

Author: wilcorrea

.claude/commands/lint.md

@@ -0,0 +1,80 @@
+You are a code quality specialist for this PHP serialization/deserialization library. Your role is to ensure all code meets project standards by running linters, analyzing errors, and applying fixes following project conventions.
+
+## Your Task
+
+Run 'make fix' first to autocorrect code style, then run 'make lint' iteratively until all linters pass.
+
+### Execution Steps
+
+1. **Auto-fix**: Run `make fix` to automatically correct code style issues
+2. **Check all linters**: Run `make lint` to check all remaining linters
+3. **Analyze failures**: If any linter fails, analyze the specific errors reported
+4. **Apply fixes**: Fix the issues following project coding standards (see below)
+5. **Verify**: Run the specific failing linter to verify fixes (e.g., `docker-compose exec constructo vendor/bin/phpstan analyse`)
+6. **Repeat**: Continue steps 2-5 until `make lint` passes completely with no errors
+7. **Summary**: Show a summary of all changes made
+
+### Available Linters
+
+- **phpcs**: PHP CodeSniffer (PSR-12 compliance)
+- **phpstan**: Static analysis (type safety, undefined methods)
+- **phpmd**: PHP Mess Detector (complexity, code smells)
+- **rector**: Code modernization and best practices
+- **psalm**: Additional static analysis
+
+### Project Coding Standards
+
+**PSR-12 Compliance**:
+- Short array syntax: `[]` instead of `array()`
+- Single quotes for strings (unless interpolation needed)
+- Strict types declaration: `declare(strict_types=1);` at top of every file
+- Use `===` and `!==` exclusively (never `==` or `!=`)
+- Trailing commas in arrays when possible
+- Control structures: use `elseif` instead of `else if`
+
+**Type Safety**:
+- Always use explicit parameter and return type hints
+- Avoid mixed types when possible
+- Use nullable types (`?Type`) instead of `Type|null`
+- PHPDoc only when PHP native typing is insufficient (e.g., `array<string>`, `Collection<User>`)
+
+**Comments Policy**:
+- **Default**: Do NOT add comments unless explicitly needed
+- Code should be self-documenting through clear naming
+- **Use PHPDoc only when**:
+  - Array types: `@param Driver[] $drivers` or `@return array<string,mixed>`
+  - Generic collections: `@param Collection<User> $users`
+  - Exceptions thrown: `@throws AuctionException When auction fails`
+- **Test comments**: Always use AAA comments (`// Arrange`, `// Act`, `// Assert`)
+
+**Naming Conventions**:
+- Classes: PascalCase
+- Methods/functions: camelCase
+- Constants: UPPER_SNAKE_CASE
+- Variables: camelCase
+- All code, variables, functions, and comments MUST be in English
+
+**Common PHPStan Fixes**:
+- Add type hints to properties, parameters, and return types
+- Handle null cases with `?->` operator or null checks
+- Use `assert()` for type narrowing when needed
+- Import classes instead of using FQCNs in code
+
+**Common PHPMD Fixes**:
+- Extract long methods (>80 lines) into smaller methods
+- Reduce cyclomatic complexity with early returns or strategy pattern
+- Remove unused variables and parameters
+
+### Iteration Limit
+
+- Fix one linter at a time if multiple lines fail
+- Explain each fix you make and why it's necessary
+- Stop after 10 iterations if issues persist and report the remaining problems
+- If blocked, suggest manual intervention with specific guidance
+
+### Success Criteria
+
+✅ All linters pass with no errors
+✅ All fixes follow project coding standards
+✅ 100% PSR-12 compliance
+✅ All code is type-safe with proper hints