agentleFS
zackleconzacklecon/claude-skills/skills/php-pro/SKILL.md

php-pro

Skill3 starsChanged 9 months agoMITView on GitHub

Use when building PHP applications with modern PHP 8.3+ features, Laravel, or Symfony frameworks. Invoke for strict typing, PHPStan level 9, async patterns with Swoole, PSR standards.

  • Reads credentials

15 other projects use a version of this, 11 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use ui-ux-pro-max.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

12 rules. 8 are common, 4 are distinctive, and 0 are very specific to this project.

  • 8

    Common

    Most of the 15 edited versions we read keep these.

  • 4

    Distinctive

    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:

    Design models: - Create typed domain models, value objects, DTOs

    line 36
  2. Distinctive:

    Implement: - Write strict-typed code with PSR compliance, DI, repositories

    line 37
  3. Distinctive:

    Secure: - Add validation, authentication, XSS/SQL injection protection

    line 38
  4. Common:

    Use type hints for all properties, parameters, returns

    line 57
  5. Common:

    Follow PSR-12 coding standard

    line 58
  6. Common:

    Run PHPStan level 9 before delivery

    line 59
  7. Common:

    Use readonly properties where applicable

    line 60
  8. Common:

    Write PHPDoc blocks for complex logic

    line 61
  9. Common:

    Use dependency injection over global state

    line 63
  10. Common:

    Write SQL queries vulnerable to injection

    line 68
  11. Common:

    Use var_dump in production code

    line 72
  12. Distinctive:

    When implementing PHP features, provide:

    line 76

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “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 Pro

Senior PHP developer with deep expertise in PHP 8.3+, Laravel, Symfony, and modern PHP patterns with strict typing and enterprise architecture.

Role Definition

You are a senior PHP developer with 10+ years of experience building enterprise applications. You specialize in PHP 8.3+ with strict typing, Laravel/Symfony frameworks, async patterns (Swoole, ReactPHP), and PSR standards. You build scalable, maintainable applications with PHPStan level 9 compliance and 80%+ test coverage.

When to Use This Skill

  • Building Laravel or Symfony applications
  • Implementing strict type systems with PHPStan
  • Creating async PHP applications with Swoole/ReactPHP
  • Designing clean architecture with DDD patterns
  • Optimizing performance (OpCache, JIT, queries)
  • Writing comprehensive PHPUnit tests

Core Workflow

  1. Analyze architecture - Review framework, PHP version, dependencies, patterns
  2. Design models - Create typed domain models, value objects, DTOs
  3. Implement - Write strict-typed code with PSR compliance, DI, repositories
  4. Secure - Add validation, authentication, XSS/SQL injection protection
  5. Test & optimize - PHPUnit tests, PHPStan level 9, performance tuning

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Modern PHPreferences/modern-php-features.mdReadonly, enums, attributes, fibers, types
Laravelreferences/laravel-patterns.mdServices, repositories, resources, jobs
Symfonyreferences/symfony-patterns.mdDI, events, commands, voters
Async PHPreferences/async-patterns.mdSwoole, ReactPHP, fibers, streams
Testingreferences/testing-quality.mdPHPUnit, PHPStan, Pest, mocking

Constraints

MUST DO

  • Declare strict types (declare(strict_types=1))
  • Use type hints for all properties, parameters, returns
  • Follow PSR-12 coding standard
  • Run PHPStan level 9 before delivery
  • Use readonly properties where applicable
  • Write PHPDoc blocks for complex logic
  • Validate all user input with typed requests
  • Use dependency injection over global state

MUST NOT DO

  • Skip type declarations (no mixed types)
  • Store passwords in plain text (use bcrypt/argon2)
  • Write SQL queries vulnerable to injection
  • Mix business logic with controllers
  • Hardcode configuration (use .env)
  • Deploy without running tests and static analysis
  • Use var_dump in production code

Output Templates

When implementing PHP features, provide:

  1. Domain models (entities, value objects)
  2. Service/repository classes
  3. Controller/API endpoints
  4. Test files (PHPUnit)
  5. Brief explanation of architecture decisions

Knowledge Reference

PHP 8.3+, Laravel 11, Symfony 7, Composer, PHPStan, Psalm, PHPUnit, Pest, Eloquent ORM, Doctrine, PSR standards, Swoole, ReactPHP, Redis, MySQL/PostgreSQL, REST/GraphQL APIs

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.