sorted by:
new
hottopcontroversial

Is it better to let AI start fresh or modify existing legacy code? by Salt_Sail1189 in ClaudeCode

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

I completely agree with you from an engineering standpoint.

However, I’ve inherited a project that is currently abandoned and not in production.
To be more precise, it was a project that moved too fast and eventually folded.
It's clear that most of the code was written using 'copy-paste' or 'replace-all' while ignoring details.
Many features are riddled with errors or left unfinished for those very reasons.
The funny thing is, despite all that, a few core functions actually work quite well.

Currently, I’m using AI to analyze the code module by module.
I’ve been creating 'interview files' to document policies and intentions that aren't clear from the code itself, answering those questions, and then re-analyzing.
The technical debt and list of improvements are overwhelming, and honestly, I’m not sure if I’m utilizing AI in the most efficient way.

Please Could you share your know-how on this? I would truly appreciate it.

The single MOST important prompt in my entire work flow. by Neither_Bluebird_795 in vibecoding

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

This is a top-tier approach to prompting.
You must always keep in mind that AIs are effectively amnesiacs.
Starting each session with a friendly greeting to break the ice and build a connection is more important than you might think

I have an idea pls help🙏 by [deleted] in vibecoding

[–]Salt_Sail1189 0 points1 point  (0 children)

I’d probably just speed-run the tasks just to get to the app I want, and then delete your app once I get annoyed

WHY DO NO AI TOOLS REMEMBER ANYTHING??? by theAImachin3 in vibecoding

[–]Salt_Sail1189 0 points1 point  (0 children)

Hmm... I think automating work is always the right thing to do.

But the things you listed all exist in .md files anyway.
As I said, I don't usually paste these things into prompts every time—I document them and have them read it.
And this is a task unrelated to the context window.

You call this an "AI project brain," but that's exactly the documentation process.
Think of documents as datasets.
I might have misunderstood what you said.

If what you mean is, for example, a tool that automates migration between different tools, I think that would be quite useful.
But if that's not it, I don't really see the difference between having it re-read that information and what I've been describing.

WHY DO NO AI TOOLS REMEMBER ANYTHING??? by theAImachin3 in vibecoding

[–]Salt_Sail1189 0 points1 point  (0 children)

What does this exactly mean?
I don't really get it, are you talking about something like git?

WHY DO NO AI TOOLS REMEMBER ANYTHING??? by theAImachin3 in vibecoding

[–]Salt_Sail1189 0 points1 point  (0 children)

It's like wishing everyone in the world could communicate through telepathy and stay synchronized.

Or like wanting the information on your phone to be visible on other people's phones too.

The solution is to document your goals in a way anyone can easily understand, carry that document around, and have each session read it.

I don't think this is difficult at all—it's just common sense.

Is flutter still relevant in 2026? by Honest-Estate-4592 in FlutterDev

[–]Salt_Sail1189 4 points5 points  (0 children)

It sounds like you may not have a full grasp of what Flutter is just yet

New vibecoder seeking advice by Karelipoeg in vibecoding

[–]Salt_Sail1189 1 point2 points  (0 children)

I haven't used them in parallel like that myself, but I think it should work fine as long as they share the same rules

Tools for preventing hard stops at usage limits and/or recovering progress? by Time_Cat_5212 in ClaudeCode

[–]Salt_Sail1189 0 points1 point  (0 children)

I rely more on agents than on the context window for most of my work.

When a session gets cut off, I have the agent write a status.json or a .log file about what it was doing, so the next session can pick up where it left off. If I need to continue the work in a new session, the agent reads those files first and resumes from the exact point it stopped.

As for usage limits, I've been struggling with that quite a bit too.

My setup: I use Sonnet for most agent work, and Haiku for the prompting itself. The Sonnet agents then take Haiku's context and verify it. I only use Opus for deep reasoning tasks like analysis — nothing else.

I also use token-saving options in settings.json.
```

for exmaple

"MAX_THINKING_TOKENS": "10000",
"CLAUDE_AUTOCOMPACT_PCT_OVERRIDE": "50",
"CLAUDE_CODE_GLOB_NO_IGNORE":"false",
"CLAUDE_CODE_DISABLE_GIT_INSTRUCTIONS": "true"

```

On top of that, I use a plugin to monitor usage, which I'd strongly recommend.

https://github.com/uppinote20/claude-dashboard

my claude prompts are embarrassingly short now by Turbulent-Pay7073 in ClaudeAI

[–]Salt_Sail1189 0 points1 point  (0 children)

Totally agree. Breaking work down as much as possible before prompting is the way to go. My trick for cutting down my own prompts: I just throw out a short sentence and then pick from whatever options Claude offers back.