據 AlphaMoat 統計,截至 2026-09,Php Full Stack Developer 累計下載 3,691 次、獲 5 個星標,在全部 5,078 個 AI 技能中排名第 2,920 位,在「開發程式設計」分類(577 個)中排名第 377 位。

累計安裝

181

累計下載

3691

星標

全站排名

#2,920

全站前 58% · 「開發程式設計」前 66%

平台	累計安裝	累計下載	星標	評論
ClawHub ↗	116	3573	5	-
SkillHub ↗	181	3691	5	—

各平台的計數口徑不同,統計時間不一致。

這個技能是做什麼的

適用於後端、前端、資料庫、DevOps、除錯、遷移和 API 工作。先明確目標、驗收標準、風險和約束，再使用明確契約、可逆步驟及驗證計劃；重要事實應對照當前專案和執行環境，而非盲信舊記憶。

資料釋出於 2026-10-27

可以用來做什麼

制定工程任務的預檢和驗收計劃
澄清 API、資料或部署契約
規劃安全、可逆的實施與驗證步驟

什麼時候用

執行可能影響安全、資料完整性或部署的工程任務時
專案上下文不清或先前記憶可能過時、衝突時

示例提示詞

以下是根據技能文件生成的示例,不代表實際執行結果。

先為這個 PHP 變更列出目標、驗收標準、風險和驗證辦法，再等待我確認是否執行。

月度資料趨勢

累計下載3691

星標5

2026-09 起統計方法調整:同名技能按作者分別統計,並覆蓋全部技能。圖中虛線為調整前的月份,與之後的資料不直接比較,也不計算跨越調整的增長。

月份	累計下載	環比	星標
2026-09	3691	—	5
2026-08	3477	+4.9%	5
2026-07	3316	+8.0%	5
2026-06	3071	+5.4%	5
2026-05	2915	—	5
2026-03	2367	—	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`.