skills.rest
JCETools-Petra
JCETools-PetraCOMMUNITY
Explore all skills by this author →
GitHub

php

Guide PHP development with framework selection, type safety, and verification workflows.

16|Updated Apr 30, 2026
Search Tags:#type safety#code review#php#composer#phpstan#pest#verification checklist
One-click install
npx skills add https://github.com/JCETools-Petra/JCE-Opencode-Tools --skill php-jcetools-petra
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: php
Source: https://github.com/JCETools-Petra/JCE-Opencode-Tools/tree/main/config/skills/php
Command: npx skills add https://github.com/JCETools-Petra/JCE-Opencode-Tools --skill php-jcetools-petra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the friction of planning and implementing safe, modern PHP changes by guiding you toward the right stack, patterns, and verification steps for the codebase you are working on.

Core Features & Use Cases

  • Project architecture guidance: Choose appropriate frameworks and styles for web apps, Composer packages, CLI tools, and microservices.
  • Type-safety and maintainability patterns: Apply strict typing, PHPStan levels, value objects, enums with methods, and immutable DTOs.
  • Testing and verification workflows: Use Pest, Pint/formatting, and CI-friendly checks to confirm correctness beyond “it runs”.

Quick Start

Ask the assistant to analyze my repository’s PHP files and propose a concrete plan to implement the requested feature with strict_types, PHPStan-focused type safety, and a Pest test strategy.

Frequently Asked Questions about php

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce strict_types and type safety in a modern PHP project?▼

Enforce strict_types in modern PHP by declaring strict typing, running PHPStan at high analysis levels, and using readonly DTOs with enums. This workflow guarantees type safety and maintainability for your codebase.

What's the best way to structure a PHP feature implementation workflow with Pest and PHPStan?▼

The best way to structure PHP feature implementation is using a Plan-Execute-Review-Verify workflow. This process plans the architecture, executes with strict_types, reviews via PHPStan, and verifies correctness using Pest tests for CI-friendly checks.

Can I use modern PHP 8.4 patterns like readonly DTOs and enums for Composer package development?▼

Modern PHP 8.4 patterns like readonly DTOs and enums are fully supported for Composer package development. They provide robust, type-safe architecture structures for packages, CLI tools, and microservices.

Does this PHP workflow support code review and debugging for existing codebases?▼

This PHP workflow directly supports code review and debugging for existing codebases. It applies strict_types, PHPStan static analysis, and Pest test strategies to verify correctness and resolve issues during review.

When do I need PHPStan and Pest for verifying PHP changes beyond just making sure it runs?▼

You need PHPStan and Pest when verifying PHP changes requires evidence-driven completion. PHPStan enforces type safety while Pest validates functional correctness, ensuring changes pass CI-friendly checks beyond basic execution.

Related Skills

Explore More Software Engineering Skills→
bdbchbdbch
2

php-development

Develop modern PHP applications with type safety, PSR standards, and Composer.

Community
Advanced
morodomimorodomi
8

laravel-quality

Run Pest, Larastan, and Pint quality checks on Laravel projects.

Community
Intermediate
tarekBassiounytarekBassiouny

Najaah LMS - Code Quality Agent

Enforces code quality standards for the Najaah LMS project using Pest, PHPStan, and Laravel Pint.

Community
Advanced
herdiansahherdiansah
23

php-pro

Generate idiomatic PHP 8+ code using generators and SPL data structures.

Community
Advanced