Turn Your Claude Code Artifacts Into a Shareable Portfolio

Every session leaves an artifact — a dashboard, a deck, a little tool. Most of them die in a downloads folder. Here's how to give the good ones a shelf.

The artifact graveyard

If you build with Claude Code, you know the feeling. Every session ends with something real — a dashboard, a pitch deck, a little single-file tool that does exactly one useful thing. It's good work. And then it goes where good work goes to die: a downloads folder named like a license plate, never opened again.

You've probably made a dozen things worth showing. The problem isn't that they're bad. It's that they're scattered, local, and invisible. Nobody can see an HTML file sitting on your laptop.

An artifact deserves a URL

The first move is to stop letting them rot offline. Any artifact your agent generates can be live in seconds — drop it on host-html, or let the agent publish it for you with the host-html skill. If you've been turning markdown into HTML artifacts, the same thing applies: published, it's a page; unpublished, it's a file nobody will ever see.

So you publish the good ones. And now — predictably — you have a new problem. You have a pile of /p/ links and no way to show them as one body of work.

From a pile of URLs to a portfolio

This is exactly the pile that collections were built to solve — here's the general how-to. A collection groups your published pages behind one link at /c/your-name. For a builder, that link is your portfolio: the live, clickable proof that you make things, all in one place, in an order you chose.

What goes on the shelf

A portfolio is a curation, not an archive. The point isn't to show everything you've ever generated — it's to show the three or six pieces that make someone think I want this person to build for me.

• Curate, don't dump.: Pick the artifacts that still hold up. Leave the experiments out.
• Lead with your best.: The first card is the one people judge you by. Put your strongest piece first.
• Blurb each one.: A line of context turns a mystery link into a deliberate exhibit.
• Empty doesn't ship.: A collection with nothing in it won't publish — a portfolio of nothing helps no one. You have to choose what goes in, which is the whole point.

The builder's portfolio, step by step

1. Publish your best artifacts — each one gets its own /p/ link.

2. Open your account and make a collection. Title it like a portfolio: your name, your studio, your handle.

3. Add the pieces, order them, blurb them. Best first. One line each.

4. Publish and pin the link. Drop host-html.com/c/your-name in your bio, your README, your "hire me." See a finished example at /c/beautiful-html.

Keep it alive

One honest note, because a portfolio is the one thing you don't want going dark: free pages expire after a few days. That's fine for a quick share, wrong for a portfolio you're linking from your bio. If these pieces are how people find you, you want pages that never expire — Pro keeps the whole shelf standing, and collections come with every paid plan. Build it once, share the one link forever.

Give your best work a front door

You already made the things. They're just hiding. Pick your three best, give them a title, and turn a downloads folder into a portfolio.

Build your portfolio → · or read why we built collections.