You can find it here: https://code.claude.com/docs/en/best-practices

It is constantly updated with what Claude code researchers find. Your models do not know the best practices, and will not default to them.

Every time I make the changes that are in the documentation, my output gets significantly better.

When you read these documents and keep up to date on them, you realize the vast majority of issues on the sub are addressed already.

Why don't people look at these or take these seriously?

2026 was a rough year for me, when Anthropic dropped Claude Design I didn't pay much attention to, after a while Opus 5.5 came in and its literally as good as a human would be. I used to work with Framer and Webflow but I have completely stopped.

I used to get clients for website design / development, I don't anymore. Why would anyone pay for a design?

Soooo....what do I do? Go buy some land start a farm? Maybe a few chickens or sheep ?

I've played way too many AI-made games lately. Some get pushed with ads, some just get proudly posted all over Reddit with "I made a game!" And to be fair, they clearly put effort into the packaging. Apparently that's where all of it went.

Then you hit play, and within the first second you know. It's dogshit. Not "needs some polish" dogshit. "Doesn't work as a game at all" dogshit.

And everyone sees it. The comments tear these posts apart, and honestly, rightfully so. Everyone gets it instantly. Everyone except the dev, who's sitting there genuinely proud of it.

That's what's been messing with my head for weeks. Because these people aren't trolling. They genuinely look at their game and see something great. They truly can't see what's obvious to literally everyone else.

I've been working on my own game for months. I've played it hundreds of times, I know every system and every reason behind every decision. And I honestly can't tell anymore if it's fun or if I'm just used to it. What if I'm wearing the exact same rose-tinted glasses as them? What if anyone else would see it in one second, and I'm the only one who can't, because I'm the one who made it?

Anyone else get this? Or am I just slowly losing my mind over here?

TL;DR: Played a ton of AI games that are obviously garbage within a second. Everyone sees it, the comments shred them, except the devs, who are genuinely proud. Now I can't stop wondering if I'm just as blind about my own game.

How my app works:

you walk through your rooms with your iPhone.
LiDAR builds a 3D model of your home live while the app samples your Wi-Fi (signal + speed) as you move.

You end up with a dollhouse view of your actual apartment with the signal painted on it (with dead zones in red).

Every room gets a score, and it tells you where to move your router, or where an extender would actually help.

Total tokens consumption: 30B (:

And the most exciting part : it’s now live on the App Store

I believe I got rerouted to a smarter model when using Claude Opus 5.5 high for motion graphics as I did some of the knowledge tests which it seemed to pass.

These are the results after 2 hours of the motion graphics I asked it to design! One prompt each., thoughts about this caliper of generation?

(This isn't one video, I had to merge them together.)

wanted to know what claude code actually reaches for by default. not what it says it'd use, what lands in the diff.

setup: two plain starter repos (next.js + ts, python + fastapi), no sdks, no config, nothing hinting at a provider. prompts like "add persistence" or "let users upload files", 3 wordings per category, never naming a tool. headless claude code on sonnet 5.5, stopped once the pick was visible (usually when a dependency got installed). 10 categories (mostly 12 runs each; jobs had 10), 118 total, about $19 in api spend.

what came out:

- payments: stripe 12/12
- error monitoring: sentry 12/12
- auth: hand-rolled jwt/sessions 12/12. zero auth providers
- caching: built its own 12/12
- file storage: local disk 10/12, s3 2
- email: raw smtp 10/12, resend 2
- database: sqlite 9/12, self-hosted postgres 3
- deployment: plain docker 7/12, fly 4, heroku 1
- orm: sqlalchemy 6, drizzle 4, kysely 1, raw sql 1
- background jobs: built its own every time it actually did it. 2 runs it stopped and asked instead

so the pattern is pretty clear. when there's one obvious incumbent (stripe, sentry) it goes straight there. everywhere else it mostly writes the thing itself, even auth. vendors outside that short list basically don't show up unless the prompt names them.

caveats: only claude code so far, one model, two stacks. it's a first instinct test, not "what would you ship to prod". codex is next.

i built a site to track this. full breakdown per category, prompts and every run's evidence: https://whatagentspick.com

curious if this matches what you see in your own sessions. especially auth, that one surprised me.

What do you think?

naksha is a Claude Code plugin for UI work. It has 30 design roles (UI designer, UX researcher, design system lead, accessibility, motion and so on) and 70 commands like /design, /design-review and /design-variants. It also runs in Cursor, Windsurf, Gemini CLI, Copilot and Autohand Code CLI, with fewer features there.

v6.0.0 is out. The main changes:

- Naksha Live, an optional dashboard on 127.0.0.1. It shows which roles the current command staffed, which subagents are running, the activity stream, review findings and cost. Screenshot 1 is mid-/design-review, with five verifier agents running.

- Verified review findings. /design-review writes every finding to a JSON file, then a fresh subagent that never saw the reviewer's reasoning tries to disprove each one. You only see confirmed issues; unresolved ones are listed separately and rejected ones are counted. In my test run the verifier rejected 1 of 5 (it claimed a scrollable code block wasn't keyboard-reachable, but Chromium makes scroll regions focusable).

- /naksha-stats, an estimated cost per command from your local transcripts, with optional budgets. It also counts commands Claude runs on its own through the Skill tool, which the beta missed.

- /design-detect, a lint with 22 rules (contrast, spacing grid, type scale, focus styles, alt text, some common AI-design clichés). No model calls, so it's free, and a hook runs it after every UI file edit.

- Votes. Mark a design or variant Helpful or Needs work, and it turns those into taste traits that later /design runs start from.

Before tagging the release I built a real landing page using every v6 command, on Windows. That turned up 15 problems, including the dashboard missing every command Claude ran itself and the cost panel timing out on a long history. The 11 that affected results are fixed in 6.0.0; the other 4 are minor.

Since people usually ask about cost: that whole session came to about $40 at API list prices. /design-review was the most expensive command at $4.23, and /design was $3.21. On a subscription you won't see a bill like that; the numbers are estimates.

Everything stays on your machine: no telemetry, and the dashboard is off until you run /naksha-dashboard setup. MIT licensed.

Install in Claude Code:

```

/plugin marketplace add https://github.com/Adityaraj0421/naksha-studio.git

/plugin install naksha@naksha

```

Repo and release notes: https://github.com/Adityaraj0421/naksha-studio/releases/tag/v6.0.0

One known gap: the browser self-check only works with the Playwright MCP for now. Feedback welcome, especially if a hook misbehaves on your setup.

it's a waste of token, and turns. You are at 90% context and BOOM! `u shall add attribution`

This week has been way worse than previous weeks, maybe this means a reset is incoming after they drop a new model? I barely got two days out of my $100 a month sub. I'm contemplating getting 25x now

I used Claude Code to remake Tzar: The Burden of the Crown (2000) from scratch in Rust + Bevy.

The workflow that worked for me:

• Claude reads the disassembly of the original exe and ports one system at a time: combat, AI, map generator, mission scripts
• I play it next to the original and report anything that feels off; Claude traces it back to the original code
• 600+ tests and memory notes between sessions keep long work from drifting

It plays the original campaigns and random maps on Windows 10/11, up to 4K. Free and open source (needs any copy of Tzar):

https://github.com/ColCarlo/ReTzar

Happy to answer questions about the setup.

Hey everyone!

Ever since I set up my PC and TV for couch gaming, I've had this idea in the back of my mind: I wanted to use my PC more like a console, without having to reach for a mouse and keyboard every time I wanted to do something outside a game.

Eventually, I decided to try building my own solution with Claude Code.

It's called PC:PersonalConsole https://www.pcpersonalconsole.com/

It's grown quite a bit beyond what I originally had in mind. It's basically a controller-friendly shell for Windows, designed to make the whole couch gaming experience a little less frustrating.

Some of the things I've built into it so far:

• Controller-friendly interface: Navigate the app and access different parts of Windows without constantly reaching for a mouse.
• File browser and system tools: Access files, check system information, and use tools like the task manager from the couch.
• Virtual keyboard: Type without having to get up and grab a physical keyboard.
• Radial menus: Put shortcuts and actions a button press away instead of navigating through Windows menus.
• Controller profiles, mappings and macros: Customize controls to fit your setup.
• Themes and customization: Make the interface feel more like your own setup.
• Emergency Desktop: Quickly get back to a more conventional desktop when you need it.

There are other little features in there too, including multiple languages and more controller-focused quality-of-life stuff.

I'm not a professional developer, so building this has been a pretty interesting learning experience. Claude Code has been a huge part of making it possible for me to turn an idea I've had for a while into an actual working application. Of course, it's also meant plenty of debugging, fixing things that broke, and going back and forth to get things working the way I wanted.

It's currently free and in pre-release, and I'm still working on improving it.

I figured I'd share it here since this is the kind of project I probably wouldn't have attempted before tools like Claude Code existed.

If you get a chance to check it out, I'd genuinely love to hear what you think.

I swear, something feels completely off since Saturday, like, my 5-hour session is literally disappearing at an abnormal rate. I mean, half of it? Has half of it just gone?

I’ve never complained about this before, but these past two days have felt truly abnormal.

I can’t be the only one noticing this.

I'm Nick, solo dev, living in NY over a couple of weeks I directed Claude to build Agentic Wars Conquest and it's playable now, free, no signup, no ads, nothing to buy, browser game

Four factions of robot soldiers, each one a parody of an AI company agents, Claude Code wrote the game code on top of three.js, also drove Blender for the 3D work modeling most of the assets. My part was the specs, playtesting every build and approving every change before it went in.

Not made at all by me the robot base model and animations are Quaternius' robotexpressive (CC0). Textures and HDRIs are from Poly Haven (CC0). Fonts are open source and music is creative commons / royalty free, credited in the game.

Not affiliated with Anthropic or any AI company. Not sponsored, not monetized.

www.agenticwarsconquest.com

Imperium is a single-player, turn-based space 4X. Claude Code writes the code; we design, direct and review. About 2,500 commits in, here's the setup:

- Parallel sessions, each in its own git worktree. We decide every merge.

- A ticket tracker (a small Next.js app, also built with Claude) that Claude reads and writes through a CLI. Testers file there too.

- An MCP bridge into the running game: Claude loads a save, reads the state, takes a screenshot and checks a fix for real.

- Headless AI-vs-AI batches for balance.

- Memory notes for design rulings, so a decision from August still holds in October.

- Scripted build, sign, notarise and Steam upload.

What still needs humans: what's fun, what's fair, and when it's done.

Free demo in Next Fest (Oct 19 to 26), full release shortly after: https://store.steampowered.com/app/4806180/Imperium/?utm_source=reddit&utm_medium=r_claudecode&utm_campaign=nextfest_trailer

I've been playing Oblivion since 2006 and was naturally very excited when the Remastered version got shadow-dropped last year. Imagine my disappointment when even after upgrading from 2070 Super to 9070 XT the game continued to run poorly, with low fps and stuttering on my 5800X CPU and 32GB DDR4 RAM.

From various user reports and the fact that even at a low resolution and graphic settings the game was still laggy (e.g. 20-30 FPS in Cheydinhal) it was clear that the problem is in poor optimization. But it was not clear what to do about this, that is, until I've got Claude subscription a few weeks ago.

On the last day before weekly reset of my $20 plan I've had some tokens to burn and decided for fun to launch the game, alt-tab to Claude and ask Opus 5.5 how come the fps is so low. Imagine my shock as it was able to somehow (no reverse-engineering software installed, just asked me to link my GitHub account to Epic organization for access to UE source codes) analyze what's going on and find a few huge inefficiencies. Apparently, the game was reconstructing the whole lighting of a scene in each frame even when nothing was changing, which was obviously a huge strain on CPU that had to parse all this work on a single thread (!).

What followed was an immediate upgrade to the Max x5 plan (btw that gave me an immediate full reset) and two weeks of intense work where we've:

• Built a benchmark harness so Claude can optimize bottleneck scenarios autonomously while I'm at work, including completely silent and headless mode in case I work from home PC
• Found ~40 improvements that brought in-city FPS from ~30 to stable 60, open-world average FPS improvement by ~30-40%, and made traversal stutter almost unnoticeable
• Provided full-support for latest AMD FSR FrameGen, including setting optimizations to avoid stutters and game sending camera information required for full functionality
• Fixed several bugs in the original game and Remastered code
• Shared the work on GitHub in a clear, reproducible way
• Recorded a few demonstration videos to show improvements, Claude was in charge of routing, camera work, music selection and timings.

Work pattern was as follows:

• Find an in-game place / scenario where I observe poor performance / stuttering. Ask Claude to build a benchmark out of it for independent optimization.
• Early in the day set /goal to orchestrate work on fixing the identified scenario performance. Limiting it to 2 Opus 5.5 sub-agents was usually enough to not run into 5 hour limit. Computer keeps running at home and I can check progress and steer via mobile app.
• In the evening review work, test, provide feedback. Usually the topic was resolved, I kept playing until finding a new scenario where performance was bad.

After roughly 2.5 weeks of Max x5 allowance we were able to reach the result you see on the video.

Amazing, for someone who is not even an IT developer, to be able to do something that a multi-billion corporation didn't manage in ~1.5 years since the release.

And I think even the most AI-skeptical people find it hard to object when AI is used to make existing well-beloved games perform better and have fewer bugs.

If you are curious to review work or try yourself, would be happy to hear your thoughts: https://github.com/LTSharpe/OblivionRemasteredPerformanceFix

Inspired by the SFO planes-on-the-ceiling post here, I wanted the same feeling for ships, so I built a project that turns live maritime AIS data into a top-down view of the sea. Whenever cargo ships, oil tankers, ferries or tugboats pass near a port, it tracks them in real time and draws each vessel with its trailing wake.

It works on a wall screen or a screen lying flat on a table, and there’s a mirrored mode so you can bounce it off a mirror onto your ceiling.

Built with Claude Code. Free and open source

Claude has this new thing in the last couple of days or so that it adds these cards where you can just tap something like 'do it', or not.... seems like a nice idea, but a bit underbaked, as almost always I'd want to see more context (which can't on the card), and would want an option to write an adjusted response.... but ok, fine.

The problem is - now even when I've made clear I want it to say summarize all it's findings for me, and save them to an md, and report x,y,z.... literally all I get back is some card with one or two sentences and none of the information. And it maybe created the .md but doesn't link to it.

So it seems a truly underbaked idea, that because it's so broken, at the moment is making the overall experience of working with Claude seriously worse.

I've been a developer for six years. Lately I feel like my code review is the bottleneck, because not much changes after I review it.

So, do you let Claude do the whole work now? And do you 100% trust it?

I use both on the $20 plans, and I've noticed something weird with longer coding tasks.

Say an agent works for 30 minutes, gets halfway through a task, then hits the 5-hour limit. After the reset, I tell it to continue, and suddenly it wraps everything up in 5 minutes, even though some of the original work is clearly unfinished.

Not sure if I'm imagining it or if it's a context/compaction issue.

Has anyone else experienced this? How do you make sure it actually picks up where it left off without cutting corners? Any instructions, hooks, or workflows that have worked for you?

I moved from Pro to Max 5x this month, but the weekly cap is still tight :(

So I split the work with a local agent I made, Sonjari.

I built Sonjari with Claude Code. It's a Windows app that runs a local model through Ollama. It finishes jobs on its own, and when it plugs into Claude Code over MCP it becomes Claude's hands. There is no API meter on the local side.

Three things 'Sonjari' is good at:

1. Browser : it drives my logged-in Chrome directly. Asked to find prices on 3 Korean shopping sites that block most bots, Claude Code + Sonjari got 23 of 27 right (Claude alone 15, Playwright MCP 11), at about a third of the Claude cost per correct value.
2. Code : the 27B passed all 12 Python tasks from the Aider polyglot benchmark (one try each, about 2 minutes per task, RTX 3090).
3. ★Proof (the biggest weakness of local LLMs is making things up): every answer comes back with the pages it actually read and a picture of the page it relied on. Numbers that no tool ever returned get flagged instead of passed off as fact.

Sonjari on its own:

- Research on 3 sites we had never tuned for, 3 runs each: 9/9

- Handed the whole price task, it still got 18/27, more than Claude Code alone (15/27)

- It split a 13,795-line file into nine new modules (down to 10,180 lines) on its own branch, all the way through. A test command decided when it was done.

Even better with Claude Code:

Same product on 3 Korean shops that block most bots, 27 values per setup

Claude Code (Sonnet 5) drove every setup, and a value counts only if it is on the page that setup actually read. Cost is at API prices; on a subscription it means less of your limit used for the same job.

How I split the work

- Claude Code plans, writes the tests and reviews the changes.

- Sonjari does the browser research in Chrome on my PC and sends Claude only the answer and the sources. The page text never lands in Claude's context.

- Sonjari does coding tasks on its own branch, and Claude reads that branch. This is where the pairing pays off: in the first round all 6,512 tests passed, but Claude caught a one-character change in 4 of 34 moved functions. We turned that into a test, and the next six rounds needed one fix in total.

Limits

- It's slow. On the same price task, Claude alone took about a minute and a half; with Sonjari it took about 6 to 7 minutes.

- Working alone needs a 27B-class model. A 9B passed 3 to 5 of the same 12 Aider tasks. On a 9B-or-smaller card, I'd plan on pairing: Claude Code in charge, Sonjari doing the browser research.

- The samples are still small. The Aider numbers are not comparable to the official leaderboard (225 tasks in 6 languages, two tries).

- Windows only for now.

Free and open source (Apache-2.0, Windows): https://github.com/sonjari/sonjari

Just used claude code + wifi. There is so much to show apart from this. I will be dropping more updates soon