Video 1: Installing Claude Code
The install, the login, and what the terminal looks like the first time. Watch this before your first hour; it is also linked in your purchase email.
Everything you need to stay independent: the videos, the skill guides, and the answers.
Focused on the known friction points, each under 10 minutes. Not a course.
The install, the login, and what the terminal looks like the first time. Watch this before your first hour; it is also linked in your purchase email.
A recorded walkthrough of the whole journey, from picking a source to a case study page running on your machine. For anyone who wants to see it before doing it.
The differentiator, recorded on a real example: pulling decisions, tradeoffs, and before-and-after states out of past AI conversations.
Shipping your site to Cloudflare Workers, including connecting a personal domain. Free hosting, your code, your name on the door.
Add a project, edit text, restore a version. The video that closes the dependency: after this one, you run the portfolio without us.
When to reach for each one. The loop is extract, build, deploy, and all of it is yours.
The guided first hour, and the right entry point for everyone. One calibration question, then a complete journey: pick a source, extract your first case study, see the page running locally. Use it once; it teaches you the loop the other skills repeat.
Use this when you are starting a portfolio site from zero. It scaffolds a clean structure with simple typography and a Cloudflare-ready setup. Skip it if you already have a site you want to keep building on.
Use this when a project of yours already lives in past Claude conversations. It pulls the real story out: decisions, tradeoffs, code snippets, before and after states. This is the skill that makes your AI process itself portfolio material.
Use this when your source is not Claude history: Figma files, Notion docs, screenshots, or a raw prompt. Same method, different input. It diagnoses what you have, drafts with marked guesses, and lets you correct.
Use this after extraction, when the case study material is ready. It turns the material into a polished HTML project page on a flexible template, running locally so you can review before anything goes public.
Use this when you are ready to publish. It ships the site to Cloudflare Workers via Wrangler: free hosting, your own domain if you want one, and the code stays yours. Deploy is always yours to time.
Use this when you already have a live site and want to know where it stands. You get a structured review with prioritized fixes, which doubles as a work plan for the other skills.
Built from the places people actually get stuck.
Three things: a computer, an active Claude subscription, and a clear half hour. That is the honest list, no surprises mid-hour.
Yes. The gentle lane was built exactly for you: every technical step is explained in one sentence before it runs, and there is a video for every known friction point.
This is setup, not the work, and it says nothing about how the rest will go. Watch Video 1 (Installing Claude Code), and if you are still stuck, ask in the community. Someone has hit your exact error before.
The chat is the terminal. You type to the agent in plain language, and it does the rest. There are no commands to memorize.
Ask yourself: which project would you show first in an interview? That one. You can always add the others later; the first case study is about learning the loop.
Your site holds less than you did. That is normal: published sites always lag the real work. The extraction process is built to surface what the site left out, from your conversations, files, and memory.
Completely. Marked guesses are the method working: the skill drafts from what it found and flags what it could not verify, so nothing invented ever ships. Resolve them in small groups of two or three, not as one giant list.
Check the obvious in order: are you in the right directory, is the file saved, is the browser pointed at the right path. The skill narrates each check with you, and Video 5 covers the maintenance basics.
No. Not being ready is legitimate. Build a second case study first if you like; the site runs locally for as long as you want. Deploy is yours to time, always.
Your site keeps working exactly as is: it is static code you own, on your own Cloudflare. Nothing breaks and nothing disappears. And if you still want to keep managing it the same way, in a conversation with an agent, without a Claude subscription: contact us individually and we will open the hosted studio for you (that alternative is reserved exactly for this case). The principle: full freedom, from us and from Claude alike.
Your site is plain HTML, CSS, and images in a folder you own, on hosting you own. It has zero dependency on Claude, on us, or on any AI at runtime. It will render in 2035 the way it renders today. Every Promtfolio site also ships with a built-in, old-fashioned content system: a plain content folder plus a simple local editor, so you can add a project, fix a typo, or swap an image by hand, no AI involved. Cancel the Claude subscription tomorrow and you keep working the way people built sites before the AI era. Nothing goes dark.
No. Promtfolio is a one-time purchase and Cloudflare hosting is free at portfolio scale. Your only ongoing cost is your own domain name if you choose to use one (usually about $10 a year). There is no subscription to us, so there is nothing to cancel.
You lose nothing. The plugin, the skills, and your site are files on your machine, MIT licensed. The learning center content is downloadable. We built the product this way on purpose: freedom from us was the whole point.
Independence is the product. By the end of the first hour you have done the loop once, extract, build, deploy, and every skill explains what it does as it works. Most people add their second case study alone. The community and the support agent are there when you want company, not because you are stuck.
Your design language lives in one file, BRAND.md, and the site is your code. Restyle it with Claude in an afternoon, hand it to a developer, or edit the CSS yourself. There is no theme lock-in and no template license, because there is no platform.
Your content stays on your machine and your hosting. The plugin talks to Claude the same way you do in any chat. The only thing that ever leaves for us is optional, anonymous friction events (which step was hard, never what you wrote), and only if you approve when asked at the end of the hour.
Still stuck?
The community is where designers compare sites, unstick each other, and share what worked. The support agent answers first, so you are never waiting on one person's inbox; a human steps in when it matters.