Bifalgorithm post

This GitHub user spent 10 months building a private cloud code setup on live production work. And he just made the whole thing public. And if you're new to this, a skill is basically a set of instructions cloud reads before it writes any code. Instead of one cloud trying to do everything, this hands every job to whoever is actually built for it. You ask for a feature and it pulls in the sub agent that writes it, the one that reviews it, and the one that checks it for security holes. That security piece runs a 102 checks across your setup hunting for the stuff that leaks. There's also a memory vault, plain markdown files sitting on your own machine, so what Claude learned about your project on Monday is still there on Friday. And it carries across tools, so you can start something in Cloud Code and pick it up in Codex without re-explaining your project. But here's the part most people miss. Every session you run, everything you and Cloud figured out together, normally that just disappears the second you close the terminal. This setup watches your sessions and turns the things that worked into brand new skills, automatically. So it gets sharper the more you use it. That is the big game changer. So if you want it, comment, stack and I'll send it to you or check the pinned comment down below. And like and follow because at 500 likes I'm dropping a tutorial on this.

This GitHub user spent 10 months building a private cloud code setup on live production work. And he just made the whole thing public. And if you're new to thi…

Bifalgorithm
Sign up
Feed/

This GitHub user spent 10 months building a private cloud code setup on live production work. And he just made the whole thing public. And if you're new to this, a skill is basically a set of instructions cloud reads before it writes any code. Instead of one cloud trying to do everything, this hands every job to whoever is actually built for it. You ask for a feature and it pulls in the sub agent that writes it, the one that reviews it, and the one that checks it for security holes. That security piece runs a 102 checks across your setup hunting for the stuff that leaks. There's also a memory vault, plain markdown files sitting on your own machine, so what Claude learned about your project on Monday is still there on Friday. And it carries across tools, so you can start something in Cloud Code and pick it up in Codex without re-explaining your project. But here's the part most people miss. Every session you run, everything you and Cloud figured out together, normally that just disappears the second you close the terminal. This setup watches your sessions and turns the things that worked into brand new skills, automatically. So it gets sharper the more you use it. That is the big game changer. So if you want it, comment, stack and I'll send it to you or check the pinned comment down below. And like and follow because at 500 likes I'm dropping a tutorial on this.

C
Connor Fraser
8w

"10 months building a private cloud code setup on live production work."

👍
0
0 comments0 shares

Sign in to view and post comments.