agentleFS
alexderzalexderz/agentic-toolbox/skills/lang-php/SKILL.md

lang-php

Skill5 starsChanged 46 days agoMITView on GitHub

use this when writing, reviewing, or testing PHP — *.php, composer.json. PHP 8+ types. do not use for JavaScript. not a Laravel architecture skill.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not display raw exceptions to clients.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

PHP

PHP 8+ types. No scripts/. Process skills that may load with this one: load-with list.

Iron law

Declare types. Parameterize queries. No eval.

Tooling / verify

composer test
# or vendor/bin/phpunit

php -l on touched files is not DoD.

Idioms a linter misses

  • declare(strict_types=1); when the project uses it.
  • Typed properties, parameters, returns. No untyped public API.
  • Constructor promotion when the class is already that style.
  • Return empty array, not null, for lists.

Errors

  • Exceptions or the project's result type. No @ error suppression.
  • Do not display raw exceptions to clients.

Concurrency

  • PHP request lifecycle is the default. Shared mutable statics are a bug in FPM.
  • Queues / workers: treat each job as a new process. No leftover state.

Testing

  • PHPUnit as the repo uses it. Test through public types.

PR review

  • New untyped public method: reject.
  • New query: binds visible.
  • Composer deps: lockfile in the diff.

Security

  • PDO or the project's DB layer with bound parameters.
  • password_hash / password_verify. No home-rolled hashing.
  • Escape output at the template boundary (the engine the project uses).
  • No unserialize of untrusted data. No eval. No extract on user input.
  • Uploads: allowlisted extensions and a storage path outside the docroot if the project already does that.

Always

  • Types on new public APIs. Binds. Tests.

Ask first

  • Raising the language level in composer.json.
  • Adding a framework the module is not already on.

Never

  • eval, extract on user input, unserialize of untrusted data.
  • md5 / sha1 for passwords.
  • mysql_* APIs. String-built queries.
  • Error suppression @.
  • Displaying raw exceptions to clients.

Red flags

  • "PHP will coerce it"
  • "addslashes is enough"
  • "unserialize is just the session format"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.