A Claude setup for solo founders

Most people use Claude like a chatbot.
This turns it into a system.

15 skills, one install. The setup I wish someone had handed me when I started, compressed into six seconds of Terminal.

Pick your starting point

Not a developer? Start with Claude chat. Free, runs in your browser, no Terminal required.

Install on Claude chat.

What's actually inside.

The shared layer, the project layer, and everything else that holds it together.

THE 15 SKILLS

Twelve work instantly. Three need a little from you.

Most skills fire the second they're installed. Three have a small fill-in block at the top because they can't do their job without knowing something about you. Voice, design, and naming. Fill them in once, then forget them.

skills/voice/SKILL.md
All 15 skills
/voiceneeds you
/designneeds you
/namingneeds you
/audit
/research
/spec
/build
/support
/go-live
/retro
/growth
/agents
/pitch
/learning-log
/unblock
Fill this in once (voice)
my voice in 3 words:
I sound like:
I never want to sound like:
writing I actually like:
PROJECT-SPECIFIC CONTENT

Everything a product needs, in one folder.

Every product you build gets its own workspace. A brief Claude reads at session start, a living spec you update at session end, skills that only apply to this product, and specialized agents for reviews. Shared stays shared. Project stays project.

projects/your-product/
📁your-product
📄 product-brief.md what you're building, read at session start
📄 spec.md living state, updated after each session
📄 project-skill.md skills only this product uses
📁 agents/ specialized reviewers for this product
📄 design-agent.md
📄 user-agent.md
📄 CLAUDE.md the rules Claude reads first
AND EVERYTHING ELSE

Four more pieces that make it hang together.

Worked examples so you know what good looks like before you start. Seven reference templates for the work around the work. The next layer for when one product becomes three. And a skill map you can pin up while you're building.

4
Worked examples
Fully filled-in profile, brief, spec, and a sample project-specific skill for a fictional product called Peach.
7
Reference templates
Product vision, user interview, GTM, weekly review, launch checklist, build process, target user.
+1
The workflow layer
For when one product becomes three. External source of truth that Claude reads every session.
1
Skill map
Every skill, every trigger, one page. Pin it somewhere you'll see it while you're building.
The next layer

When you outgrow the foundation.

Without the workflow, the foundation handles most days just fine. When your spec starts feeling like a wall you re-read instead of write, the workflow is here.

Move your source of truth out of your repo. The board is where work lives — a page per product, every subpage a click away.
notion.so · plsBuild OS
🧰
plsBuild OS
A Claude setup that grows with you. plsbuildos.com
Product
📄 Product Vision
📄 What plsBuild OS is
📓 Notepad · feedback
Build
🏗️ Architecture
🎨 Design direction
📝 Voice & copy guide
Launch
🚀 GTM & launch plan
✅ Go-live checklist
🧰 Current state of affairs
3 products · 18 items
Ready 4
Write THE_WORKFLOW.md
P0
Add /board skill
P2
In Progress 2
Wire workflow layer
P0
Rename Claude.ai
P2
In Review 1
Homebrew install block
P1
Live 11
Build the 15 skills
Picker + install flow
+ 9 more
P0page
Wire workflow layer into landing page
StatusIn Progress → In Review
CategoryLanding Page
Last editedjust now
What changed
✓ Add ribbon under subhead
✓ Add "When you outgrow" section
✓ Ship THE_WORKFLOW.md
○ Update feature-grid link
Claude's update

Drafted three card moves:

  • Move this card → In Review
  • Create: Notion hub mockup
  • Close: Remove prompts → Live

The pattern lives in workflow/THE_WORKFLOW.md inside every flavor. Notion is the example. Linear, Jira, Productboard, GitHub Projects — any PM tool works.

Alright. Your turn.

Pick your flavor up there, paste one prompt, go build. Claude handles the rest.

↑ Back to the picker