ericrisco/rsc-harness / skills/php
php
VerifiedUse when writing, reviewing or modernizing PHP (8.3-8.5) outside Laravel — strict types, union and intersection types, readonly classes, backed enums, property hooks and asymmetric visibility, the pipe operator and clone-with, Composer with PSR-4, PER-CS style, PSR interop, and the quality toolchain (PHPStan, Pint, Rector, PHPUnit/Pest). NOT Eloquent, Blade or Artisan (that is `laravel`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.5 KB |
| evals/README.md | markdown | 865 B |
| evals/cases.yaml | config | 2.8 KB |
| references/tooling.md | markdown | 4.3 KB |
| references/type-system.md | markdown | 6.8 KB |
| scripts/verify.shexecutable | script | 5.2 KB |
evals/README.md
View on GitHub# Evals — php
These cases are a behavioral spec, not an automated harness. Run them by hand: prompt a fresh
agent with each `should_trigger` line and confirm it loads the `php` skill; prompt it with
each `should_not_trigger` line and confirm it declines and routes to the named sibling
(`laravel`, `wordpress`, `security-audit`, `api-design`, `mysql`) instead of answering from
this skill. For the `capability` scenario, give the agent the scenario prompt and grade the
generated package against the `must_include` rubric — every item must be present (strict
types in each file, PSR-4 autoload, a backed enum, a readonly DTO with a property hook, a
typed exception, `phpstan.neon` at `level: max`, and zero framework coupling). `scripts/verify.sh`
is the separate code-artifact check you run inside a real PHP project root, not part of these
behavioral evals.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |