把 Claude Code/Codex 当资深工程师用

精选追评与案例

1. Vox@Voxyz_ai · 查看追评

   给出可直接复用的端到端目标模板，强调持续验证、审查与生产级完成标准。

   𝟭. 𝘁𝗵𝗲 𝗴𝗼𝗮𝗹 𝘁𝗲𝗺𝗽𝗹𝗮𝘁𝗲 𝗶 𝗿𝘂𝗻 𝗼𝗻 𝗲𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴 goal: {your task / the full spec you already agreed on}. keep going until the architecture and result meet the bar, not just until it runs. after every meaningful step: real-time test the real thing (full end-to-end, plus computer use, browser, keystrokes, whatever it needs), auto review then commit, write progress somewhere sensible in the project. finish: one dedicated review pass over everything. done = every dimension at 100%, production-grade, a real user can walk in and use it. swap out {your task} and go. new feature, refactor, all the same. tip: don't hardcode the progress path. tell it to write somewhere sensible and it finds the right spot on its own. this is the wrapper for everything below. drop a task prompt into the {your task} slot, use #2 for big jobs, and it runs end-to-end instead of stopping at the first thing that compiles.

   中文译文 · 机器翻译

   1. 我在所有任务上都会使用的目标模板 goal: {your task / the full spec you already agreed on}。持续做下去，直到架构和结果达到标准，而不只是做到能运行。 每个有意义的步骤之后：对真实产物做实时测试（完整端到端，再加上 computer use、浏览器、键盘输入，凡是需要的都用上），自动审查后提交，并把进度写到项目里合适的位置。 收尾：对全部内容做一次专门审查。 完成 = 每个维度都达到 100%，达到生产级，真实用户可以直接上手使用。 替换掉 {your task} 就可以开始。新功能、重构，全都一样。 提示：不要硬编码进度路径。告诉它写到合适的位置，它会自己找到正确的地方。 这是下面所有内容的包装器。把任务提示词放进 {your task} 槽位，大任务用 #2，它就会端到端运行，而不是在第一个能编译的东西处停下。

2. Vox@Voxyz_ai · 查看追评

   补充大任务的并行拆解与多智能体协作流程，适合复杂项目落地。

   𝟮. 𝗽𝗮𝗿𝗮𝗹𝗹𝗲𝗹 + 𝗲𝗻𝗱-𝘁𝗼-𝗲𝗻𝗱 𝗴𝗼𝗮𝗹 (𝗳𝗼𝗿 𝗯𝗶𝗴 𝘁𝗮𝘀𝗸𝘀) For this task, write yourself a new end-to-end /goal: complete the whole plan, not just the next step, until the architecture, implementation, tests, review, and final result meet the standard. Split that goal into independent pieces, spawn as many parallel agents as needed to do it better and faster, and give each agent its own dedicated /goal that includes its expected deliverable, verification, and completion standard. Dispatch them concurrently, keep tracking progress in the right place, synthesize results as they return, resolve conflicts, continue implementation, run real-time validation after important steps, and finish with review, submission/commit when appropriate, and a final summary. Validation should cover the real end-to-end path, including browser/computer use, clicks, keyboard actions, and any necessary operation. Do not stop after partial progress unless blocked by missing credentials, destructive ambiguity, or conflicting requirements.

   中文译文 · 机器翻译

   2. 并行 + 端到端目标（用于大任务） 对于这个任务，给自己写一个新的端到端 /goal：完成整个计划，而不只是下一步，直到架构、实现、测试、审查和最终结果都达到标准。把这个目标拆成相互独立的部分，按需生成尽可能多的并行智能体来做得更好、更快，并给每个智能体各自专门的 /goal，其中包含它预期的交付物、验证方式和完成标准。 并发派发它们，在正确的位置持续跟踪进度，汇总返回的结果，解决冲突，继续实现，在重要步骤后做实时验证，最后以审查、在适当时提交/commit 以及最终总结收尾。验证应覆盖真实的端到端路径，包括浏览器/计算机操作、点击、键盘操作以及任何必要的操作。除非被缺少凭证、破坏性歧义或需求冲突阻塞，否则不要在只完成部分进度后就停下。

3. Vox@Voxyz_ai · 查看追评

   提供从需求分析到生产级交付的完整开发框架，强调架构与边界情况。

   𝟯. 𝗯𝘂𝗶𝗹𝗱 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻-𝗴𝗿𝗮𝗱𝗲 Act as a senior engineer shipping something production-ready, whether it's a single feature or a full app. Don't jump to code. First analyze the requirements, list the edge cases, design the architecture, lay out a plan. Build the minimal version that's still scalable and maintainable. Then deliver: architecture overview, folder structure, data flow, database schema and API design where relevant, full implementation, edge case and error handling, performance notes. Design it like a real startup MVP, not a demo.

   中文译文 · 机器翻译

   3. 构建生产级成果 以一位交付生产级成果的资深工程师的身份行事，无论是一个单独功能还是一个完整应用。 不要直接跳到代码。先分析需求，列出边界情况，设计架构，制定计划。构建仍然可扩展、可维护的最小版本。 然后交付：架构概览、目录结构、数据流、相关时给出数据库 schema 和 API 设计、完整实现、边界情况与错误处理、性能说明。 像真实的创业公司 MVP 那样设计，而不是一个 demo。

4. Vox@Voxyz_ai · 查看追评

   给出接手陌生代码库后的架构梳理、问题定位与重构路径。

   𝟱. 𝘀𝗲𝗻𝗶𝗼𝗿 𝗱𝗲𝗯𝘂𝗴𝗴𝗶𝗻𝗴 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿 Act as a senior engineer chasing a bug in production. Read the code carefully, reason step by step, find the root cause, give a robust fix. Account for edge cases and performance. Your answer should cover three things: the cause, the fix plan, and production-ready code.

   中文译文 · 机器翻译

   4. 理解一个陌生的仓库并重构 以一位刚接手一个大型、陌生代码库的资深工程师的身份行事。先理解架构和数据流。 然后找出：结构性问题、重复代码、性能瓶颈、可维护性风险。 交付：架构概览、问题区域、重构策略、改进后的架构和代码。

5. Stan van Rooy@stanvanrooy · 查看追评

   反向指出资深工程师通常不需要手把手指令，提醒该类比存在逻辑漏洞。

   @Voxyz_ai lol isn't it the other way around? If I tell a senior "fix this bug" I trust it'll get fixed, while an intern needs detailed explanation

   中文译文 · 机器翻译

   @Voxyz_ai 笑死，难道不是反过来吗？如果我让一位资深工程师“修这个 bug”，我相信它能修好；而实习生才需要详细解释。