poteto@poteto

怎么才能更信任你的 agent 干的活？把这条帖子/链接复制给你的 @bot 或 agent！ 1. 代码库改进：这其实就是好的软件工程——更好的架构、更强的类型和不变量、清晰的边界。agent 超爱照抄现有的东西、走最短路径，所以要让简单的做法就是正确的做法。用代码从根上消灭问题，你就再也不用操心了。 2. 静态分析：lint 规则、测试、CI、验证（比如 TLA+）。都是提前抓问题、非常省 token 的办法。 3. 文字说明：注释、规则、AGENTS.md、skills——所有没法强制执行、需要 agent 自己判断的东西。尽量少用，但一定要用 /create-verification-skill。 4. 人工审查：最难规模化。按 agent 提交代码的速度，几乎不可能把每个 PR 都仔细审一遍，所以把精力花在杠杆最大的地方：设计一个让 agent 默认就做对的环境。 这就形成了一个倒金字塔：大部分精力放在顶部，底部最少。代码库改进是确定性的，所以更省 token，也能让你晚上睡得更踏实。 安装 pstack，然后新建一个 Project： 1. 翻一遍我在 slack/聊天消息和代码审查评论里对 PR、代码、架构给过的反馈 2. 对我过去的对话记录用 /recall，学习我是怎么引导 agent 的 3. /poteto-mode 对过去的 commit 用 /correct 和 /architect，找出 agent 最常踩的坑，然后提出一个方案，把我负责的代码重构得对 agent 更友好。遇到开放问题就靠做原型来回答，别推给我，并且用真实数据支撑这个方案。 4. 开始之前，先用 /sharpen + /in-your-own-words 跟我确认这段提示词

how do you trust your agents' work more? copy this post/link and give it to your @bot or agent! 1. codebase improvements: this is just good software engineering - better architecture, stronger types and invariants, clear boundaries. agents love to copy what exists and take the shortest path, so make the easy thing the right thing. categorically eliminate problems through code and you won't need to think about it again. 2. static analysis: lint rules, tests, CI, verification (eg TLA+). very token efficient ways to catch issues ahead of time. 3. prose: comments, rules, AGENTS.md, skills - anything that can't be enforced and requires agent judgment. use it minimally, but do use /create-verification-skill. 4. human review: the hardest to scale. at the rate agents land code, it's pretty much impossible to thoroughly review every PR, so spend that effort on the highest leverage point, designing an environment where agents do the right thing by default. this forms an inverse pyramid: you want most of your effort at the top, least at the bottom. codebase improvements are deterministic, making it more token efficient, and lets you sleep more soundly at night. install https://github.com/cursor/plugins/tree/main/pstack and create a new Project: 1. look through my slack/chat messages and code review comments where i've given feedback on PRs, code, architecture 2. use /recall on my past transcripts to learn how i steer agents 3. /poteto-mode use /correct and /architect on past commits to find the most common pitfalls agents fall into, then propose a plan to rearchitect the code i own so it's more agent friendly. answer open questions with prototyping rather than defer to me, and back the plan with real data. 4. before you begin, use /sharpen + /in-your-own-words and confirm this prompt with me