Installs the Claude Code skills and profile template. Then open welcome.html for Claude Chat and Cowork setup.
Why I made this
"Every new session, I was re-explaining myself to Claude. The output was only as good as the setup."
After nine years in corporate roles, I forgot I could just make things alone. Claude brought that back — but only once I stopped using it like a chatbot and set it up like a system. plsBuild OS is the setup layer I built for myself.
The shared layer, the project layer, and everything else that holds it together.
THE 17 SKILLS
Something for every phase. Six you'll use every week.
Six of them (/spec, /build, /voice, /design, /ship, /retro) are the ones you'll reach for most.
skills/voice/SKILL.md
All 18 skills, grouped by phase
Before you build
/speccore
/research
/audit
/pitch
While you build
/buildcore
/voicecore · needs you
/designcore · needs you
/unblock
Almost done
/shipcore
/go-live
After it's live
/launch
/growth
/support
/retrocore
The system itself
/learning-log
/pull-in
/learn-codebase
/agents
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.mdwhat you're building, read at session start
📄spec.mdliving state, updated after each session
📄project-skill.mdskills only this product uses
📁agents/specialized reviewers for this product
📄design-agent.md
📄user-agent.md
📄CLAUDE.mdthe rules Claude reads first
Alright. Your turn.
Pick your flavor up there, paste one prompt, go build. Claude handles the rest.