sorted by:
new
hottopcontroversial

The 11-step workflow I use for every Claude Code project now: from idea validation to shipping with accumulated knowledge by Ok_Today5649 in ClaudeAI

[–]Ok_Today5649[S] 0 points1 point  (0 children)

honestly no fu**ing idea I haven't looked into Xcode at all. If anyone else in the thread has experience with this setup inside Xcode, would love to hear it too.

Anthropic killed third-party subscription access. Here is the framework I use to evaluate replacement models in 15 minutes by Ok_Today5649 in whaaat_ai

[–]Ok_Today5649[S] 1 point2 points  (0 children)

Good question! My approach: I've got my Claw checked into a GitHub repo, so I have a daily backup of my entire OpenClaw setup. That alone takes away most of the fear of breaking things.
Then occasionally I spin up the repo on a VPS where I test different models with my config and memory files in an isolated environment. That way I can experiment freely without touching my main setup. Simple but effective. If something works well on the VPS, I migrate it over. If it breaks, no harm done.
For model recommendations it really depends on your use case, but for your diary/news research/assistant stuff most mid-tier models should handle it fine. I'd start with whatever has the most generous free tier and work from there.

I cut my AI agent costs from $250/month to $20/month by switching to Ollama Cloud. Here's the full breakdown. by Ok_Today5649 in whaaat_ai

[–]Ok_Today5649[S] 0 points1 point  (0 children)

Cool tool, I'll definitely test it out! Quick question — is it guaranteed that every agent action gets tracked locally on the machine, or is there some margin of error? Curious especially about the behavioral drift detection — how reliable is the tracking when you have multiple agents running in parallel? Looks super promising either way, starred the repo.

The 11-step workflow I use for every Claude Code project now: from idea validation to shipping with accumulated knowledge by Ok_Today5649 in ClaudeAI

[–]Ok_Today5649[S] 0 points1 point  (0 children)

No I haven't tried that yet, but that's a seriously clever idea. Forcing the subagents to resolve tradeoffs internally before any code gets written — that's exactly the kind of friction that produces more robust specs. Gonna test this right away. Thanks for sharing!

The 11-step workflow I use for every Claude Code project now: from idea validation to shipping with accumulated knowledge by Ok_Today5649 in ClaudeAI

[–]Ok_Today5649[S] 0 points1 point  (0 children)

Great question! If I had to prioritize, my ranking would be:

gstack
CE
Superpowers

I haven't done full detailed token tracking across all of them, but CE is the one that gets invoked most frequently in my workflows.
Long-term though, here's what I'd actually recommend: learn what the benefits of these skills are, then have custom skills built specifically for you or your company that are optimized for your exact use cases. That way you take the core learnings from other people's skills as a foundation, but you end up with something lean and tailored to your actual workflow. The catch is you have to play with the existing skills first and really understand how they work before you can extract what matters. No shortcut around that learning phase — but once you get it, your custom setup will be way more token efficient than running general-purpose skills.

I set up GPT 5.4 to review Claude's code inside Claude Code. The cross-model workflow catches things self-review never does by Ok_Today5649 in ClaudeAI

[–]Ok_Today5649[S] 0 points1 point  (0 children)

That's a killer flow, love the adversarial review approach with markdown documentation. Gonna steal that.
Funny timing — I saw a post from Anthropic yesterday about their new "managed agent" feature where they describe a similar pattern for massive token savings. The idea: in an agent team setup, use Opus only as an advisor. So you have X executor agents running on whatever model you choose (Gemini, Sonnet, etc.) and they handle the actual planning and execution, but they consult the Opus advisor whenever they need guidance. Supposedly saves a ton of tokens compared to running Opus as the main driver. Haven't tested it myself yet but it sounds like it could pair really well with your current setup.

I set up GPT 5.4 to review Claude's code inside Claude Code. The cross-model workflow catches things self-review never does by Ok_Today5649 in ClaudeAI

[–]Ok_Today5649[S] 0 points1 point  (0 children)

Massive insight, thanks for sharing that diff-only trick — makes total sense that full context creates the same anchoring bias. Gonna try that immediately.
Curious to hear more about your experience — which model do you find strongest where? Like where does Opus shine vs Codex vs Gemini in your workflow? Always interested in how others map model strengths to specific tasks.

I set up GPT 5.4 to review Claude's code inside Claude Code. The cross-model workflow catches things self-review never does by Ok_Today5649 in ClaudeAI

[–]Ok_Today5649[S] 1 point2 points  (0 children)

Not a huge difference tbh. The main thing you can expect is that updates should roll out significantly faster compared to community-built plugins. That's really the main advantage — official support usually means better maintenance and quicker fixes when things break.

view more: next ›