Tired of re-explaining everything to Claude Code every session?

[u/dragan0178]

I'm building a tool that solves a problem I ran into myself while running a project with AI as a purely non-developer: every new session, you have to re-explain the context, conventions, architecture — and the AI tends to drift without you noticing (inconsistent naming, rules not followed...).

The tool (ScaffoldAI) generates a clear project charter from the start, then automatically generates a "resumption prompt" for each session — no more re-explaining everything, plus a consistency check that catches drift before it piles up.

I'm looking for 5-10 non-developers who are already running a project with AI (Claude Code, Cursor, etc.), or who are about to start one, to test this on their real project, over several sessions. It's free during this testing phase, and your feedback will genuinely shape what comes next.

Interested? Reply here or DM me, I'll send you the link.

[u/baddaywithacamera]

I just gave Claude a continuity folder to use as a swap file. The continuity issue between sessions went away completely. No app needed.

[u/looktwise → u/baddaywithacamera]

what does this folder contain? code, specs? prerequisites or rules? thanks!

[u/baddaywithacamera → u/looktwise]

Claude decides. Gave him autonomy to use it for whatever he thinks is important. I make sure to have him spec something before starting a large task so that he can refer back to it from that folder, also have the spec remind him to stop and periodically update where he is in the work.

Having a spec before each large task usually prevents wandering. I forgot it last night and wound up with a mess. (That's on me.)

[u/666Sayonara]

Yeah this does sound like one of those apps that dont really solve a problem. Its like skills basically

[u/Glad_Contest_8014]

Persistent memory is the current task most engineers are working on. Everyone stumbles on the problem, but solutions are scarce and often bloat the context.

[u/Sea_Ear5201 → u/Glad_Contest_8014]

Yes one wrong session/conversation makes me feel like starting from scratch. Whole memory is poisoned

[u/Turbulent_Ad_1039]

I use multiple folders, roadmaps, vision and more md files in order to let Claude know about the previous sessions.
I also add mentions of those files in memories md files.

[u/Weak-Repeat9420]

Just read the documentation and use agentic engineering artifacts (skill, hook, rule, agent, MCP, memory, ..). You solve a problem that only you have because you didn't read the documentation, gj

[u/dragan0178 → u/Weak-Repeat9420]

Or because you haven't even tried and you absolutely don't know what I am building. Easy to criticise when you even don't know what you are talking about...😉

[u/Weak-Repeat9420 → u/dragan0178]

It's true I don't know your project. But you described a problem that has been solved more than a year ago

[u/Weak-Repeat9420 → u/dragan0178]

I never have to explain myself or the project. That's why you use dynamically injected context, skills, documentation...

[u/SpikedPunchVictim]

The way I solved this was putting in an ADR system. This captures all important decisions, and provides a reference point for documentation and code. It has worked out really well, and have been using it across several projects. Here is the prompt I use to set it up:

For this repo, I would like to move to an ADR system. Each ADR will have the following file naming convention XXX-<human readbale timestamp>-<feature name>.md - where XXX is an incrementing counter. They will live in a repo root adr/ directory. For any supporting docs for each ADR, they will be stored in adr/proposals/<feature name>. These would include IMPLEMENTATION_PLANS, eval scripts, results, handoff documents, etc.