Activity
Mon
Wed
Fri
Sun
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
What is this?
Less
More

Memberships

Glitch Cat Club

34 members • $29/month

The Agent Hub

30 members • $1/month

Vibe Coders

1k members • Free

AI Laugh Lab

167 members • Free

Zero To Founder by Tom Bilyeu

2.7k members • $119/m

AI with Apex - Learn AI w/ Max

383 members • $9/month

Early AI-dopters

1.3k members • $77/month

AI Developer Accelerator

11.3k members • Free

AI Automations by Jack

3.3k members • $87/month

14 contributions to AI Developer Accelerator
As Promised: The Corpus Analysis Meta Prompt We Discussed This Week
As promised during this week’s coaching call, and at the request of several participants, I’ve published the meta prompt we discussed as a GitHub Gist. The goal is to turn a frontier reasoning model like Claude Fable into a strategic analyst instead of just a coding assistant. Rather than focusing on a single project, it analyzes an entire development corpus, mines previous AI sessions and memory, reconstructs intent across projects, identifies hidden opportunities, and identifies the handful of problems that are actually worth spending frontier-model tokens on. If you’re juggling multiple AI projects, agent frameworks, research initiatives, or a growing codebase, I think you’ll find it useful, or at the very least it’ll give you ideas for building your own version. All values in <%YOUR VALUE HERE%> need to be replaced by your real information. !!! WARNING I altered the prompt to target 'high' or 'xhigh' Effort in order to try to contain the token usage, but when I ran it, I ran it on UltraCode. ONLY do that if you are ready to spend an entire 5-hour reset limit on a single prompt run. On UltraCode this is insanely token hungry WARNING!!! GitHub Gist: https://gist.github.com/hopchouinard/60d4d6e0d477e22d344ef75489fb2149 If you improve it or adapt it to another model, I’d genuinely be interested in seeing where you take it. The prompt is only half the idea. The methodology behind it is what I hope proves useful over time.
0 likes • 27d
@Patrick Chouinard Finished it. Two changes from yours: everything that's not Fable-worthy becomes a fully spec'd task for Opus to execute cold. Kept your Fable-worthiness triage and the personal-operating-system phase. Those were sharper than my first draft. Ran it against propria-core. 25 agents. Found a live unauthenticated endpoint leaking data and API tokens sitting in git history. Can send the full prompt if you want it.
1 like • 27d
Attached. Genericized the paths and stripped a business-specific ranking section I use internally — everything else is intact, including the parts of yours I kept as-is. @Patrick Chouinard
Live tomorrow 2 PM ET: watch builders demo what they shipped with Claude Code
Live tomorrow 2 PM ET: watch builders demo what they shipped with Claude Code Tomorrow (Wednesday) at 2 PM ET we run our weekly Show & Tell. Builders get about 2 minutes to demo something they actually shipped with Claude Code or Codex, then about 5 minutes of honest feedback from the room. Real builds, real feedback, no slides. Free to watch, no signup: https://shipsafe.franklabs.io/watch That page can also email you the live link an hour before we start. Nothing else, unsubscribe any time. If you want to see how other people run Claude Code and Codex day to day, it is a good hour. Come lurk.
4
0
I SOLVED Claude Code forgetting what it was building
Deep in a session, right when I understood the work best, I wrote down what to build next as a short structured capsule. Then I cleared the context. A fresh session with none of that understanding read the capsule cold and built it to spec. It did not know it was finishing its own work. Handoff notes fail two ways: they ROT (you forget) or they CANNOT TRAVEL (a fresh session can't read your mind). And terse notes silently drop the two things that matter most: WHERE the work goes and what DONE looks like. I measured it. Labeled-field capsules scored 10/10 on intent fidelity vs terse prose at 9.67, and prose's weakest spots were exactly WHERE and ACCEPTANCE. The honest part: the model still ran ~31% of malformed input instead of refusing it, so that check is deterministic code, not a model call. It understands the capsule. It does not get to decide the capsule is safe. Free CLI and Claude Code plugin, MIT. Try authoring one capsule next time you are deep in something, then clear and let a fresh session build it. github.com/gtsbahamas/intent-capsule
2 likes • Jun 17
@Patrick Chouinard @Paul Miller @Morgan Cook Here it is, in all its glory!!
Use your AI agent with both hands. Here's the seatbelt.
OpenClaw, NanoClaw, ClaudeClaw. An assistant in your chat that reads your inbox, remembers everything, and gets things done. Lean in. The people getting the most out of them aren't the most careful. They just wear a seatbelt, so they can drive faster: - Read-only to start. Let it earn more. - It asks before it sends, deletes, or pays. - Its own space, not your main account. That's most of the protection, at zero cost to what it can do. Full playbook, plain English, no login. Plus a prompt your agent runs to audit itself: https://shipsafe.franklabs.io/agent-safety Which one are you running, and what have you got it doing?
1
0
Sharing what new have built during last 5 months.
Hi all, I kind of dropped off from the community during last few months as I got a good gig at a large bank to build an AI AML platform for them. But I will be dropping in again .. Sharing how my SDLC agentic harness look like and how I make sure quality of code I produce is high. I am still doing all this inside Claude Code. Can give a demo or presentation if community is interested.
0 likes • Jun 2
@Dmitry Avramenko Looks interesting but there is no GitHub repo??
1-10 of 14
Ty Wells
3
25 points to level up
@ty-wells-7394
A curious and resourceful developer who thrives at the intersection of creativity and precision—comfortable navigating the latest AI-powered tools.

Active 9h ago
Joined Apr 25, 2025
Powered by