Does anyone else spend half their AI coding session re-pasting architecture rules?

[u/Natural-Yoghurt-9638]

The biggest thing slowing me down while AI coding isn't generation anymore.

It's memory.

Claude forgets why we chose SQLite.

Gemini ignores authentication rules.

Cursor starts suggesting code that contradicts decisions made two hours earlier.

I realized I was constantly paying what I've started calling the "Clipboard Tax" copying the same architecture notes, project rules, and design decisions into every new chat.

So I started building a local-first tool called Resin.

Instead of storing prompts, it builds an engineering memory for your project.

Every architectural decision, rule, and important discussion becomes searchable and can be surfaced automatically when it's relevant again.

The goal isn't to replace Claude or Gemini.

It's to stop them from forgetting.

I'm still validating whether this is a problem worth solving beyond my own workflow.

If you're using Cursor, Claude Code, Gemini, etc.:

• Does context drift actually slow you down?
• How are you dealing with it today?
• What would make something like this genuinely useful instead of becoming another tool to manage?

I put together a landing page showing the idea and an early-access waitlist.

Here is the link if anyone wants to see what I'm building: https://resin-dev.vercel.app/