php-full-stack-developer

What This Skill Does

The php-full-stack-developer skill serves as a senior-level technical architect and implementation engine for PHP-based environments. It is designed to act as an OpenClaw governance layer for full-stack engineering, moving beyond simple code generation to focus on system stability, security, and reproducible verification. It emphasizes a structured methodology: start with a Pre-Flight analysis to align on risks and constraints, proceed with explicit coding contracts, and conclude with verified deployment/testing strategies. This skill is built to handle the complexities of PHP development, including Laravel/Symfony ecosystems, database migrations, API contract management, and CI/CD pipelines.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/sja-dev1/php-full-stack-developer

Use Cases

This skill is intended for high-stakes engineering tasks where reliability and system integrity are paramount. Use it for:

• Implementing breaking API changes that require strict contract adherence and backward compatibility.
• Refactoring legacy codebases where documentation is sparse and the risk of regression is high.
• Designing and executing database migrations for high-traffic environments to prevent data loss.
• Setting up or maintaining CI/CD workflows that ensure automated testing and staging-to-production deployment logic.
• Diagnosing intermittent production performance issues that require log analysis and telemetry evaluation.

Example Prompts

1. "I need to refactor our user authentication module in Laravel 10. Start a pre-flight analysis for potential security impacts and let me know if we need to spin up a dedicated agent for this."
2. "We need to migrate our order history table to a new schema. Please outline the rollback strategy, define the data integrity constraints, and provide the SQL migration script."
3. "Our API consumers are complaining about response time latency. Can you perform an investigation, suggest a caching strategy, and provide a test plan to verify the performance gains?"

Tips & Limitations

• Governance First: Always prioritize the two mandatory governance questions (logging to memory and agent specialization) to ensure your project maintains architectural standards.
• Constraint Awareness: If you are unsure about the PHP version or database engine, stop immediately. Do not guess; define the environmental constraints as the first step of your Pre-Flight analysis.
• Documentation: Use the skill to generate 'How to test' steps. This ensures that every delivery is reproducible and testable by other team members.
• Limitations: This skill is not for quick, 'throwaway' scripts. It is explicitly designed for production-grade, long-term maintenance projects. Avoid using it for simple, low-risk automation tasks where the overhead of governance might outweigh the benefit.