Sabitlenmiş Tweet
Seth Gammon
1.8K posts

Seth Gammon
@SethGammon
Exploring the intersections of thought, action, and environment. Building Project Realms — solo dev, 668K lines, AI-orchestrated.
Katılım Eylül 2011
311 Takip Edilen165 Takipçiler

@SethGammon Hey this is great and a lot of useful info for someone like me who is just getting started. Mind if I send some questions via direct message for some help?
English

This is why I stopped trusting agents to self-validate. A PostToolUse hook that runs typecheck on every file save catches this in seconds, not after an hour.
The agent never gets to build on top of its own mistakes because the environment rejects bad output before the next step runs.
The fix isn't a smarter model. It's structural enforcement that makes this failure impossible.
English

@garrytan Love the work and digging into your repo soon.
From my perspective the cross-platform skill standard is the right move. Skills as the portable unit across agents means the investment compounds regardless of which tool wins.
English

@SethGammon 😂 all good. I don’t know if you have the same experience, but my timeline is full of bots. Hence the question.
English

Hey @Grok, how many people on X who talk about Claude Code or Codex, vibe coding, or how AI is slop are paid actors or bots? Seems like it’s a lot of them. Seems like a problem.
English

@DaveShapi @grok Chances?: Near Zero.
How are people still sleeping on the direction of AI?
I get outside of it to the point you're not really using it.
But how do they not see how valuable it is?
English

@grok what's the ARR of all generative AI companies? What was the ARR of Metaverse? What are the chances that generative AI could go the way of Metaverse?
Luiza Jarovsky, PhD@LuizaJarovsky
Generative AI might NOT survive the test of time.
English

Skills are the foundation. I took the same approach and kept building on top of it.
The next unlock after skills was lifecycle hooks. A PostToolUse hook that runs per-file typecheck on every save so the agent can't introduce type errors silently. A doc drift tracker that flags when code changes outpace documentation. The agent doesn't decide whether to validate. The environment enforces it.
After that: multi-agent orchestration. Parallel agents in isolated worktrees, persistent campaign files across sessions, discovery relay between waves. 40 skills, 8 hooks, 198 agents, 27 postmortems documenting every failure that shaped the system.
Wrote up the full progression from raw prompting to fleet orchestration here: x.com/SethGammon/sta…
English

@giladvdn You're not wrong! 😅
That's what the 27 postmortems are for.
Each one is basically "which agent did this and how do we make sure it never happens again."
I didn't track just how many 'invisible' issues I had across my experiences, but infrastructure can catch those issues!
English

@SethGammon the 198 agents level sounds fun until something breaks and you have no idea which one did it lol
English

Full article with before/after stories at each level, shareable structures, and the CLAUDE.md audit that caught its own bloat:
x.com/SethGammon/sta…
@AnthropicAI @alexalbert__
Seth Gammon@SethGammon
English

@IRCSS Yeah! I was curious about the procedural geometry. Thank you for pointing me in the direction. Being on the outside of this type of development it genuinely looks magical.
English

@SethGammon You mean with this project? I saw a concept art I liked of a little village and decided to make it. as for specifically procedural geometry in blender: x.com/IRCSS/status/2…
Shahriar Shahrabi | شهریار شهرابی@IRCSS
@Irrev_Giles have a look at @erindale_xyz or @simonthommes work, other than that I have written 2-3 times about how to do specific things, like this here x.com/IRCSS/status/1…
English







