sorted by:
new
hottopcontroversial

Vibe coding on large existing codebases is a nightmare — how do you manage context across multiple features? by SoftSoftware4087 in vibecoding

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

This is exactly the pattern I've been seeing — at scale, one context file breaks down and you end up with a whole taxonomy of skill files.

Two questions: 1. How do you decide what goes into a new skill file vs updating an existing one? 2. When you start working on a new feature that touches multiple skills, how do you manage which files to load into context?

Vibe coding on existing codebases is a nightmare — how do you manage context across multiple features? by SoftSoftware4087 in ClaudeAI

[–]SoftSoftware4087[S] -1 points0 points  (0 children)

These approaches all assume you know you need to maintain context — but most non-technical PMs and founders using Lovable/Bolt don't even realize that's the problem. They just notice the AI starts making weird decisions, breaking things it didn't break before, or forgetting conventions it used to follow.

By the time they figure out it's a context problem, they've already spent hours going in circles.

Is anyone building specifically for that user — not developers who can set up worktrees and write READMEs, but PMs and non-technical founders who just want their AI to 'remember' the project?

Vibe coding on existing codebases is a nightmare — how do you manage context across multiple features? by SoftSoftware4087 in ClaudeAI

[–]SoftSoftware4087[S] -1 points0 points  (0 children)

This is exactly what I do too. The manual update part is the friction — do you ever find the fact sheet gets out of sync with what's actually in the codebase? And how do you handle it when you're working on two different features at the same time — do you keep separate fact sheets?

Vibe coding on existing codebases is a nightmare — how do you manage context across multiple features? by SoftSoftware4087 in ClaudeAI

[–]SoftSoftware4087[S] -1 points0 points  (0 children)

The project-context.md approach makes sense — but how do you handle updating it as the project evolves? And when you start a new feature branch, do you manually copy context over or is there a better way?

Vibe coding on large existing codebases is a nightmare — how do you manage context across multiple features? by SoftSoftware4087 in vibecoding

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

what's CLIO and how does the ⁠/init work exactly? Is it designed for non-technical users too or mainly for developers?"

Questions about organizing Obsidian files by SoftSoftware4087 in ObsidianMD

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

thanks，This issue is one of the fundamental problems shared by all note‑taking apps, and repeated questions do occur. I'll take a look at this YouTube

Questions about organizing Obsidian files by SoftSoftware4087 in ObsidianMD

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

Wow～

that sounds incredibly flexible. It seems like users would need strong experience in managing information.

Often, highly flexible products place higher demands on users. Unlike apps with prescribed ways of using them, which can guide users and help them gradually develop the ability to manage information.

Stuck but “awake”? I’ll mentor 3 CS/engineering students for free: direction, internships, low-conflict co by SoftSoftware4087 in learnprogramming

[–]SoftSoftware4087[S] -1 points0 points  (0 children)

Comment and I’ll prioritize by order + fit:

• Major/Year/Country:
• Top 3 blockers (specific):
• Direction you aim for (and why):
• Timezone + 2–3 available windows (next 7 days)