做什么
建成地物后,验证其与原计划相符,尊重系统架构和设计标准,并做好生产准备. 报告显然有问题,因此开发商决定如何处理.
技能库 智客分类:设计创意 review
建成地物后,验证其与原计划相符,尊重系统架构和设计标准,并做好生产准备. 报告显然有问题,因此开发商决定如何处理.
官方网址:skills.sh
先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。
建成地物后,验证其与原计划相符,尊重系统架构和设计标准,并做好生产准备. 报告显然有问题,因此开发商决定如何处理.
官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。
按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:What This Skill Does Not Do、Step 1 — Understand What Should Have Been Built、Step 2 — Review in Three Layers、Layer 1 — Does it match the plan?、Layer 2 — Does it respect the system?、Layer 3 — Is it production ready?。 其中含规范建议的小节:分步指令。
文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。
After building a feature, verify it matches what was planned, respects the system architecture and design standards, and is ready for production. Reports issues clearly so the developer decides what to fix.
What This Skill Does Not DoStep 1 — Understand What Should Have Been BuiltStep 2 — Review in Three LayersLayer 1 — Does it match the plan?Layer 2 — Does it respect the system?Layer 3 — Is it production ready?Step 3 — Report What You FoundReview — [Feature Name]Layer 1 — Plan alignmentLayer 2 — System integrityLayer 3 — Production readinessSummary
来源分类:skills.sh agent-skill
namereviewdescription具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗
先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。
复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。
把 Agent Skill「review」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-528dc565acf033a3-%E5%AE%A1%E6%9F%A5.html 请存为 .cursor/skills/review/SKILL.md 或 .claude/skills/review/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。
npx skills add 'https://github.com/jsmastery-pro/jsm-agent-skill' --list
npx skills add 'https://github.com/jsmastery-pro/jsm-agent-skill' --skill 'review'
CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。
Building is not done when the code runs. It is done when the code is correct.
AI moves fast. Fast means things get built that work on the surface but drift from the architecture, violate the design system, or miss edge cases that matter. This skill catches those things before they compound into bigger problems.
Run this after every feature. Before you move on.
It does not fix anything. It reports what it finds and lets the developer decide what matters and what to do about it. Fixing without understanding is how problems get buried, not solved.
Before reviewing anything, establish the benchmark.
Read in this order:
/architect if one existsIf no plan exists, ask the developer to describe what the feature was supposed to do before reviewing. You cannot verify correctness without knowing what correct looks like.
Compare what was built against what was planned.
Check:
Flag anything that was planned but missing. Flag anything that was built but not planned.
This is where AI drift most commonly happens. The feature works, but it violates rules that the project depends on.
Check:
Check:
After completing all three layers, produce a clear report. Do not bury issues. Do not soften them. Report honestly so the developer can make informed decisions.
## Review — [Feature Name]
### Layer 1 — Plan alignment
[PASS / ISSUES FOUND]
[List any gaps between what was planned and what was built]
### Layer 2 — System integrity
[PASS / ISSUES FOUND]
[List any architecture, design, or code standard violations]
### Layer 3 — Production readiness
[PASS / ISSUES FOUND]
[List any error handling gaps, edge cases, or obvious bugs]
### Summary
[X] issues found across [Y] layers.
[If no issues: "No issues found. This feature is ready to ship."]
[If issues: "Resolve the above before moving to the next feature."]
After presenting the report, stop. Do not start fixing. Do not suggest fixes unless the developer asks.
Wait for the developer to:
The developer owns the quality decision. You inform it.
Not all issues are equal. Use this to help the developer prioritise:
Critical — fix before moving on
Important — fix soon
Minor — fix when convenient
Label each issue with its severity so the developer can triage quickly.
The question this skill answers is not "does it work?"
The question is "is it correct?"
Working and correct are not the same thing. A feature can work today and break the project tomorrow. Review exists to catch the difference.
设计创意
设计和实施自动化工作流程,以节省时间和规模化操作作为独家. 用于识别重复任务实现自动化,构建跨工具的工作流程,设置触发器和行动,或优化现有自动化. 包括自动化机会识别,工作流程设计,工具选择(Zapier,Make,n8n),测试,和维护. 触发"自动","自动","工作流程自动…
设计创意
UI/UX设计智能及建筑抛光接口实施指导. 当用户要求UI设计,UX流量,信息架构,视觉风格方向,设计系统/托盘,组件规格,副本/显微镜,可访问性,或生成/critique/refine前端UI(HTML/CSS/JS,React,Next.js,Vue,Svelte,Tailw…
设计创意
创建美丽现代UI的专家前端设计指南. 在构建起落架页面,仪表板,或任何用户界面时使用.
设计创意
设计和输出 n8n 工作流程 JSON 有强力触发器, idempotency, 错误处理, 记录, 重试, 以及 人入"一站"审查队列. 当您需要可审计的自动化时使用.