Skip to content

How to write a case study from your Claude conversations (2026)

Sitting down to tell the story of your own work is one of the hardest things to do alone. If you made the project with Claude, you do not have to: the decisions, the dead ends and the breakthroughs are in the conversations already. This is how they become a page on your site.

By , designer and art director · Updated October 18, 2026

By starting, you confirm this is your site and your content.

The short answer

If you made the project with Claude, the case study is already in your conversations: the extract-from-claude-history skill in a Promtfolio folder pulls out the problem, the decisions and the before and after, asks you a short round of questions, and build-portfolio-page turns it into a page in your site's style. Then you upload the folder, and it is live.

Where the case study already is

When you build something with Claude, the case study writes itself as you go. The first message is usually the problem. "Let's try this instead" is a decision. "This does not work because" is a constraint you found live. The last state is the outcome. The extract-from-claude-history skill reads that history and pulls those moments out, so nothing is written from scratch.

What it can read:

  • The project's own folder: its notes for the AI tool, its README, its record of saved changes, and any memory files Claude kept while you worked.
  • Exported conversations: a Claude conversation saved as a file.
  • A conversation you paste in: treated as one source document.

It keeps only what a peer designer would learn from, replaces abstractions with specifics, and keeps your voice as it found it. A line it cannot back is marked, not filled in: a guess says what it rests on, and a blank says what it needs from you.

How to do it, step by step

1. Open your site's folder in Claude Code

The folder is the one you downloaded from Promtfolio with Take it with you. Its hidden .claude/skills folder holds seven Promtfolio skills, extract-from-claude-history and build-portfolio-page among them, and Claude Code loads the skills in the folder it starts in. Nothing to install, nothing to switch on.

2. Ask for the case study

In your own words, for example: "Turn last month's app redesign into a case study, from our Claude chats." Claude picks up extract-from-claude-history and follows it.

3. Answer one round of questions

  • The project's name, and a short name for its folder.
  • Where the history is: the project's folder, exported conversations, memory files, or a conversation you paste.
  • Roughly when the work happened, so the right part of the history is read.
  • Who the case study is for. This is read from a PORTFOLIO-BRIEF.md in your site's folder; if there is none, you are asked once and the answer is saved there.

4. Read the draft, in your words

You get a case-study.md to read in the chat: a headline that makes the claim, a line for the home page card, the facts (your role, the team, the timeline, the year, the tools), the outcome in one line, the one image to look at, an opening that ends in the question the project had to answer, and then the sections: the problem, the constraints, the approach, the turning points, the outcome with what the project proved, and what you carry forward, which is written only when you said it yourself. Each section carries a note of where it came from, which never reaches the page. You are asked three things: anything missing or wrong, anything to redact, and whether the voice feels right. Read the opening aloud; only you can answer that one.

5. Build the page

When the draft is yours, build-portfolio-page turns it into a page. On a site that came from Promtfolio it does not bring in a layout of its own: it takes your site's own strongest project page as the base, with its structure, its stylesheet and its fonts, writes the new page into a folder under projects, and adds the card to your home page in the site's own card markup. If a mark is still open in the draft, it stops and resolves it with you first. Then it starts a local preview and shows you the home page, the new page, and the new page at phone width.

6. Upload the folder

Say "publish". The publish-site skill walks you through it: the folder goes up by dragging it onto a page at Netlify Drop or Cloudflare Pages, the same way the site first went online. It shows you the site before anything goes up, and nothing is published on its own.

Made the project without Claude? The same folder has extract-case-study, which reads your existing portfolio page, a Figma file, notes, screenshots or what you tell it, and writes the same case-study.md. The steps from the draft on are the same.

With Codex instead of Claude Code

The folder is the same. Codex reads AGENTS.md before doing any work, and the AGENTS.md in the folder points it at the skills and says to follow them. The history it reads is the same too: your exported Claude conversations, the project's folder, or a conversation you paste.

In the studio

In the studio, whichever way you choose, Change with AI rewrites a project into a case study. With Go live with us the site is already live, so there is nothing to upload. With Take it with you, download the page and add it to your folder. The folder and its skills are yours whichever way you choose, whenever you download it.

Where the folder comes from

Paste your link and see your site rebuilt, free and with no signup: the whole home page with every project, and the inside page of three projects. The inside pages of the other projects open when the site is yours, for $39 once, plus tax where it applies, with no subscription. Once it's yours, change anything with AI. The skills travel inside the folder you download, and the Learning Center has every step from the ZIP to your own domain. To see what else the folder is set up for, read how to build a portfolio website with Claude Code or Codex.

Ready to move an Adobe Portfolio? See how Promtfolio brings every project with you →

Adobe, Adobe Portfolio, Creative Cloud and the other product names mentioned are trademarks of their respective owners. Promtfolio is not affiliated with or endorsed by them. Facts were checked on the date above, unless a different date stands next to them, and can change; confirm with each vendor.

Questions people ask

Can Claude write a case study from my Claude conversations?

Yes, when the site's folder carries the skill for it. The folder you download from Promtfolio has extract-from-claude-history in its .claude/skills, and Claude Code loads the skills in that folder on its own. Ask for a case study of a project you made with Claude, and it reads the conversations you point it to, pulls out the problem, the decisions, what was tried and dropped and the before and after, and writes a draft for you to read before any page is built.

What does Claude need from me to write the case study?

One round of questions: the project's name, where the history is, roughly when the work happened, and who the case study is for. The history can be the project's own folder with its notes and memory files, exported conversations, or a conversation you paste in. Who it is for is read from a PORTFOLIO-BRIEF.md in your site's folder; if there is none, you are asked once and the answer is saved there, so the next case study does not ask again.

Will the case study be in my words, or in AI words?

In yours. The skill keeps your voice as it found it in the conversations and quotes you directly where a quote says it best. It never invents a detail: a line it can back with a quote is marked as a guess, a blank is marked NEED INPUT with the question for you, and what you carry forward from the project is written only when you said it yourself. The page is not built until every mark is resolved with you.

Does the new case study page match the rest of my site?

Yes. On a site that came from Promtfolio, build-portfolio-page takes your site's own strongest project page as the base: its structure, its stylesheet and its fonts. The new page is written to projects, in a folder named after the project, and the card for it is added to your home page in the site's own card markup, so it looks like it was always there. Before it is done, it starts a local preview so you can look at the home page and the new page, on a phone width too.

Can I do this with Codex instead of Claude Code?

Yes, with the same folder. Codex reads AGENTS.md before doing any work, and the AGENTS.md in a folder from Promtfolio points it at the skills in .claude/skills and says to follow them, references and all. The history it reads is the same: your exported Claude conversations, the project's folder or a conversation you paste. What Claude Code picks up on its own, Codex is told where to find.

What if I made the project without Claude?

Then the material is somewhere else, and a second skill in the same folder reads it: extract-case-study works from your existing portfolio page, a Figma file, Notion or Google Docs notes, a folder of screenshots or mockups, or what you tell it. It writes the same case-study.md as the Claude history skill, and build-portfolio-page turns it into a page the same way. So nothing changes for the page, only where the story comes from.

How does the new case study go live?

You upload the folder, and nothing goes online before you say so. With Take it with you, say publish and Claude Code follows the publish-site skill: the folder goes up by dragging it onto a page at Netlify Drop or Cloudflare Pages, the same way the site first went online. In the studio, whichever way you choose, Change with AI rewrites a project into a case study, with credits, and with Go live with us the site is already live.

Where these facts come from

Read on and , each on the company’s own page. These pages change; if one says something else today, it is the one to trust.

By starting, you confirm this is your site and your content.