一键导入
delivery-handoff
Use when website or browser-motion work is being delivered, packaged, released, transferred to another contributor, or described as complete.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when website or browser-motion work is being delivered, packaged, released, transferred to another contributor, or described as complete.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when a user explicitly requests an independent review, challenge pass, or second opinion on a rendered website or animation artifact. Produces one bounded evaluator report and evidence verdict; it never auto-starts another build pass.
Use when a website task involves visual direction, existing-project discovery, animation, browser verification, or delivery and the smallest bounded route is not yet explicit.
Use when a user gives one sentence, a vague idea, or a loose brief and wants a finished website route. Turns "I want something like X" into an explicit bounded route, a verified artifact, and an honest handoff without autonomous review loops.
Use when claiming a visible, responsive, interactive, scroll-led, canvas, WebGL, or animated browser result is complete and fresh evidence is needed.
Use when browser work needs UI transitions, scroll choreography, GSAP, Motion, canvas, WebGL, responsive motion, or reduced-motion behavior.
Use when a landing page, portfolio, product story, or editorial site lacks a clear visual premise, hierarchy, material direction, or meaningful critique target.
| name | delivery-handoff |
| description | Use when website or browser-motion work is being delivered, packaged, released, transferred to another contributor, or described as complete. |
A useful handoff lets another person run the result, inspect the same evidence, understand the bounded claim, and continue from a known baseline.
Include the goal, baseline, changed areas, run/verify path, evidence location, verdict, known limits, and one recommended next action. State unresolved issues plainly instead of burying them in a completion message.
Exclude credentials, environment files, private assets, caches, dependency trees, unrelated history, and client-identifying evidence. Use a clean export when a working tree or Git history is not safe to publish.
Read ../../references/delivery-handoff.md and use ../../templates/handoff.md. Load browser-evidence first when the evidence verdict has not been determined.