做什么
使用任何编码库中带有**Cursor**的建筑特性时,工程应经过有纪律的建筑_审查_测试_固定回路. 触发"运行构建回路","构建下一个任务","继续计划","正确构建这个功能",或任何从计划文件或直接功能提示执行工作的请求. 从计划(或如果没有计划时的提示)中构建,运行Cursor的"/审查"并修正每一个发现的问题,测试并验证特性结束,修正任何测试表面,一旦完成就报告. 重复到所有计划任务被检查结束为止 .
技能库 智客分类:Agent 工作流 build-loop-cursor
使用任何编码库中带有**Cursor**的建筑特性时,工程应经过有纪律的建筑_审查_测试_固定回路. 触发"运行构建回路","构建下一个任务","继续计划","正确构建这个功能",或任何从计划文件或直接功能提示执行工作的请求. 从计划(或如果没有计划时的提示)中构建,运行Cursor的"/审查"并修正每一个发现的问题,测试并验证特性结束,修正任何测试表面,一旦完成就报告. 重复到所有计划任务被检查结束为止 .
官方网址:skills.sh
先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。
使用任何编码库中带有**Cursor**的建筑特性时,工程应经过有纪律的建筑_审查_测试_固定回路. 触发"运行构建回路","构建下一个任务","继续计划","正确构建这个功能",或任何从计划文件或直接功能提示执行工作的请求. 从计划(或如果没有计划时的提示)中构建,运行Cursor的"/审查"并修正每一个发现的问题,测试并验证特性结束,修正任何测试表面,一旦完成就报告. 重复到所有计划任务被检查结束为止 .
任何编码库中带有**Cursor**的建筑特征,工程应经过有纪律的建筑_审查_测试_固定回路. 触发“运行构建循环”、“构建下一个任务”、“继续计划”、“正确构建这一功能”或任何从 pl 执行工程的请求
按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Cursor Build Loop、Source of work、The loop、Rules。
文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。
Use when building features with **Cursor** in any codebase and the work should go through a disciplined build → review → test → fix loop. Triggers on "run the build loop", "build the next task", "continue the plan", "build this feature properly", or any request to implement work from a plan file or a direct feature prompt. Builds from the plan (or the prompt if no plan exists), runs Cursor's `/review` and fixes every issue found, tests and verifies the feature end to end, fixes anything testing surfaces, and reports back once complete. Repeats until all plan tasks are checked off.
Cursor Build LoopSource of workThe loopRules
· 许可:MIT
来源分类:skills.sh agent-skill
namebuild-loop-cursordescription具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗
先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。
复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。
把 Agent Skill「build-loop-cursor」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-e53a6914bb76a10a-%E6%9E%84%E5%BB%BA%E5%BE%AA%E7%8E%AF%E5%85%89%E6%A0%87.html 请存为 .cursor/skills/build-loop-cursor/SKILL.md 或 .claude/skills/build-loop-cursor/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。
npx skills add 'https://github.com/buildgreatproducts/builder-os' --list
npx skills add 'https://github.com/buildgreatproducts/builder-os' --skill 'build-loop-cursor'
CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。
/review and fixes every issue found, tests and verifies the feature end to end, fixes anything testing surfaces, and reports back once complete. Repeats until all plan tasks are checked off.
license: MIT
metadata:
author: BuilderOS
version: "1.0"Quality-gated feature work: nothing ships on "it compiles" — every increment is built, reviewed, tested end to end, and fixed before the user hears "done."
- [ ] checkboxes — search the repo): work the first unchecked task. Tasks are ordered intentionally — never skip ahead. If the plan references spec docs, read only the sections relevant to the current task.Run per task (or per prompted feature). Do not advance until every step passes.
Build. Implement exactly what the task specifies. Simplest implementation that satisfies it, surgical changes, no speculative scope. Match existing project conventions.
Review. Run Cursor's /review on the changes. Fix all findings in scope — bugs, security issues, edge cases, performance, style in files you touched. If the project has a design system spec (design tokens file, DESIGN.md, theme config), check UI changes against it — no hardcoded colors, type, or spacing that bypass tokens. Note pre-existing issues in untouched code for the report instead of fixing silently. Re-run /review until clean. If a finding contradicts the task or spec, the spec wins — flag the disagreement.
Test end to end. Run the task's verification step (or the success criteria). Run the full test suite — everything that passed before must still pass. Add tests for new logic. Then exercise the feature as a user would: run the app, walk the real flow including empty, loading, and error states.
Fix. Anything testing finds goes back through the loop: fix → /review → re-test. Never mark a failing task complete; never start the next task with the app broken.
Continue. Mark the task - [x], update any progress/status line in the plan, and loop to the next task until the requested scope is complete.
Report. When done, tell the user: what was built and plan progress, review findings fixed and anything deferred, how it was verified (tests + flow walked), and what needs their attention next. Be honest about anything flaky or partially verified.
Agent 工作流
创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.
Agent 工作流
使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.
Agent 工作流
管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.
Agent 工作流
Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…