据 AlphaMoat 统计,截至 2026-09,Php Full Stack Developer 累计下载 3,691 次、获 5 个星标,在全部 5,078 个 AI 技能中排名第 2,920 位,在「开发编程」分类(577 个)中排名第 377 位。

累计安装

181

累计下载

3,691

星标

全站排名

#2,920

全站前 58% · 「开发编程」前 66%

平台	累计安装	累计下载	星标	评论
ClawHub ↗	116	3,573	5	-
SkillHub ↗	181	3,691	5	—

各平台的计数口径不同,统计时间不一致。

这个技能是做什么的

适用于后端、前端、数据库、DevOps、调试、迁移和 API 工作。先明确目标、验收标准、风险和约束，再使用明确契约、可逆步骤及验证计划；重要事实应对照当前项目和运行环境，而非盲信旧记忆。

资料发布于 2026-10-27

可以用来做什么

制定工程任务的预检和验收计划
澄清 API、数据或部署契约
规划安全、可逆的实施与验证步骤

什么时候用

执行可能影响安全、数据完整性或部署的工程任务时
项目上下文不清或先前记忆可能过时、冲突时

示例提示词

以下是根据技能文档生成的示例,不代表实际运行结果。

先为这个 PHP 变更列出目标、验收标准、风险和验证办法，再等待我确认是否执行。

月度数据趋势

累计下载3,691

星标5

2026-09 起统计方法调整:同名技能按作者分别统计,并覆盖全部技能。图中虚线为调整前的月份,与之后的数据不直接比较,也不计算跨越调整的增长。

月份	累计下载	环比	星标
2026-09	3,691	—	5
2026-08	3,477	+4.9%	5
2026-07	3,316	+8.0%	5
2026-06	3,071	+5.4%	5
2026-05	2,915	—	5
2026-03	2,367	—	5

SKILL.md 原文

以下是作者发布的原始文件,按纯文本显示,本站未做修改或审核;其中的链接不可点击,命令请核实后再运行。抓取于 2026-10-23。

1.7 KB · ClawHub v0.1.0

---
name: php-full-stack-developer
description: A senior, governance-backed PHP full-stack delivery OS for OpenClaw. Emphasizes pre-flight analysis, safe data changes, explicit contracts, and reproducible verification.
---

# 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.

展开全部(共 37 行)

- 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)
1) Should I make and log this into a project to store it in memory?
2) 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`.