Tw93

Kaku is my open-source Mac terminal for AI coding. Running several agents at once? A tab lights a dot when its agent needs you, and Cmd+J jumps straight to it. On your phone, the remote page lists every tab with its agent's status. github.com/tw93/Kaku

这两天做了一个有意思的事情，把我的全部的 Skills 删除了将近 1/3，同时把所有项目的上下文也都优化了一下，感觉干净清爽了不少，我认为随着模型能力越来越厉害，我们有经常去更新裁剪我们的项目的一些给到模型的上下文信息，防止你的内容反而阻碍了模型的发挥。 于是我就把最近做的继续沉淀成一些大伙也用得上的提示词，可以直接给到你的 Agent 去帮你优化你的项目的内容要求和 Skills，已经安装 Waza 的小伙伴可以直接更新到最新然后说「帮我精简一下规则」就好，也可以 Copy 下面内容给你的Agent。 帮我精简这个项目给 Agent 的上下文和我装的 Skills，按下面的要求来，先整理出清单给我确认，确认前先不改任何文件。 1. 先盘点每轮对话都会加载的内容，包括根目录的 AGENTS.md / CLAUDE.md、全局规则、没写 paths: 的 .claude/rules 和每个 skill 的描述，看各占多少字，再看按需加载的部分，这里不少看着臃肿的内容可能不是写多了，而是放的位置不对。 2. 逐段给出处理方式，分成修、删、挪、改写、保留五种，挪的写清目的地，每条附一句原因，做成一张清单给我确认。 3. 逐句判断删掉后你的行为会不会变，把类似这种「先读再改」「跑测试」「注意边界」你本来就会做的描述删掉，拿不准的可以先保留找我确定。 4. 我们更加推崇是给 Agent 写目标，少些如何实现的路线，写清做完是什么样、怎么算完成、要什么证据，一个步骤删掉后你还能换条路做到同样结果就删掉，只有顺序本身是约束的才留下来，比如先验证再发布、先确认再删除这种需要保留。 5. 同一种要求说了三遍，换成一个你本来就懂的词语，比如「快、确定、开销小」可以写成 tight；「要简洁」这类口号换成一个更好理解的想想的词语比如「报告腔」，然后再配一组 NO / OK 例子。 6. 把对应内容放对位置，需要判断的进 skill，同样输入总是同样输出的改成脚本或 hook，项目命令和发布步骤进项目指南，跨项目的硬约束才放进全局规则，遇到「做 Y 之前先读 X」这类要求改成做 Y 时由 hook 把 X 注入进来更好。 7. skill 描述只写做什么、什么时候用、不用于什么，近义词移到 when_to_use，只有部分场景用到的内容移到 references；判断一个 skill 有没有人用，要看真实调用记录，不要只 grep 名字，要删的也先列给我看一下。 8. 这些内容不要删除： - 我的偏好、被否掉的方案和原因、机器环境。 - 不报错的坑，以及看着像出错其实正常的现象。 - 描述句里「从不写入」「不上传」这类半句约束。 - 删数据、需要花钱、要发布、提权、改写已推送历史这些不可逆操作的规则。 - 我们带日期的拍板决策记录。 9. 内容先移到对应正确的位置再来压缩，能整行搬到按需加载的文件里就整行搬，不要边搬边改写，不可逆的规则原样整段搬。 10. 把内容搬到能自己加载的地方可以参考这些技巧： - 提交、发布、回复、删除这类对话里随时会触发的规则留在根目录。 - 挪进 docs/ 的要在根目录留一句什么时候去读。 - 根目录不要建 CLAUDE.md，它会让 Claude Code 不再读 AGENTS.md。 - 项目里重复全局规则的句子，只有在我用的每个工具都读全局规则时才删。 11. 改完以后自己去查一遍：paths: 里的 glob 都要能匹配到真实文件，grep 一遍拆走的旧文件名，再列出所有消失的行，每一行都要对上清单里我确认过的删除。 12. 交给一个没参与精简的 Agent 查有没有删过度了，只给它消失的行和仓库，不给你的结论，让它搜关键名词而不是整句，意思在哪都找不到的原样恢复。 13. 验证移过去的内容真的会被加载：在新文件里埋一个暗号，开一个新会话，先读一个匹配的文件再问它暗号，然后读一个不匹配的文件做反向对照。 14. 最后全部做完以后，可以帮我沉淀一下这个思路，方便以后有模型升级的时候，我可以再来跑一遍。

买了一个新玩具大疆 4p，很小巧 去线下试了试感觉两个摄像头效果会比一个好 这次出去玩试试效果给大伙分享

MiaoYan is a native Markdown notebook for Mac, iPad and iPhone, light and fast. I've been building it since 2020. It's AI friendly too. Notes are plain Markdown files, so agents can edit them, and the miao CLI lets them search, read and add notes. miaoyan.app/

刚刚 Agent 提醒我 Mole 的 Windows 版本马上就发布一个月了，让我去检查一下早鸟价的时间只有 2 天了，时间过起来真快，想给小伙伴聊聊这一个月上线，Windows 版本都做了哪些有意思的事情让它一个月卖到了几十个国家～ 由于 Windows 版本属于功能完善的过程，这一个月累计又发布了 15 个正式版本，从 0.10.0 到 0.21.2，打了 20 个 tag，累计提交代码 1084 次。代码上 C# 和 XAML 新增 6.2 万行，居然也删掉 1.2 万行代码，当前功能代码累计 9.6 万行。 为了保障产品的稳定性，测试类从 2032 个增加到 3302 个，多了 1270 个，测试代码从 4.1 万行涨到 6.7 万行，功能代码只比测试代码多 30% 了，很神奇，但在 AI 时代我认为也是正常的。 Windows 上面的各种软件测试也在继续，当前测试到了 482 款了，后面仍会继续下去，也欢迎小伙伴这里给我反馈一些需要测试的软件，让整体变得更加完善。 新增的功能上面不少是用户给我提的，非常感谢天使用户 @sujingshen @lihir55 @ldl123292 等专业的Windows 用户，给了我非常多的建议，比如当前分析页面终于支持多选逻辑了，你可以选中一批要删除的内容好比先加到购物车，等全部选完后一起删除。 软件卸载和更新的体验也大福增强，当前可以多路并行同时更新多个软件，软件卸载甚至增加了保留 App 只清理数据的功能，整体卸载扫描速度相比之前快了 5 倍。当然这里被诟病的 Windows 的 UAC 弹框也做了一些不打扰大家的工作，可以安心静心清理维护你的电脑。 状态页面能力也和 Mac 完全对齐了，支持蓝牙设备耳机键盘电量的展示。菜单栏小动物大伙非常喜欢，这次新增加了可以翼龙阿飞、阿獭、阿豚、阿龟，更加有趣。 在 Windows 市场售卖软件其实会远比 Mac 市场要难很多，为了做好 Windows上的效果体验，我对比了试用了市面上数十个同类产品在功能清理、卸载能力的差异，尽可能把欠缺的补齐到最好，当然还有很多不足，小伙伴们可以在使用过程中有任何建议问题都可以找我～ mole.fit/windows

太长不读 在代码没啥壁垒的年代，我们需要多做一点不可扩展的事情来让自己的产品形成一些自己的特色。 好比大模型把所有产品默认加到 60，也即之前我们认为的及格等于现在的 0 分。

Here's how I keep X clean without missing the good stuff from people I follow. I gave Grok this prompt, and you can try it too: Every evening at 8pm, put together today's highlights from the accounts I follow, plus others worth reading. Read posts only through the official X API, and skip anything covered the day before. Format: - Open with "Today's main threads" in 3 short sentences - One section per person, with their name and @, and a divider between sections - 2 to 4 points per section, each as a bold topic, then the content and a link to the original post. Use two to four sentences to cover what they said, the key details and the background - End each section with one sentence of your own take - Put small tools in a final "Tools" section - About 10 to 15 sections, no em dashes, no AI tone, keep it simple and clear Now I get this digest every day, so I scroll X less and stay a bit more focused.

MUJI 这个双层纱睡衣家居服好舒服，推荐买来在家里穿，哈哈但不推荐穿出去，适合开着暖气的冬天和不开暖气的春秋。

Pake V3.18 is out. It's an open-source tool that turns any webpage into a lightweight desktop app with one command, now at 62.9K stars. What's new: 1. The docs have their own site now, with a step-by-step getting started tutorial and pages for shortcuts, scripts and AI agents. 2. Dragging a file onto a page to upload it now always works. 3. Downloads keep their real names, so Annual Report.pdf no longer gets saved as Annual%20Report.pdf. 4. On Windows, downloads show the native WebView2 panel with progress, and a failed build no longer blocks the next one. Thanks to the contributors whose pull requests went into this release. github.com/tw93/Pake

🤣 笑死居然把这款漱口水在脆上面带火了 已经变成生活博主了吗？

最近上映的这个埃及的电影《生日快乐》很好看，推荐有空的小伙伴一看。

People often ask me how to use AI to design products that look good and don't feel like AI slop. It's not an easy question, since I'm not a professional designer, so I can only share it from a product engineer's point of view: how to make products that aren't ugly and are easy to use. First, one premise. A good-looking design can't save a product that doesn't solve a problem. Design is the icing on the cake, not what decides whether a product succeeds. If I had to rank priorities, it would be: solves a problem > easy to use > looks good. It's like food: first don't go hungry, then get enough to eat, then eat well. I won't say much about solving the problem, since that depends on the product itself. It solves a concrete need: someone needs it, there's a real scenario for it, and your product happens to offer a way for a person or an agent to get it done. Some problems are just bigger than others. So how do you make a product that's easy to use and not ugly? Ha, you can walk through the list below yourself, or hand the whole thing to your agent and have it review your product's codebase. 1. Pretend you're an ordinary user who knows nothing about tech. Can they get through the main flow and come out with what they need? Find every place where they get stuck, where something isn't explained, or where one step doesn't lead naturally into the next, and fix all of it, so people can use the product without a manual. Only where that's truly impossible, add a short hint. 2. Every piece of copy should read the way native speakers of that language actually talk. Choose your words carefully instead of translating flatly. Look at how Apple, Windows and well-known websites word the same thing, and aim for copy that feels simple, clear and natural to a local. 3. Where the product itself already makes something clear, don't add text to explain it. Don't over-explain. Check every line of helper text for whether it says what it means without padding, and if the interaction or the visuals already say it, don't say it again in words. 4. When you show a number, make sure people know what it refers to, and make it easy to read for what it means. Money, metrics, distance and other units each have their own best practices. Accuracy matters a lot, so don't skip validating the data to save effort. 5. Don't keep asking users to confirm something they already chose. Ask a second time only when an action can't be undone, so the screen isn't full of confirmation dialogs. Don't splash big red areas over dangerous actions either. Think about how pleasant the product feels to use. Users aren't stupid, so don't worry too much about them making mistakes. 6. Visually, keep one accent color per page. Try to avoid orange, terracotta, and the bright corporate blue of old admin dashboards. Make every gray a warm gray, never a cold blue-gray. If you can't find a good color, look through traditional Chinese colors. 7. Use as few font sizes as possible, at most four on a page. Think about the reading rhythm of the whole page, its clarity and text contrast, and make sure it meets accessibility standards. Line height, letter spacing and paragraph spacing all need repeated tuning, while the whole system stays consistent. 8. Use italics, monospace and all caps sparingly, and only with a clear reason. No italics for helper text, monospace only for code, paths and metrics, and no all-caps text in buttons or labels. Go easy on joining things with a middle dot (·). Use one verb for one action across the whole product, and avoid verbs that push people to act, like the marketing-style "Buy now". 9. Keep buttons, spacing, corner radius, dividers, dialogs, animation and shadows consistent and restrained, so they don't get in the user's way. Nested rounded corners should be concentric: the inner radius equals the outer radius minus the padding between them, and it looks better. Pages are flat by default: no stacked shadows, no glow, no frosted glass. Shadows are only for dialogs that really float above the page, and no cards inside cards. 10. In a multilingual product, lay things out for the longest translation first, and put meaning before looks rather than changing what the text says to make it fit. You can rewrite the copy, but don't change the font size or truncate it. Check that everything displays well at different sizes on the devices your users actually use, test them all, and fix everything that looks off. 11. For a design you keep tweaking without getting it right, or one that still looks off after many rounds, ask your agent for the three options it thinks are best and pick one, then tell it to keep refining until you're happy. I like having AI put before-and-after images into one PDF, which makes comparing them much easier for me. That's about it. One more thing matters a lot, though: your own patience and willingness to keep iterating. I'm a bit of a perfectionist, and I often go a dozen rounds with AI over a single line of copy, a color or a design until I'm happy with it. AI is smart, but you often need to ask more of it, and put in more time and patience to get a result you like. Or put another way, spend more time and look at more good design, and you can build products that are easy to use and not ugly.

假如你在杭州想尝试一下素食 一定要去试试庆春里，很好吃 特别是黑松露炒饭还有藜麦椒麻豆腐

最快乐的事情 当然是拆李志的 CD 然后立马播放！

经常有小伙伴问我，怎么用 AI 做出好看的产品设计，不那么 AI Slop，其实不是很好答，因为自己也不是专业的，只能站在产品工程师视角来给大伙聊一聊，怎么做出不丑且易用的产品。 首先要知道一个前提，很多时候好看的设计也救不了不解决问题的产品，设计在这里只是锦上添花的作用，而非决定产品的成败，假如要我选择产品优先级，应该是能解决问题 > 易于使用 > 好看美观，好比先解决不饿着、再解决温饱、最好解决吃好一样。 能解决问题这里不多说，更多取决于产品本身，它是去解决一个具体的需求，有人需要，有场景需要，刚好你这个产品可以提供一个解决方案让人或者 Agent 使用完成目标就好了，只不过解决问题有大有小。 那么如何做易用且不丑的产品呢？哈哈，可以照着走一遍，也可以把下面的这一大段给你的 Agent 让他去帮你 Review 一下你的产品代码仓库。 1. 把自己当做一个普通不懂技术的小白，他拿到我们产品，能否把主链路走完产出他所需要的东西，哪些地方有卡点，哪些地方没有讲明白，哪些地方的衔接不通顺，全部去修复，让用户不用说明书也可以完成产品的使用，假如实在不能，可以适当补充提示说明。 2. 所有文案需要符合对应语言当地人的使用习惯，需要仔细斟酌词藻，不要干巴巴的翻译，可以从 Apple、Windows 系统以及知名网站去找同类词的最好翻译和解释，文案做到尽可能让本地人感觉非常简单、易懂、清晰。 3. 产品上能用产品本身表达清楚的地方就不要再加文案说明，不要啰嗦的解释一个东西，仔细思考每一个说明文案是否达意且不啰嗦，交互视觉可以说清楚的地方就不要用文案再表达一遍。 4. 在数字的表达上需要让用户明白这个数据指的内容，以及考虑到数据表达意思后的易读，比如钱、指标、距离各种单位需要考虑到本身的最佳实践，数据的准确性非常重要，不要为了偷懒少了数据的校验。 5. 对于用户确定的操作不需要反复找用户确定，只有在会产生不可逆影响的时候二次找用户确定是否需要执行，防止满屏都是各种弹框确定，对于危险的操作不要出现大片的红，需要考虑用户操作一个产品的愉悦度，用户不是傻子不要过度担心会犯错。 6. 视觉上，一个页面只留一个强调色，尽量不要使用橙色、陶土色和后台常见的那种老企业亮蓝色，灰色全部用偏暖的灰，不使用冷冰冰的蓝灰，找不到合适的颜色可以去中国传统颜色里面去找到合适的。 7. 字号类型尽可能少一点，一个页面最多控制4种不同的字号，需要考虑到页面整体的阅读节奏感，清晰感以及文字的对比度，确保符合无障碍，包括考虑到行间间、字间距、段落间距需要反复调整，同时保持整体的规范一致。 8. 少用斜体、等宽字体、全大写，要用的场景必须要有详细的理由说明，说明文案不要使用斜体，等宽字体只用于代码、路径、指标，按钮和标签里面的字不要大写，少用中间点 · 来连接内容。同一个动作在整个产品里面只用一个动词，此外动词的考虑尽量不要催促用户去执行，比如少用立即购买这种营销词。 9. 页面的按钮、间距、圆角、分割线、弹窗、动画、阴影这类设计规范保持一致，同时保持克制，不打扰用户，嵌套的圆角要同心，里面的圆角等于外面的圆角减去间距会更好看。页面默认是平的，不叠阴影、不发光、不加毛玻璃，阴影只给真正浮起来的弹窗，不要卡片套卡片。 10. 在多语言的环境下，优先考虑最长文案的排布，优先考虑达意而非为了好看而改变原意，可以改文案，但不要变字号和截断。需要特别考虑在不同尺寸下的展示效果是否都良好，考虑到用户常用的设备，全部去测试，遇到不好的地方全部修复。 11. 对于反复调整不好的设计，或者做了好多轮都感觉不好看的设计，让 Agent 帮你出3个他认为最好的方案来让你挑选，然后你选择一个更好的，告诉他去优化，直到改到你满意，我比较喜欢让 AI 生成对比前后的图片放到一个pdf里面，这样我的阅读对比体验会更好。 大概就是上面这些，不过还有一个非常重要的就是你自己的耐心和反复调整，我比较强迫症，经常会因为了一个文案、一个颜色、一个设计和 AI 讨论十几轮，直到自己满意了才舒服，虽然 AI 很聪明，但是很多时候你对他的要求要更多，以及你需要付出更多的时间和耐心，才可以做出满意的效果，或者说你多花时间，多去看好的设计，其实就可以做出易用不丑的产品了。

疯狂推荐用这个来洗你的茶杯，咖啡杯，或者任何洗不干净的杯子碗 一点点下去，有魔法一样立马光亮如新！

Yesterday a reader sent me a message. They study computer science, and they feel AI can now do all of their homework and papers for them. They asked whether this field still has a future, and what advice I'd give for the years ahead. It made me think: if I could go back to my final year of college, what would I do to make the road ahead a little smoother, with fewer pitfalls? This is just my own limited view, and I'd love to hear yours. 1. I'd still choose computer science, then pick the sub-field I find most interesting, and use AI to amplify my work there as much as I can, so that right after graduating it already feels like leading a team. 2. Move to a city with a strong tech scene and plenty of tech companies, like San Francisco, New York, London or Seattle. If your degree and skills are strong enough, find a good AI company in the few blocks of San Francisco between SoMa and Mission Bay. Being that close to the AI labs will sharpen your sense of where large models are heading far more than anywhere else. 3. At work, get things done fast, and be willing to pay for good AI tokens so you can do them well and quickly. Push the projects you care about to 150%, and finish the ones you don't to a solid 80 in the least time possible. Don't waste time, so there's room left to learn more. Embrace new things eagerly, and be willing to spend money on the best AI. 4. Put half of your salary into VOO and QQQ as a regular monthly investment. You can also pick one or two tech companies you strongly believe in, like NVIDIA, Apple, or Anthropic once it goes public. Don't chase hot stocks, and don't speculate. 5. Find your partner earlier, rather than putting it off until you've been working for a few years. Watch how they handle problems and how patient they are. Look for the one who cares how you feel, stays optimistic, and stands on your side whatever happens. 6. Don't lend money to anyone, including relatives, classmates and old friends. Lending money will only weigh on you while you're young. Don't show off how much you earn, and don't spend carelessly. First grow your first pot of money to the point where you'd feel comfortable living for two years without working. 7. Keep learning, keep talking with people, and keep making fun things for the community, your circles and X. Build your GitHub and X accounts without chasing profit, so they grow into your personal brand. Always serve people assuming your users are good people. 8. Outside your main work, grow your own interests. Take some classes, whether photography, a musical instrument, sports, or even running and cycling. Life outside work won't get dull, and it gets you out and about more. 9. Health always comes first. Sleep matters, so never stay up late. Don't sit for too long, drink plenty of water, and walk more. Don't push too hard at work either. The first burst of energy fades, the second runs low, and the third is gone, so stretch out how long you can keep working. 10. In the end, find your own path to not having to clock in, as early as you can. You can still work, but you don't have to show up for a job. Earn money through your interests, expertise, strengths and what you keep learning, keep improving along the way, and enjoy making that money.