Welcome in

You just downloaded plsBuild OS.

Three clicks and Claude already knows who you are, how you work, and what you're building. Pick the Claude product you're installing on below.

Not sure which one? If you're a solo founder or vibe coder who writes copy and reviews designs more than you edit code, start with Claude Chat. If you want Claude to actually edit files and run commands inside your project, use Claude Code. Cowork is for the desktop app workflow with local folders. You can always install on more than one.

Two steps that matter. A third that's optional.

1

Paste your profile into Claude Settings

Open profile/my-profile.md in a text editor. Fill in the bracketed parts — your name, voice in three words, design taste, stack. Copy the whole file.

Then in Claude Chat, go to Settings → Profile, paste into "What personal preferences should Claude consider in responses?", and save.

Claude will now read your voice, taste, and stack at the start of every conversation.

Fill it in here instead · under a minute

Three questions, a few words each. Copy the result into Settings, or download as my-profile.md.

Not sure how specific to be? Open examples/my-profile-example.md — a fully filled-in profile for a fictional product called Peach.
2

Install the 18 skills

In Claude Chat, go to Customize → Skills. Click Upload skill and upload all 17 zip files from the skills/ folder. Toggle each one on.

The skills, grouped by the phase you're in:

🌱 Before you build
/spec
/research
/audit
/pitch
🔨 While you build
/build
/voice
/design
/unblock
🚀 Almost done
/ship
/go-live
📣 After it's live
/launch
/growth
/support
/retro
⚙️ The system itself
/learning-log
/pull-in
/learn-codebase
/agents
★ The core six. You'll reach for these every week: spec, build, voice, design, ship, retro. Learn these first. The rest you discover when the moment comes.

Two of them (/voice, /design) have a small fill-in block at the top of their SKILL.md file. Open each, fill in your answers once, and save.

Try one right now. Start a new chat and type: "Use the /voice skill to write three headlines for my product." If they sound like you, the setup is working.

3

Optional: create a Project for your first product

The skills work in any chat, but when you set up a dedicated Project for each product you build, Claude gets additional context automatically.

In Claude Chat → Projects → New Project, name it. Paste project/product-brief.md (filled in) into the Project Instructions. Upload project/spec-template.md as a file.

See examples/product-brief-example.md and examples/spec-example.md for fully filled-in references.

Three things. Cowork reads from local folders, so step 3 is slightly different from Chat.

1

Paste your profile into Cowork Settings

Open profile/my-profile.md, fill in the brackets, copy the whole file. In Cowork, go to Settings → Profile and paste it in. Save.

Claude will now read your voice, taste, and stack at the start of every session.

Fill it in here instead · under a minute

Three questions, a few words each. Copy the result into Settings, or download as my-profile.md.

See examples/my-profile-example.md for a fully filled-in reference.
2

Install the 18 skills

In Cowork, go to Customize → Skills. Upload each zip from the skills/ folder. Toggle each one on.

🌱 Before you build
/spec
/research
/audit
/pitch
🔨 While you build
/build
/voice
/design
/unblock
🚀 Almost done
/ship
/go-live
📣 After it's live
/launch
/growth
/support
/retro
⚙️ The system itself
/learning-log
/pull-in
/learn-codebase
/agents
★ The core six. You'll reach for these every week: spec, build, voice, design, ship, retro. Learn these first. The rest you discover when the moment comes.

Two of them (/voice, /design) have a fill-in block at the top. Open each, fill it in once, save.

3

Create a product workspace

Pick a permanent folder, for example ~/plsbuild-os/my-product/.

Copy project/product-brief.md into it and rename it to context.md. Cowork reads workspace context from that exact filename. Fill it in.

Also copy project/spec-template.md into the folder, rename to my-product-spec.md, fill it in as your living spec.

In Cowork, New workspace → point it at the folder. Cowork reads context.md and the spec automatically every session.

See examples/product-brief-example.md and examples/spec-example.md for references.

Four steps. Works in the desktop app or Terminal.

Before you start: Claude Code requires a Claude Pro account ($20/mo). If you're on the free tier, upgrade first at claude.ai/settings. Free accounts will get an error.
1

Fill in your profile

There's already a CLAUDE.md file in your plsBuild OS folder with a blank profile template. Answer the questions below, then either:

  • Click Download to get a filled-in CLAUDE.md and replace the existing one in the folder
  • Or click Copy and paste the profile into the existing CLAUDE.md file
Fill it in here · under a minute

A few words each.

Or open CLAUDE.md in any text editor and fill in the brackets yourself.

See examples/my-profile-example.md for a fully filled-in reference.
2

Connect this folder to Claude Code

Open Claude Code and connect it to the plsBuild OS folder. It will set up a .claude/ directory and read your profile automatically.

Already have a project folder connected? Stay in it. Skip to Step 3. You can merge anything useful from this bundle's CLAUDE.md into your existing one later.

3

Install the skills

Open the skills-for-claude-code/ folder in the plsBuild OS bundle. Select all 18 folders inside and copy them.

Then open the .claude/ folder inside whichever project you connected to Claude Code (the plsBuild OS folder, or your existing project). If there's a skills folder inside, paste them in. If not, create one called skills and paste them there.

One-time setup per project.

4

Try a skill

Tell Claude what you're working on and try a skill:

"I want to build [your idea, even if it's vague]. Use the /spec skill to help me figure out what exactly to build first."

Replace the brackets with your actual idea. Even "an app that helps people find good restaurants" is enough. The skill will help you sharpen it.

?

Prefer Terminal?

Skip Steps 1-3 above. Run this one command instead and it does everything:

curl -fsSL https://plsbuildos.com/install-plsbuild.sh | bash

Then open ~/.claude/CLAUDE.md and fill in your profile. Can't find it? Press Cmd + Shift + G in Finder, type ~/.claude and hit Enter.

What's in this folder?

The starred items are what you'll touch first. The rest is here when you need it.

welcome.html This file. The setup guide you're reading. Open it first, always.
profile/ Your voice, taste, and stack. Fill in my-profile.md once, paste it into Claude. Claude reads it at the start of every conversation.
skills/ The 18 skills. Each is a zipped SKILL.md that you upload to Claude's Customize → Skills. Once uploaded, Claude reaches for them automatically.
project/ Brief and spec templates. One set per product you're building. Fill in product-brief.md once per project. Update spec-template.md as you build.
examples/ Fully filled-in versions of everything — profile, brief, spec, learning log, project skill — for a fictional product called Peach. Look here when you're writing your own and wondering what "good" looks like.
templates/ Seven reference templates for the work around the work — product vision, user interview script, GTM plan, weekly review, launch checklist, build process, target user. Use them in your own notes, or paste into Claude when you want help with one specific piece.
workflow/ The next layer of plsBuild OS. Read the-workflow.md when you're juggling more than one product and the spec file stops being enough.
skill-map.html Every skill, every trigger, one page. Pin it somewhere you'll see it while you work.
license.txt Personal use only, not for resale.
The one rule

Keep the spec alive.

Setup is quick. The real value comes from a two-minute ritual at the end of every meaningful session.

When you've made a decision, shipped something, or changed your mind, ask Claude:

"Update the spec with what we did today."

Claude drafts the update from your conversation. You review, paste into the spec file (or your board, if you're using the workflow layer), done. Every session drifts forward instead of sideways.