How I Turn My AI Chat History into Claude Code Projects Memory

Stop starting from scratch every time you open Claude Code

When you switch from ChatGPT to Claude, the weird part isn’t the model.
It’s the reset.

You open a new chat, and everything you worked to build starts to disappear.

• The tone shifts.

• The format drifts.

• You end up re-explaining decisions you already made.

That’s not a prompt problem. It’s a memory problem.

Claude Code fixes this because you don’t “work inside a chat.”
You work inside a project, and the project loads your context from files every time.

This is the setup I wish I had from day one.

In this guide, you’ll get:

• 3 prompts to extract your existing chat history and turn it into reusable files

• A simple folder structure that keeps Claude Code consistent across every session

• A system you can set up in minutes and keep building on over time

No coding. You run the prompts in your current AI tool (ChatGPT, Gemini, etc), copy the outputs, and paste them into your Claude Code project.

Our series of guides on Claude, Claude Cowork and Claude Code keeps growing every week!

You can find all my Claude guides here. Consider becoming a paid subscriber if you like these guides 👇

The shift that matters: from chat to project

Most people use AI like this:

Open a chat → ask for something → correct the output → repeat tomorrow from scratch

That works fine for one-off tasks.

However, once you start producing the same kind of work on a regular basis (guides, decisions, documents, analysis), two things start breaking:

• Inconsistency (each day it answers differently)

• Repetition (you keep re-explaining who you are, what you want, and how you work)

Claude Code fixes this because it reads from files you set up, not just your latest message.

So the goal isn’t to move your prompts over. It’s to move your structure.

It’s to build a stable structure Claude Code can load automatically.

Here is the workflow :

Instead of relying on the chat to "remember," you make the project carry the memory.

The minimum structure that actually scales

This setup is enough to make the system work — and simple enough to actually maintain. As your project grows, it grows with you.

my-project/
├── CLAUDE.md
├── rules/
│ ├── quality.md
│ └── boundaries.md
└── context/
├── you.md
├── project.md
└── writing-voice.md

Why does it work?

• It's not about having a lot of files. Each file just has one clear job.

• CLAUDE.md acts as the project’s memory.

• One thing worth knowing: CLAUDE.md doesn't replace your system prompt. It just adds context on top — things that are always true about your project. That's what makes it so consistent.

Think of it this way:

• CLAUDE.md = the essentials that always apply

• rules/ = longer policies and checklists (quality, boundaries, style)

• context/ = project facts, how you work, your voice, your audience

• skills/ = repeatable procedures (only when there is truly repetition)

This keeps you from stuffing everything into one file until it becomes a mess you can't manage.

Prompts to extract your chat history and turn it into reusable files

The whole point is to pull out what you’ve already built across your history and turn it into project memory.

Here are three prompts, each focused on a different layer:

• Prompt 1: Extractor from a ChatGPT export

• Prompt 2: Project blueprint

• Prompt 3: Writing voice compiler (articles, emails, notes, and more)

The idea is simple: don’t try to do magic, do setup. You don’t need to run all three every time. Treat them like modules — use only what you need.

You run these prompts in your current AI chat tool.

What you get back are Markdown blocks you copy and paste into .md files in your Claude Code project.

Prompt 1: Extractor from a ChatGPT export