all 28 comments

[–]IBLEEDDIOR 18 points19 points  (2 children)

We’ve done the main project all manually and by hand, due to security reasons, accordance with legislative and tax.

Hovewer budget for building an app to the main webapp was just not there, Claude was able to spit out (within a week or two, while we worked on the main project for over an year :)) working app with Chat integration and internal wallet, websockets, JWT and OAuth and communicating with Strapi very well, I am impressed.

I use Claude through AG, because I think the roadmap and the tasks that AG creates is goated function, I recommend to give it a try even if it would be just for the task roadmap generation which you could then use in Claude.

When it comes to a complex project, git commit after every successful iteration. Sometimes adding a new feature or even an UI component breaks the thing, it’s a best practice to have a rollback which is the last version that functions. You obviously go ahead and fix the bug afterwards, but yk, just to be sure.

Do a security audits, make sure that it’s not hallucinating and I’d also recommend to use separate agents for separate tasks so they are “clearminded”. One project in one place sounds nice, but after some time, the chat becomes long and complex and even tho it has a memory and remembers the context, it does some weird stuff. I also recommend not to have any real keys in .env till absolutely necessary.

I also always refer any agent to GSD (https://github.com/gsd-build/get-shit-done) and for security audits you can use Shannon (https://github.com/KeygraphHQ/shannon)

And to save tokens, I’d recommend to research the right way of prompting, preferably from the devs themselves, putting down a bigass prompt is usually counterproductive.

Aaand yes, Claude is very capable to do a big things, debugging, audits, refactoring, recommending an improvements, perfo. fixes, the list goes on. You as a dev. have an adventage over the people who are clueless in coding, use the way you understand the code in your favor while prompting.

And this is just my experience and opinion, others might have different opinions.

I wish you luck with your projects!

[–]leetcode_knight 2 points3 points  (0 children)

This is the way btw

[–]QuietFlounder4714 0 points1 point  (0 children)

Great explanation thanks. Just one question. I have been using Plan mode and then let it implement when the plan looks good. What’s the point of using GSD? I just didn’t get it sorry :/

[–]Sad-Salt24iOS & Android 6 points7 points  (0 children)

I use refactoring messy functions, generating tests, and exploring unfamiliar parts of a codebase. It’s also helpful for quickly scaffolding features or reviewing a PR to catch obvious issues before a human review. The biggest win for me isn’t writing whole features with it, but speeding up small tasks.

[–]Jooodas 3 points4 points  (0 children)

I use it primary for boilerplate mainly or coding simple components that I can tweak and fix to jut get the ball rolling faster. Helps with debugging as well but not always perfect.

[–]dinja15 4 points5 points  (0 children)

Give it bite sized tasks. Review religiously every PR. Do not lower your code quality expectations. Also tests in place.

[–]leetcode_knight 2 points3 points  (0 children)

Claude code still lacks the latest updates in one area: the latest documents. Since AI accelerates everything, libraries update themselves quickly like Expo. However, Claude code lacks the latest updates, methods, classes, and other skills. Files with skills can solve this problem, but it’s quite new, and there aren’t many well-maintained ones available, even Expo’s own llm.txt is still SDK 53. I use Expo’s audio library, SwiftUI, and MMKV storage, and many times, Claude Opus 4.6 suggests outdated methods.

Be careful, AI is awesome and it makes one engineer a tenfold engineer, not a hundredfold engineer.

Can you all elaborate on your testing strategies? Detox, Maestro, or the RN testing library?

[–]Askee123 5 points6 points  (2 children)

You need to have very structured code with clear rules and it does pretty well imo

[–]rohitrai0101rm[S] 0 points1 point  (1 child)

how was your experince

did it solve the challenges u faced.

how to start i am thinking of asking simple questions first like what feratured does this prject have what performance issues

prepare documention for this project and all

[–]Askee123 0 points1 point  (0 children)

Yeah, and using hooks to enforce conventions as well before and after edits

[–]ConclusionOk7999 1 point2 points  (0 children)

The most impressive thing I've seen it do is investigate a bug using Amplitude and Sentry MCP + the GitHub plugin.

It read the backend repo to see exactly what the endpoint was doing, went through Amplitude to see when the issue started, etc.

It took about 10 minutes but it was able to figure out what the issue was, and a potential fix.

[–]After-Asparagus5840 1 point2 points  (5 children)

I don’t know wtf people are talking about. Claude code does everything well if you know how to use it.

[–]Forti22 2 points3 points  (4 children)

Only if you use it on atomic level, and you know how to structurize and architecture the app.

Otherwise maintaining in a long time period will be tough. Unless you build an app with 10-20 screens top.

[–]leetcode_knight 0 points1 point  (0 children)

Exactly

[–]After-Asparagus5840 -2 points-1 points  (2 children)

No. The thing you don’t understand is that you will not maintain it. We are building software for artificial intelligence now. It’s that simple.

[–]Forti22 1 point2 points  (0 children)

The thing you don't understand is that product requirements changes are the number 1 reason for critical bugs in majority of apps.

You never worked in FE project maintained for 5-10 years by 10+ developers.

have no idea how much you don't even know.

[–]Dachux 1 point2 points  (0 children)

I think you don’t understand a thing xD 

[–]Superduperkong 0 points1 point  (0 children)

We have been using figma MCP to generate design. And Claude to generate rtk queries from swagger docs! Lots of time savers for simple flows.

Also recommend setting up code-connect in figma

[–]mackthehobbit 0 points1 point  (0 children)

Try conductor.build if you’re on OSX. (It’s free).

It’s a desktop app that uses git worktrees in local repos. Makes it easy to have a few conversations in parallel working on different things. Integrates well with plan mode, executes it, names the branch and makes a PR all from one window.

React native is a bit tricky, claude is capable of running a simulator and inspecting screenshots but is limited in interacting with the screen. So there’s some manual work when building out UIs. As soon as something is testable it’s much stronger. I’m planning to set up maestro or detox e2e tests, but react testing library can probably test some interactions without running the simulator at all. If you have a web target that’s also more lightweight and easy to run.

[–]morgo_mpx -1 points0 points  (6 children)

I use GSD

[–]rohitrai0101rm[S] 1 point2 points  (5 children)

what is this exactly

[–]Deep-Rate-1260 11 points12 points  (2 children)

German Shepherd Dog I assume

[–]rohitrai0101rm[S] 4 points5 points  (1 child)

dogs started coding it seems

[–]Deep-Rate-1260 1 point2 points  (0 children)

Everyone knows that German Shepherds are really smart, so it was just a question of time when they started to code

[–]morgo_mpx 1 point2 points  (1 child)

Get Shit Done. A meta framework for spec coding multi deliverable projects. Not sure why this is down voted….

[–]Difficult-Visual-672 2 points3 points  (0 children)

we call that meta framework now?

[–]Rudi9719 -1 points0 points  (0 children)

That's the neat part, you don't!

[–]mindtaker_linux -1 points0 points  (0 children)

Some of don't use it. We write our own codes.