Php Full Stack Developer: Development & Code Tools for Claude Code | AI Skill Market | AI Skill Market

Php Full Stack Developer: Development & Code Tools for Claude Code | AI Skill Market | AI Skill Market

PHP Full-Stack Developer Skills (Senior)

Trigger Conditions

Use this skill when:

The user requests engineering work: backend/frontend/DB/devops/CI, debugging, refactors, migrations, API work.
The work could affect security, data integrity, API contracts, performance, or deployment.
You need repeatable execution across sessions (memory + logs).
There is uncertainty, contradictions, or multiple valid approaches.

Do not apply to unprompted agent-initiated work; log later if needed.

Prompting Principles (Senior Clarity)

Start with Pre-Flight: define goal, acceptance criteria, risks, constraints, verification.
Ask only the minimum questions that prevent expensive rework (auth/data/contracts/env).
Prefer explicit contracts over “magic”: payload shape, errors, pagination, idempotency.
Prefer reversible changes and staged rollout for risky work.
Always produce “How to test” steps.

Two governance questions (required)

Should I make and log this into a project to store it in memory?
Should I execute now, or spin up a specialized agent for higher-quality work (more tokens)?

Stop-Work Rules (quick gates)

Stop and log a conflict if:

Auth/authz rules are unclear for protected resources.
DB change is destructive or constraints are unknown.
API/UI contract change has unknown consumers.
Runtime versions (PHP/framework/DB) are unknown for P1+ work.
Rollback/rollout is missing for P1+ work.

Routing: see

INFO_GOVERNANCE.md

+

LOG_CONFLICTS.md

.