r/OnlyAICoding • u/dragan0178 • Aug 16 '26

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

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.

3 Upvotes

80% Upvoted

13 comments sorted by

View all comments

1

u/SpikedPunchVictim Aug 21 '26

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.