#教程/实践

我很好奇一个问题： 大家在不同的 Coding Agent 之间到底怎么共享上下文？ 比如我现在在Claude Code里跑完了一个项目，或者项目跑到一半，然后需要在CodeX里继续。 这两块的上下文怎么衔接比较好？有没有优雅的解决方案？

【Tripo × Astra / Opus / Argon × Blender】 ３Dモデル完成しました✨ -------------------- 制作スキルはリプ欄で配布いたします! GithubURL添付いたしますので、良ければご活用ください！ -------------------- 制作期間はおよそ２週間（実質１ヶ月ですが、品質微妙で２回作り直しました💦） 簡単に制作ステップを解説すると以下の通りです。 ✅ 顔・身体・髪の毛・表情毎の３面図・アクセサリー類のイラストを作成 ✅上記のモデルをTripoで全て作成 ・全部SmartmeshP2.0 四角形5000～10000くらいのポリゴン数がおすすめ ・ポリゴン数が多すぎると、補正時に歪みやすくなります ✅各パーツをBlenderMCPで結合 ✅簡単な小物・装飾類は直接モデリングで作成してもらう ✅眼球のモデリング・手を補正 ✅リグ挿入・スキンウェイト調整、IK/FK制作 ✅揺れもの調整 ✅シェーダー調整 ちなみに翼の開閉もできるようにしました🔥 これは翼の構造自体をしっかりAstraに考えさせ、羽の配置を一枚一枚しっかりモデリングさせました！ 気合でこれくらいの品質のものまで作れるのはホント凄いですね💦 #Tripo

Vibe coded hardware is here, and amazingly fun! This week I'm covering how to use @OpenAIDevs Codex, @CloudflareDev Workers and the Zectrix Note4C to build your own custom eink display. I made a train tracking screen 🤓🚂 https://jamesdevonport.com/p/can-you-vibe-code-hardware

pstack is the new solid

it's easy to fall into the trap of micromanaging your agents instead of correcting the environment that shapes its behavior. pstack 0.15.9 now ships a new /correct skill: if you keep correcting agents for the same mistakes, it finds the pattern and fixes it with architecture, types, and checks. i like to imagine that commits rapidly flowing into the codebase are like a bonsai tree rapidly growing in whatever direction it pleases. what you want to do is not to give in to the chaos, but tame it intentionally with the right constraints 0.15.9 also has improvements to: • /architect: now includes instructions on designing agent friendly architecture • a new /benchmark-checklist skill based on @brendangregg's benchmarking checklist here's a prompt you can give to grok bot to start architecting a better codebase with pstack: /poteto-mode create a new Project agent to refactor and rearchitect my repo so that our architecture is more agent friendly. it should use both the /correct and /architect skill to look through past commits and find the most common pitfalls that agents fall into, whether its with code quality, performance, or bugs. if relevant you can also use the /recall skill to find past conversations for context. it should make a high level plan for me to review. it should also answer its own open questions by prototyping rather than defer to me. come back to me with a plan backed by real data. once i approve the plan, use either the stack or full autopilot playbook (ask me which i want) to execute

ban and delete most if not all code comments! agents love copying what already exists. a seemingly harmless comment explaining some temporary workaround is one of the worst viruses you can have in your codebase. like a weed it'll spread quickly as a tool for agents to quickly get their job done. before you know it, your codebase is overrun with hacks and stale comments. just one more workaround bro you can use pstack's /no-comments skill as a weedkiller. it'll seek out useless comments while keeping the ones that actually should exist (like explaining a browser quirk), and figure out how to solve them on a first principles basis here's a prompt you can try asking @bot: create a project agent that uses /poteto-mode to spawn a /swarm to use /no-comments and identify useless code comments we can prune in my repo. come back with a high level plan of which of these workarounds would be best solved by refactoring and which we can straight up delete https://x.ai/bot/plugin/9717366

https://x.com/i/article/2110601994578866176

让不同平台的个人 agent 相互通讯的极简方法：电子邮件！Grok Bot 先行一步，你可以给自己的 Bot 配置一个邮箱 xxx@mail.grokbot.com 这种，例如我现在要让我的 Grok Bot 和我的 Muse Agent 之间相互发指令，可以拿 Gmail 当中介，设置一个 Gmail 的别名（xxx+muse@gmail.com）给 Muse 使用，然后通过邮箱和签名来验证，最后让你的 agent 信任这个邮件地址，发消息不需要通过你确认就可以了。 现在 Gmail 就是没法 push 消息，需要每 15 分钟检查一遍新邮件，所以说消息没法即时，其它都很方便！如果想用更强大即时的方案，可以用 @turingou 同学做的服务 http://yobiru.com 👀