A kit of 18 skills, one profile template, and the instructions I wish someone had handed me on day one.
Two lines inside Claude Code. That's the whole install.
/plugin marketplace add madeehahassan/plsbuild-os /plugin install plsbuild-os@plsbuild-os
Paste into any Claude Code session — desktop app or terminal. Installs all 18 skills; updates arrive when you re-sync.
View the source on GitHub →Unzip and open welcome.html — it walks you through connecting the folder and installing the 18 skills.
curl -fsSL https://plsbuildos.com/install-plsbuild.sh | bash
Or one Terminal command. Installs the skills and a profile template into ~/.claude/, backing up what's there first. About six seconds.
One zip for all three surfaces. Open welcome.html inside — it walks you through Claude chat and Cowork setup in three clicks.
"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.
Read the full essay on Substack →The shared layer, the project layer, and everything else that holds it together.
Six of them (/spec, /build, /voice, /design, /ship, /retro) are the ones you'll reach for most.
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.