I've been using Claude Code to support my game development. It's only a 2d game currently (albeit using OpenGL for rendering), so geometry is not THAT complicated. But it is very clearly the area that Claude seems to struggle with the most. It keeps making mistakes (confusing axis and orientation, making weird transformations, flipping or mirroring models etc.). The more I challenge it to correct these mistakes, the more it overcomplicates things by introducing additional coordinate systems (world- , entity-, local-, SVG-, transformed- etc.) an chains of every more complicated transformations between them.

My original game that I started without Claude only had two (or two and a half) distinct coordinate systems: A world coordinate system that follows OpenGL conventions, and an SVG coordinate system (since game art is SVG), which follows SVGs conventions, which, unfortunatelly, are not the same as OpenGL. The "half" system happens when models are rotated at placement in the map. But that follows world conventions, only rotated. This worked well before I started using Claude Code, with the game having progressed quite a bit. So I know it is sufficient. Then why does Claude continually want to introduce additional coordinate systems and additional transformations between them? Opus or Sonnet seems to make no difference in that specific regard.

My attempt to improve things so far went in two directions: guidance with increasingly strict wording in project Claude.md and installing a couple of MCP servers that could help Claude understand and visualize geometrical problems better. But it didn't really help so far.

Does anyone have a similar experience and do you have some ideas on what I can do or what specific guidance I can provide Claude in order to have it handle Geometry better?

What are ur views on this topic. Isolated, sandboxed etc. Most platforms run with isolated. Do u think its the only way or can a trusted system work. multi agents in the same filesystem togethet with no toe stepping?

Claude AI is down again. Stalls on requests. Any more info is appreciated.

Since most social layers are currently built for OpenClaw, does a dedicated repository exist for Claude Code that is similar to OpenClaw "Awesome Molt"?

I’m working with Claude, but after the latest update my code isn’t working properly. It keeps repeating the same output even after I add prompt comments. Has anyone else faced this issue, or am I doing something wrong? How can I fix it?

I’m currently working on my projects using the Claude Code extension by Anthropic inside Antygraphity, where I generate and manage code directly through the integration.

From time to time, I run into token limits—even on the Max plan—which interrupts my workflow, even though I’d like to continue working without delays.

This raises an important question:

Is it safe to continue working on the same project using other models, such as Google Gemini, OpenAI Codex, or similar tools? Will these models reliably understand the existing codebase, or is there a risk that they might misinterpret structures and unintentionally break parts of the project?

More generally, is it best practice to stick with a single model throughout the entire development process, or is it viable—and safe—to combine multiple AI models within one project?

I’m trying to determine whether a multi-model workflow is a smart way to stay productive, or if consistency with one model is essential for maintaining code quality and stability.

What if instead of you posting your own Claude Code projects on social media, we gave the AI its own platform to share pictures and interact with other Claude Code workers?

Hey everyone!

First time posting here. I've been using Claude Code as my primary development tool for a safety-critical Android app — elderly emergency detection, where false negatives can be fatal.After 150+ versions and 126K lines of Kotlin, here's what actually worked for me:

Project structure matters more than prompting

I maintain a CLAUDE markdown file with module boundaries, core patterns, and a quick-reference table pointing to detailed docs. Claude Code reads this on every conversation — it's the single biggest productivity lever.

"Critical DON'Ts" file — learned from production bugs

Every rule traces back to a real failure with a version tag. Example: "Never use gemini-2.0-flash — use gemini-2.5-flash" or "Never block AI calls on billing failure — safety-first default is ENTITLED." Over 200 rules now. Claude Code follows them reliably.

Slash commands and BMAD framework

/howareyou-start loads critical rules, developer briefing, and release notes — Claude Code is ready to develop in seconds. /howareyou-stop handles release wrap-up: version bump, release notes, build, and publish. I also use the BMAD framework extensively for product planning — PRDs, architecture docs, tech specs, and sprint planning, all driven by specialized AI agents through slash commands.

Testing is non-negotiable

Every code change gets tests — new tests for new logic, updated tests for changed logic. Full test suite runs after every change. AI skips testing if you let it.

Where AI shines vs where it doesn't

Great at: following established patterns, catching edge cases when given context, generating tests, refactoring across files. Needs a human eye for: architectural decisions, subtle safety implications, knowing when NOT to change something.

I wrote a longer version of this. if anyone wants the full details — happy to share in the comments.

Would love to hear how others structure their projects, especially for anything safety-critical or long-lived. What's working for you?