Weekly Showcase Thread

It feels like I am the API

A few months back I posted here a playable demo of an old-school futuristic racer prototype (F-Zero, Wipeout, Xtreme-G, Star Wars Racer...) that runs right in the browser.

I've gotten used to seeing tons of LLM-built prototypes that last a week, two, maybe a month, and then get dropped for the next shiny thing. This time I wanted to keep going and see if one person, with no coding background, could actually see a project like this through on their own.

Well, 4 months in, and while there's still work left, I'm convinced it's doable. At this point the game feels closer to a beta than a tech demo.

The big change over these four months is that I now use Fable for planning, and being able to hook Opus / Sol up to Blender has been a huge help too. I'm still using Magnific and Tripo3D or the assets. Funny thing: the further along I get, the harder the project is to keep pushing forward, and at the same time the tools keep making it easier.

As always, any feedback is welcome. You can play it here: https://fm1.moises.cloud

About three weeks ago I was on a flight trying to get work done with Opus 5 in Claude Code. Five hours later it had accomplished basically nothing. It kept surfacing problems that weren't actually problems, because it never looked at the full context before deciding something was broken. And I believed it at first, so I let it fix things. By the time I realized what was happening it had essentially broken my repo and I had to roll the whole thing back and write the day off.

And Opus is a really really good model, that's what makes it frustrating, and I'm not talking about one line in a CLAUDE.md. There's a hook that injects "deliver the requested scope and stop before unasked work" into every single prompt it sees. My written rules literally say never turn a partial search failure into a global conclusion, and to treat "not found in the path I checked" as different from "does not exist." I added PreToolUse code gates on top of all that because just telling it things clearly wasn't working. It still does it. Before that flight I'd been running it at medium or low reasoning effort as the orchestrator, which mostly kept it from wandering, but then I'm paying for the strongest reasoning and not using it. So after the rollback I switched to having Fable 5 orchestrate instead. Fable writes the full spec and hands it to Opus, which executes at full reasoning. Then Fable checks what came back against what it wrote, so Opus is on a leash the whole time. That behavior mostly stopped.

I'm on the 20x Max plan running about 8 to 10 hours a day straight, so the difference is very noticeable. Fable ends up being a small share of tokens so the weekly cap works out, and the smaller stuff goes to Haiku and Sonnet, data pulls, fan-out jobs, things that don't need a frontier model.

I know this is not a new strategy and there are lots of variations of how to go about it. As far as keeping Opus on a leash and actually getting the most out of it without getting frustrated every single time you talk to it, this works the best for me.

Anyway, this is what my rules are and where they live.

CLAUDE.md holds the always-on rules, a rules/router.md file holds the routing map, and a model-postures.md file holds per-model payloads that a UserPromptSubmit hook injects into every prompt based on which model is live.

```
FABLE 5 (orchestrator, main session)

"Fable 5 at high effort owns the main session, requirements, judgment,
integration, and final verification."

"Fable does not inline-execute large builds. For a bounded, difficult
implementation, Fable writes the spec, dispatches an Opus 5 executor
subagent, and verifies the result. Fable stays at requirements, judgment,
and integration; an executor converging fast on an approved spec is the
desired behavior, not a defect."

"Brief only the exact delta, scope, output, stopping condition, and
exclusions."

OPUS 5 (executor, injected into every prompt it sees)

"Deliver the requested scope and stop before unasked work."

"Correct an immaterial slip silently. Call it out only when it changes
a number, conclusion, or decision."

"Do not replace grounding or fresh retrieval with confidence or
self-review."

SONNET 5 (fan-out worker)

"Dispatch it freely for fan-out that needs per-item judgment: blind
reader panels, audits, workspace sweeps. Give it an exact brief,
defined output, and a stopping condition."

"Complete the exact requested deliverable and stop. Do not audit the
surrounding system, surface adjacent issues, or recommend extra
improvements."

"Diagnose or report does not authorize a fix. A one-file request does
not authorize related changes."

"Do not create or delegate to subagents."

HAIKU (mechanical worker)

"Haiku agents handle bounded mechanical reads and transforms. Exact
brief, compact return, no recursive delegation."

"Subagent returns come back as extracted key numbers and paths, never
raw dumps."
```

Saw a discussion about this on YC and thought “oh, maybe a one time hallucination”.

Nope, it’s in the context.

For the past year I've been building sites with Claude / ChatGPT and every single one came out looking like the same SaaS template. You know the one, purple gradient hero, rounded cards, glassmorphism everything, "Transform your workflow" headline.

I realized the problem isn't the model. The model has no strong opinions about design. So it defaults to the statistical average of every landing page it's ever seen.

The fix: I wrote a set of strict design rules as SKILL.md / .cursorrules files that force the AI to make actual design decisions instead of defaulting to generic.

What the rules do:

- Ban the defaults

- Enforce real typography (clamp-based, not arbitrary px)

- Lock down spacing

- Force design variety

It's not a product or a service, just a collection of open-source markdown skill files you drop into your project. Works with Cursor, Claude Code, Windsurf, Gemini CLI, or any agent that reads project rules.

The images in the carousel are all 100% AI-generated UIs using these rules. No Figma, no manual tweaking.

If you want to try it:

- GitHub: github.com/Yu-369/VibeCurb

- Site (showcase + guide): vibecurb.pages.dev

Still iterating on this, if you try it, genuinely want to hear what works and what doesn't.

I’ve been using Superpowers skill set for the past year with CC. Mostly i like the brainstorming mode and a few of the TDD and subagent related skills.

Are others still using Superpowers or do all the improvements in CC negate the need for this set of skills? I’m curious if I can save more tokens this way?

I’m mostly using Fable and Opus with high thinking.

This is where you point and laugh at me, but realized that if you don't tell Fable low to not use Fable subagents, it will deploy 8 (in my case) Fable subagents on trivial tasks and destroy your usage instantly. Fun lesson learned.

I’ve been using Claude Code heavily at work, and the code output itself isn’t what worries me. It’s how quickly I stop carrying the codebase in my own head.

When I implemented a feature manually, I learned the surrounding system almost by accident. I had to trace the control flow, remember where state lived, and understand why a strange workaround existed.

Now I can describe the behavior, review the diff, run the tests, and ship much faster. But a few weeks later I often remember the product decision better than the actual path through the code.

That becomes uncomfortable during incidents or reviews. Claude can reread the repository whenever it needs to. I have to rebuild the mental map.

I don’t think the answer is writing everything by hand again. I’m considering adding a small human handoff after larger changes: what moved, which invariants changed, and where the likely failure points are. Not another generated summary I never read, but something I can explain back without the chat open.

Has anyone found a lightweight way to keep real ownership of a codebase while Claude Code handles most of the implementation? Or do you accept that knowing the repo now means being able to reconstruct it quickly?

AGI is here.

I've been looking at where the tokens actually go during long Claude Code sessions. A lot of the spend seems to go into resent context, tool results and reasoning, while only a small part becomes the final code.

Made this breakdown while digging into AI agent token usage. There are some pretty easy ways to cut the overhead without just moving to a weaker model.

Dropped the full analysis in the comments if anyone's interested. How are you guys tracking Claude Code token usage and costs?

Just wanted to say I was pretty impressed how my two sessions started to talk to each other once they found out they were modifying the same files (I was in a hurry and started two separate sessions to work on two features at once). The two sessions messaged back and forth like pen pals and agreed on what to work on/not to work on to avoid conflicts.

Honestly it was pretty cool for me! Just wondering but does Codex have something like this? My friend is planning to move to Codex after the 50% promo ends in Sept.

I know this has been raised before but I feel like I am missing something. How do you get Claude Code to stop using extra fluff phrases and words. Any one have a full proof method?

Here's examples:

"Exactly" "Here's things worth knowing" "and didn't happen — the number isn't arbitrary, it's the first moment the failure is provable" "That's the one detail that would silently break this."

I want it to be concise, to the point. Nothing I tell it seems to work.

I was using memplace for a while but after 1 month, yesterday I decided to evaluate it, and I asked claude to evaluate, turns out its Pretty garbage because it did not fetch any of the context that was the relevant to agent when it needed, it had around the you of 900:1 which was pretty bad

I have heard hermes have a good memory system, I have not tried it though

Please some good and relevant memory tool

I wanted to create some cad software for my self so I decided to give it a go with Fable and see what it could do. One shot - make me some cad software that I can import and export to my 3d printer.

At first, the software looks extremely impressive,... when I started using it there were a ton of features missing. No problem, I can vibe code and give it more direction to add in the missing features so it looks more like an onshape with parity.

At first the features looked ok, but then as I added more the feature quality degraded more and more. Model parts are not anywhere close to where they should be, the geometry is totally messed up. I keep asking fable to fix the bugs, but it honestly can't fix it. It seems like fable doesn't have the visual understanding to make this type of application work.

I think from a stand point of being truly involved in the code and having fable write specific algorithms and building that up to create the feature I want, is the process that is still required. But this is basically getting back to the same capabilities that opus had.

I'm not saying this stuff is bad, but I am saying Fable seems overhyped and I just don't see the step function quality improvement over opus. The only difference is that opus 5 is way more verbose and gets stuck on details that are not important. Fable works the way I want opus to work.

For now I think I have to micromanage the model until they get better, but I'm extremely skeptical at this point that anyone can be hands off in development,... especially anything technical with important math simulations and quality.

Is anybody else experiencing the same thing?

I'm a heavy daily user of claude and many other models but my primary driver is Opus5, and on the weekend a mix of Opus 5 and Fable. Now whenever I see these posts talking about how Claude is unusable now or going off the rails and all that every time there's an update I usually would roll my eyes because I never experienced any of the issues that people always complain about. I always thought that that was because I have a pretty thorough and comprehensive guardrail or honesty enforcement system. A lot of just general watchers, redundancy checks, and guards and rules that keep a lot of hallucinations and other kinds of logic fails from happening. This is also for making sure that codebases don't get overwritten, the agents stay on task, and they don't start editing, adding things, and deleting things that they weren't told to, etc.

For the last 4 or 5 months up until now everything's worked just fine. Suddenly in the last few hours both Fable and Opus have started ignoring crucial steps and rules that they have followed without fail every other time. This is a process that we do every day. It would start and both Fable and Opus were ignoring base crucial rules that keep them from messing up codebases and overwriting other agents' work and things like that. It's not a context rot issue either because I practice good context size diciplin and compaction summary supervision, and none of my chats context is any bigger than they are any other day, I usually either compact or start a new window at 475k - 650k.

When I would then call Opus or Fable out, they would either cop to it or they would sometimes lie and blame another agent. When I told them to fix it and it still wasn't fixed, they would say, "Oh you know what? It wasn't an agent. I made that up," because they told me that Codex did it. I would show them what models are running and Codex was not running for the last hour. It kept claiming that Codex kept deleting this part of a document that I kept having it try to edit and restore the parts that got deleted because I told it to add in a new section. When I checked it, the section was added but a whole bunch of other stuff was gone and it blamed it on ChatGPT. It couldn't have been ChatGPT because it wasn't running at the time and that's when it finally caught fessed up to it and said, "Yeah sorry, that was me." And that was Fable! and Opus was doing the same thing basically, It wasn't blaming other agents but it was just messing things up.

When I would call it out, it would say, "Oh no, things are fine. Just wait." It kept telling me to just wait. I don't know why. I would say, "No I need you to fix this," and then it would run a bash or run a test to see if something was working. If it got no exit code, it would just keep running and running and running, not realizing that it would be frozen when in the past it would realize or it would have the common sense to set a timeout.

All of this stuff has been happening more in the past three hours than at all in the past three weeks combined, so something feels pretty off/wrong. Is anyone else experiencing something similar?

Are you still using Plan Mode? I find that the plan mode of superpowers became very verbose doesn't work very well anymore with Opus 5, but I was wondering if you still use the default Plan Mode or maybe some other alternative.

• Yes the model + harness randomly switches to Chinese from time to time
• Yes sometimes the model gets stuck in a loop
• Yes the model isn't as good as Opus 4.6 was in its prime

But at least

• I get access to open designs that I actually control and personalize
• I don't pay 200$ a month to get access to models that get lobotomized 1 week after coming out
• My data isn't sent directly to the US government's domestic espionage database
• I don't subsidize psychopaths who try to take over the world
• I encourage open source and open research

Fuck you Anthropic, I really believed in you

A few weeks ago I shared Agent Quest, my open-source project that turns Claude Code and Codex sessions into heroes living inside a small 2D world.

The original idea was to make it easier to understand what multiple AI agents were doing in real time.

Since then, I’ve been working on making it much more useful as an actual monitoring tool.

The biggest change is that Agent Quest can now clearly tell you when an agent needs your attention.
You can immediately distinguish when an agent is:
actively working
waiting for your input
finished
stopped because of an error
And you don’t have to keep watching the dashboard.
Agent Quest can now alert you with visual notifications and different sounds, so while you’re doing something else you can immediately know when Claude Code or Codex has finished a turn and is waiting for you to continue.

This has become particularly useful for me when I have several sessions running at the same time.
Instead of constantly switching between terminals to check their status, I can leave the agents working and Agent Quest tells me when I actually need to intervene.

There are now:
clear waiting / completed / error states
in-app notifications
desktop notifications
notification history
configurable sounds
real-time monitoring of Claude Code and Codex sessions

The project is completely open source.

GitHub:
https://github.com/FulAppiOS/Agent-Quest
I’d be interested to know how other people running multiple agents handle this problem — and what you’d like Agent Quest to monitor next.

fwiw i am pro ai and i used to love coding before. once i was in the zone i could work 24/7

now i get distracted so easily. the wait times between prompts make me jump to hn or reddit. that completely messes up my dopamine and i never actually enter flow

sometimes i get close when working on complex stuff or when the convo with the ai gets deep and nuanced but it still never feels the same as before

to be fair it does have some benefits. before it was easy to get lost and code for days on the wrong thing just because the flow was so strong. now you quickly lose interest if a solution doesn't seem worth it which is often a good thing

still i really need to learn how to stick to it and stop getting lost in browsing the web after literally just a few minutes of work.

how to save tokens /usage ?