Turn Build & Brew Photos Into Social Posts

Use Claude Code and MCP to design on-brand social posts from event photos.

Introduction

30 Second Summary

You ran a Build & Brew event. People showed up, built cool things, and had a great time. Now you need proof of it online so the next event fills itself.

In this project, you will use Claude Code (an AI agent that lives in your terminal) to turn your event photos into a polished, on-brand social media post ready to share on Instagram or LinkedIn.

What You'll Build

You describe your night to Claude Code in plain English, watch it design a branded post on a live canvas, and drag a finished image straight to your phone to upload.

By the end of this project, you'll have:

A conversation-driven design workflow where you talk about your event and Claude Code drafts copy in your voice and builds the visual for you.
Two ways to produce a post: a live Paper canvas for the full interactive experience, or a universal HTML/Chrome fallback that works on any computer.
A finished exported image (1080x1350 for Instagram) or PDF (for LinkedIn) ready to upload and share.
Secret Mission: Build a full multi-slide carousel that tells the story of your Build & Brew night from doors to demos.

Do I need any experience for this project?

None at all. This guide walks you through installing every tool from scratch, including Git and Claude Code. Both macOS and Windows instructions are included at every step.

You will need a Claude Pro subscription ($20/month) to use Claude Code. You can cancel anytime after your event post is done.

Before We Start

Before We Start...

Before any installs or commands, let's lock in what you're about to build and why it matters.

Install Git and Claude Code

Install Git, Claude Code, and Paper

You need three tools before anything else in this project works. Git downloads the Build & Brew Kit from the internet to your machine. Claude Code reads that kit and designs your social post. Paper gives Claude Code a live design canvas to build on.

Without these three tools installed, nothing else in this project can run. In this step, you'll install all three from scratch and confirm they're ready to go.

In this step, get ready to:

Install and verify Git on your machine.
Sign up for Claude Pro and install Claude Code.
Authenticate Claude Code with your account.
Install Paper Desktop and connect it to Claude Code via MCP.

Open your terminal and install Git

Git is the tool that downloads code repositories from the internet to your own machine. You'll use it in the next step to grab the Build & Brew Kit.

Press Cmd+Space (macOS) or the Windows key (Windows) to open your search bar.
Type Terminal (macOS) or PowerShell (Windows) and press Enter to open it.
Check whether Git is already installed by running this command:

git --version

✔️ I see a version number (e.g., git version 2.x.x)

Git is already on your machine. You're good to move on to the next substep.

ⓧ I don't see a version number

No worries. On macOS, you might see a system dialog asking to install Command Line Tools. On Windows, you'll see an error that the command is not recognized. Follow your platform's instructions below.

macOS

Click Install on the dialog that appeared. This downloads Apple's Command Line Tools, which includes Git.
Wait for the installation to finish. This can take a few minutes.
Once complete, confirm Git is ready by running this command:

git --version

You should see output like git version 2.x.x printed in your terminal.

Windows

Install Git by running this command in PowerShell:

winget install --id Git.Git -e --source winget

Wait for the installer to finish. You'll see progress output in the terminal.
Close PowerShell completely.
Reopen PowerShell by pressing the Windows key, typing PowerShell, and pressing Enter.
Confirm Git is ready by running this command:

git --version

You should see output like git version 2.x.x printed in your terminal.

Linux

Install Git by running this command in your terminal:

sudo apt install git -y

Enter your password when prompted. You will not see characters as you type.
Wait for the installation to finish.
Confirm Git is ready by running this command:

git --version

You should see output like git version 2.x.x printed in your terminal.

Still not seeing a version number?

On macOS, if the Command Line Tools dialog didn't appear, try running xcode-select --install manually and then re-run git --version.
On Windows, make sure you closed and reopened PowerShell after the install. The new PATH only loads in a fresh session.

Why isn't git --version working after I installed it?

Sign up for Claude Pro and install Claude Code

Claude Code is an AI agent that runs in your terminal. It reads instruction files, writes code, and controls design tools. To use it, you need a Claude Pro subscription.

✔️ I already have Claude Code

Confirm Claude Code is ready by running this command:

claude --version

You should see a version number printed in your terminal. If you do, skip ahead to the validation checkpoint below.

Command not found?

If you see a "command not found" error, Claude Code may not be installed on this machine. Close and reopen your terminal, then try again. If it still fails, switch to the other tab and follow the full installation instructions.

Help me figure out if Claude Code is installed.

ⓧ I need to install Claude Code

Open your browser and go to claude.ai.
Click Sign up and create an account (or log in if you already have one).
Subscribe to the Pro plan ($20/month). Claude Code is included with Pro and Max plans.

Why do I need Claude Pro?

Claude Code runs AI models directly from your terminal. The Pro subscription gives you the usage allowance needed to power the design workflow in this project. You can cancel anytime if you only need it for one event.

Once your subscription is active, install Claude Code from your terminal by running the command for your platform below.

macOS

Install Claude Code by running this command:

curl -fsSL https://claude.ai/install.sh | bash

This command downloads and runs the Claude Code installer. You should see output confirming the installation completed.

Windows

Install Claude Code by running this command in PowerShell:

irm https://claude.ai/install.ps1 | iex

This command downloads and runs the Claude Code installer. You should see output confirming the installation completed.

Linux

Install Claude Code by running this command:

curl -fsSL https://claude.ai/install.sh | bash

This command downloads and runs the Claude Code installer. You should see output confirming the installation completed.

Seeing a permissions error?

On macOS, make sure you're running Terminal as your normal user (not root). If you see a write permission error, try closing and reopening Terminal.
On Windows, try running PowerShell as Administrator: right-click the PowerShell icon and select Run as administrator.

Help me fix my Claude Code installation error.

Claude Code needs to connect to your Claude account before it can process requests. The first time you launch it, a browser window opens for authentication.

Launch Claude Code by running this command:

claude

What happens when I run this?

A browser window opens automatically. You'll be asked to log in with the same Claude account you just subscribed with. After you approve, the terminal shows a Claude Code session where you can type prompts.

When the browser window opens, log in with your Claude account.
Once authenticated, you'll be dropped into a Claude Code session in your terminal.
Type /exit and press Enter to close the session for now.

Before you run the final check, what do you think you'll see when you ask Claude Code for its version number?

Confirm the install worked by running this command:

claude --version

You should see a version number printed back in your terminal. That confirms Claude Code is installed, authenticated, and ready.

Not seeing a version number?

If the browser window didn't open when you ran claude, check that you have a default browser set on your system.
If you see a "command not found" error for claude, close and reopen your terminal so the new PATH takes effect.

Help me get Claude Code working in my terminal.

Install Paper Desktop and connect MCP

Paper is a design tool built on real HTML and CSS. Because its canvas speaks the same language as the web, Claude Code can read and write to it directly. You'll use it as the live surface where Claude Code assembles your social post.

✔️ I already have Paper Desktop

Open Paper Desktop.
Click New File to create a blank canvas.

Creating a new file starts the MCP server in the background at http://127.0.0.1:29979/mcp. You do not need to configure anything else in Paper itself.

ⓧ I need to install Paper Desktop

Open your browser and go to paper.design/downloads.
Download Paper Desktop for your operating system (macOS or Windows).
Run the installer and open Paper Desktop when it finishes.
Create a free Paper account when prompted (email sign-up is fine).
Click New File to create a blank canvas.

Creating a new file starts the MCP server in the background at http://127.0.0.1:29979/mcp. You do not need to configure anything else in Paper itself.

claude mcp add paper --transport http http://127.0.0.1:29979/mcp --scope user

What does this command do?

claude mcp add paper registers a new MCP server called "paper" with Claude Code.
--transport http tells Claude Code to connect over HTTP (not stdio).
http://127.0.0.1:29979/mcp is the local address Paper's server is running on.
--scope user makes the connection available across all your Claude Code sessions, not just this project.

Using WSL on Windows?

WSL cannot reach localhost by default. Go to your WSL settings, find Networking, change networkingMode to mirrored, then restart WSL. This lets WSL access Paper's MCP server on localhost.

🙋‍♀️ Paper not connecting?

Make sure Paper Desktop is open with a file loaded. The MCP server only runs when a file is open.
If you see an error about the address already in use, close any other Paper instances and try again.
On Windows with WSL, confirm mirrored networking is enabled before running the add command.

Help me connect Paper MCP to Claude Code.

Your environment is ready. Git, Claude Code, and Paper are all installed and connected. Next up, you'll download the Build & Brew Kit and start a conversation with Claude Code about your event.

Clone the Kit and Start the Conversation

Your tools are ready. Now it's time to give Claude Code something to work with.

Claude Code needs two things before it can design your post: the AGENT.md file (the brain of the Build & Brew Kit) and your event photos. You'll clone the kit, drop your photos in, and start a conversation where Claude Code learns about your night.

In this step, get ready to:

Clone the Build & Brew Kit repository to your Desktop.
Add your event photos to the project folder.
Start Claude Code and begin the intake conversation.

Clone the Build & Brew Kit repo

The Build & Brew Kit lives in a Git repository on GitHub. Cloning it downloads the entire kit to your computer, including the AGENT.md file that tells Claude Code how to build your post.

Move to your Desktop by running this command:

cd ~/Desktop

Clone the repository and move into it by running these commands:

git clone https://github.com/nextworkengineering/build-brew-kit.git
cd build-brew-kit

Confirm the clone worked by running:

ls

✔️ I see AGENT.md and a templates folder

The clone worked. You now have the full Build & Brew Kit on your machine.

What just happened?

You downloaded a copy of the NextWork Build & Brew Kit to your Desktop. The most important file is AGENT.md. It contains all the brand rules, archetypes, and instructions that Claude Code follows when designing your post.

The templates/archetypes/ folder contains the HTML/CSS templates for each post style (A, D, F, G, etc.). Claude Code picks the right one based on your photos and story.

ⓧ I don't see those files

If git clone failed, make sure Git installed correctly in Step 1. Run git --version to check.

On Windows, if ~/Desktop does not work, try cd $HOME\Desktop instead, then re-run the git clone command.

If you see a "folder already exists" error, you may have cloned it previously. Run cd build-brew-kit and then ls to check if the files are already there.

Help me troubleshoot my git clone command.

Add your event photos

Claude Code uses your actual Build & Brew photos to design the post. You need to put them somewhere it can find them.

Create a photos folder inside your build-brew-kit folder by running:

mkdir photos

Open the build-brew-kit folder in Finder (macOS) or File Explorer (Windows).
Drag your Build & Brew event photos into the photos folder.

Confirm your photos are there by running:

ls photos

You should see either your individual photo file names (like IMG_1234.jpg) or a folder name (like B&B 07:22 photos) listed in the output. Both are fine.

iPhone photos in HEIC format

On macOS, Claude Code handles HEIC-to-JPG conversion automatically using the built-in sips command. No extra work needed.

On Windows, HEIC files need to be converted first. Rename them to .jpg if they open fine, or use a free online converter before dragging them in.

Hand AGENT.md to Claude Code and start the intake

Now you'll launch Claude Code inside the project folder and tell it to read AGENT.md. This kicks off the intake conversation where Claude Code learns about your event so it can write copy that sounds like you.

Launch Claude Code in the build-brew-kit folder by running:

claude

A Claude Code session starts in your terminal. You are now inside the Claude Code interface where you can type prompts.

Type this prompt and press Enter:

Read AGENT.md and follow it. My Build & Brew photos are in ./photos. Make me a single post for Instagram.

What does this prompt do?

This prompt does three things at once. It points Claude Code at the AGENT.md instructions. It tells Claude Code where your photos live. It sets the goal: a single Instagram post.

Claude Code reads the entire AGENT.md file, understands the brand system, and then begins the intake process described in that file.

Once you upload your images to "photos" in "build-brew-kit", open Paper, create a new file, and tell Claude Code the name of the file, Claude Code will respond with intake questions.

It asks about what happened at your event, who you are, what people built, whether you want a light or dark background, and what accent colour you prefer.
Answer each question naturally in your own words. There are no wrong answers. Describe your night honestly.

This is Gate 1 of the workflow. Once Claude Code has enough context about your event, it moves on to building.

Claude Code responds with a setup checklist. It confirms Paper Desktop is open, checks for a blank file, verifies Full Disk Access, and confirms your photos folder. Follow its instructions to confirm each item.

Now let's get to designing with paper.

You've got your kit cloned, your photos ready, and Claude Code has finished the intake conversation. It knows your event story, your colour preferences, and which photos to work with.
Now it's time to let Claude Code loose on your Paper canvas. In this step, you'll watch it build your post live, give feedback, and export the finished image.
Claude Code finished the intake and gathered all the details about your night. Now it has everything it needs: your photos, your story, and the brand rules from AGENT.md.
In this step, you'll tell Claude Code to start building. It designs your post live on the Paper canvas while you watch, then pauses for your feedback before you export the final image.

In this step, get ready to:

Watch Claude Code build your branded post live on the Paper canvas.
Give feedback and steer the design in real time.
Export a finished image file ready to upload to Instagram or LinkedIn.

Build the post on the Paper canvas

Paper is connected and Claude Code has all the context it needs. Time to tell it to start building.

Type this prompt inside Claude Code and press Enter:

Paper MCP is connected. Continue building my post.

What happens next?

Claude Code will now:

Pick a post archetype (A, D, F, etc.) based on your photos and the story you shared during intake.
Create an artboard on your Paper canvas with your photo and copy laid out.
Apply your chosen ground (light or dark) and accent colour.
Pause and ask you for feedback before finalising.

Switch to Paper Desktop and watch the canvas. You will see elements appearing as Claude Code places them.

This is Gate 2 of the workflow. Claude Code shows you the draft and waits for your reaction.

Look at the post on the Paper canvas. Decide if you want to change anything: swap a photo, tweak a headline, try a different accent colour.
Tell Claude Code your feedback in plain language (e.g. "swap the photo for IMG_0042" or "make the accent orange instead").
Once you are happy with the result, tell Claude Code you approve the post (e.g. "Looks great, let's export").

Keep feedback conversational

You do not need design terminology. Talk to Claude Code the way you would talk to a friend helping you make a flyer. "Can you make the text bigger?" or "Use the group photo instead" works perfectly.

Export your finished post

Your approved post is sitting on the Paper canvas. The final step is to get it off the canvas and into a file you can upload.

Tell Claude Code to export by typing a prompt like:

Export my post as a 1080x1350 PNG for Instagram.

What about LinkedIn?

If you are posting to LinkedIn instead, ask Claude Code to export as a PDF. The AGENT.md workflow handles both formats. You can always export both if you want to post on both platforms.

Claude Code uses Paper's export tool to save the file to your project folder. It will tell you the file path in the terminal output (e.g. ./output/post.png).

Confirm the exported file exists by running:

ls output/

You should see your exported file listed (something like post.png, post.jpg, or post.pdf depending on the format you chose).

No file in the output folder?

Check that you approved the post before asking Claude Code to export. It will not export a draft that has not passed Gate 2.
Look at Claude Code's terminal output for any error messages about the export path.
Try asking Claude Code: "Where did you save the exported file?" It will print the exact path.

help me find or re-export my finished post from Paper

Your post is done and saved to your project folder. You can AirDrop it to your phone, email it, or upload it straight to Instagram or LinkedIn from your computer. Next up, you will learn the universal fallback path that works on any computer, even without Paper.

Build Your Post on the Paper Canvas

In this step, get ready to:

Watch Claude Code build your branded post live on the Paper canvas.
Give feedback and steer the design in real time.
Export a finished image file ready to upload to Instagram or LinkedIn.

Build the post on the Paper canvas

Paper is connected and Claude Code has all the context it needs. Time to tell it to start building.

Type this prompt inside Claude Code and press Enter:

Paper MCP is connected. Continue building my post.

What happens next?

Claude Code will now:

Pick a post archetype (A, D, F, etc.) based on your photos and the story you shared during intake.
Create an artboard on your Paper canvas with your photo and copy laid out.
Apply your chosen ground (light or dark) and accent colour.
Pause and ask you for feedback before finalising.

Switch to Paper Desktop and watch the canvas. You will see elements appearing as Claude Code places them.

This is Gate 2 of the workflow. Claude Code shows you the draft and waits for your reaction.

Look at the post on the Paper canvas. Decide if you want to change anything: swap a photo, tweak a headline, try a different accent colour.
Tell Claude Code your feedback in plain language (e.g. "swap the photo for IMG_0042" or "make the accent orange instead").
Once you are happy with the result, tell Claude Code you approve the post (e.g. "Looks great, let's export").

Keep feedback conversational

You do not need design terminology. Talk to Claude Code the way you would talk to a friend helping you make a flyer. "Can you make the text bigger?" or "Use the group photo instead" works perfectly.

Export your finished post

Your approved post is sitting on the Paper canvas. The final step is to get it off the canvas and into a file you can upload.

Tell Claude Code to export by typing a prompt like:

Export my post as a 1080x1350 PNG for Instagram.

What about LinkedIn?

If you are posting to LinkedIn instead, ask Claude Code to export as a PDF. The AGENT.md workflow handles both formats. You can always export both if you want to post on both platforms.

Claude Code uses Paper's export tool to save the file to your project folder. It will tell you the file path in the terminal output (e.g. ./output/post.png).

Confirm the exported file exists by running:

ls output/

You should see your exported file listed (something like post.png, post.jpg, or post.pdf depending on the format you chose).

No file in the output folder?

Check that you approved the post before asking Claude Code to export. It will not export a draft that has not passed Gate 2.
Look at Claude Code's terminal output for any error messages about the export path.
Try asking Claude Code: "Where did you save the exported file?" It will print the exact path.

help me find or re-export my finished post from Paper

Build Without Paper (Universal HTML Path)

You have a finished post from Paper. That is great for machines where Paper Desktop runs.

Not every system supports Paper Desktop. Linux, Chromebooks, and older OS versions cannot run it. This step teaches you a universal fallback that works on any computer with Claude Code and a browser. After this, you are never blocked from posting about your event.

In this step, get ready to:

Tell Claude Code to build your post as an HTML file instead of a Paper canvas.
Preview the branded post in Chrome and export it as a PDF.
Transfer the PDF to your phone and get it ready to upload.

Tell Claude Code to build as HTML

The archetype templates in templates/archetypes/ are plain HTML and CSS files. Claude Code can customise them directly and output a styled HTML file, no Paper canvas required.

Switch back to your terminal. If Claude Code is still running from Step 3, type /exit to close the session.
Start a fresh Claude Code session by running:

claude

Type this prompt and press Enter:

Read AGENT.md and follow it. My Build & Brew photos are in ./photos. Make me a single post for Instagram. Paper is not available - build the post as an HTML file I can open in Chrome instead.

What does this prompt do?

This prompt tells Claude Code to skip the Paper MCP path entirely. Instead of building on a live canvas, it generates a standalone HTML file styled with the same brand system and archetype layout.

Claude Code still runs the same intake conversation (asking about your event, your name, your accent colour). The only difference is the output format.

Answer Claude Code's intake questions. It will ask what happened at your event, who you are, what people built, and your colour preferences.
Answer naturally in your own words.

Claude Code picks an archetype based on your photos and story, then generates a styled HTML file. Watch your terminal for the file path where it saves the result.

What should I see?

Claude Code will confirm it saved the file. Look for a message like "saved to ./output/post.html" or similar. The exact path appears in the terminal output.

🙋‍♀️ Claude Code stopped and asked about Paper?

If Claude Code says Paper MCP is not connected and stops, it may have missed the last part of your prompt. Tell it directly: "Paper is not available. Build the post as a local HTML file using the templates in templates/archetypes/ instead."

help me get Claude Code to build my post as HTML instead of using Paper

Preview in Chrome and save as PDF

Your branded post is now a local HTML file. Opening it in Chrome shows you the finished layout before you export.

Find the HTML file path that Claude Code printed in the terminal. It is typically ./output/post.html.
Open the file in Chrome by double-clicking it in your file manager, or by dragging the file onto an open Chrome window.

You should see your fully branded social post rendered in the browser. It uses your chosen archetype layout with your photo and event copy.

Seeing a blank page or broken layout?

Make sure you opened the file in Chrome specifically. Some other browsers may not render embedded styles correctly.

If images are missing, check that your photos/ folder is still inside build-brew-kit. The HTML file references photos using relative paths.

my HTML post is blank or broken in Chrome

With the post open in Chrome, press Cmd+P (macOS) or Ctrl+P (Windows) to open the Print dialog.
Click the Destination dropdown and select Save as PDF.
Click Save.
Choose a location you can find easily (your Desktop or the build-brew-kit/output/ folder).

Why PDF instead of a screenshot?

PDF preserves the exact layout and resolution at any zoom level. For Instagram, you can crop the PDF to 1080x1350 using Preview (macOS) or Photos (Windows). For LinkedIn, PDFs upload directly as swipeable documents.

You should now have a PDF file saved locally showing your branded post.

Transfer and post

Your post exists as a PDF on your computer. The last step is getting it to where you actually publish.

Send the PDF or a screenshot of it to your phone using AirDrop, email, or Google Drive.
Upload to Instagram or LinkedIn.
For your caption and tags, scroll back through your Claude Code terminal output. Claude Code drafted the caption text and suggested tags during the conversation.

Instagram dimensions

Instagram posts use 1080x1350 (4:5 ratio). If your PDF is a different aspect ratio, crop it in Preview (macOS) or Photos (Windows) before uploading.

Before you check the result, predict: what do you think you will see when you open the PDF on your phone?

Open the PDF on your phone. You should see your on-brand social post with your event photo, the NextWork brand styling, and the copy Claude Code wrote from your intake answers. That is a finished post, ready to share.

You now have two ways to produce a social post from any Build & Brew event. Paper gives you a live canvas for real-time steering. The HTML path works on any machine with a browser. Next up, the Secret Mission challenges you to build a full carousel that tells the story of your entire night.

Secret mission

Build a Full Carousel

A single post is proof you shipped. A carousel tells the full story of your night, from doors to demos, and gives you more surface area to tag attendees and fill your next event. Ready to level up?

Clean Up Your Resources

Decide whether to keep your resources running, pause them to come back later, or delete them entirely. The main ongoing cost from this project is the Claude Pro subscription at $20/month.

Cost warning

Your Claude Pro subscription costs $20/month and renews automatically. If you do not plan to use Claude Code again soon, consider pausing or cancelling to avoid charges.

Resources you used:

Claude Pro subscription ($20/month recurring charge).
Paper Desktop app (free tier, no charges).
Local files: the build-brew-kit folder on your Desktop and any exported images or PDFs.

Keep everything running

No action needed. Choose this if you plan to use Claude Code and Paper Desktop for your next Build & Brew event. The whole workflow takes about 10 minutes once you have done it once.

Leave Claude Code installed on your machine.
Leave Paper Desktop installed. Your free-tier account stays active.
Keep the build-brew-kit folder on your Desktop for quick access next time.
Your Claude Pro subscription continues at $20/month.

Pause - I'll come back to this later

Cancel your Claude Pro subscription between events and re-subscribe when you need Claude Code again. Your local tools stay installed so you can pick up faster next time.

Cancel your Claude Pro subscription by going to claude.ai/settings in your browser and selecting the cancellation option.
Leave Claude Code and Paper Desktop installed on your machine. They take minimal disk space.
Keep the build-brew-kit folder on your Desktop so your photos and exports are ready when you return.

Delete - I don't want to use this again

Remove all project resources and start fresh. Follow each step below for a complete cleanup.

Cancel your Claude Pro subscription at claude.ai/settings in your browser.
Remove the Claude Code binary and data from your machine.

macOS

Run these commands in Terminal to remove Claude Code:

rm -f ~/.local/bin/claude
rm -rf ~/.local/share/claude
rm -rf ~/.claude
rm ~/.claude.json

Delete the project folder:

rm -rf ~/Desktop/build-brew-kit

Remove Paper Desktop by dragging it from your Applications folder to the Trash.

Windows

Run these commands in PowerShell to remove Claude Code:

Remove-Item -Path "$env:USERPROFILE\.local\bin\claude.exe" -Force
Remove-Item -Path "$env:USERPROFILE\.local\share\claude" -Recurse -Force
Remove-Item -Path "$env:USERPROFILE\.claude" -Recurse -Force
Remove-Item -Path "$env:USERPROFILE\.claude.json" -Force

Delete the project folder:

Remove-Item -Path "$env:USERPROFILE\Desktop\build-brew-kit" -Recurse -Force

Remove Paper Desktop by opening Settings, selecting Apps, finding Paper, and clicking Uninstall.

Linux

Run these commands in your terminal to remove Claude Code:

rm -f ~/.local/bin/claude
rm -rf ~/.local/share/claude
rm -rf ~/.claude
rm ~/.claude.json

Delete the project folder:

rm -rf ~/Desktop/build-brew-kit

Paper Desktop does not support Linux. No additional cleanup is needed.

Remove project-specific config files if they exist in any folder where you ran Claude Code:

macOS

rm -rf .claude
rm -f .mcp.json

Windows

Remove-Item -Path ".claude" -Recurse -Force
Remove-Item -Path ".mcp.json" -Force

Linux

rm -rf .claude
rm -f .mcp.json

That's a Wrap!

Nice work! You just turned your Build & Brew event into a professional social post, ready to share and prove what you shipped.

Here's what you accomplished:

Installed Git and Claude Code from scratch, connected Paper Desktop via MCP, and drove an AI agent through a full brand-aware design workflow using AGENT.md.
Built an on-brand social post on a live Paper canvas and learned the universal HTML/Chrome fallback that works on any computer, so you are never blocked from posting about your event.
Exported a finished 1080x1350 image for Instagram and a PDF for LinkedIn, ready to upload and share with your community.
Secret Mission: You built a full multi-slide carousel telling the story of your Build & Brew night from doors to demos.

Ready to quiz yourself?