Set up a side business in the right order — the do-first sequence (separate money, basic terms, simple records) vs. the feels-official-but-waits list (logos, LLCs-by-default, office chairs), with the structure question framed honestly and routed properly. Use when asked I'm starting a side business what do I need, do I need an LLC, set up my side hustle properly, or what comes first legally and financially. Produces the ordered setup sequence, the structure-decision framing (jurisdiction-flagged, professional-routed), the money-hygiene rules, and the employer-conflict check most people skip.
“I'm starting a side business what do I need.”“Do I need an LLC?”“Set up my side hustle properly.”“What comes first legally and financially?”
What to give it
▸The business, concretely — selling what, to whom, revenue so far or expected; liability texture matters (advice and physical products carry different risk than selling prints)
▸The employment situation — employed? The contract's IP-assignment and moonlighting clauses are the first read (using employer equipment or work hours for the side business is the classic self-inflicted disaster — asked directly)
▸Jurisdiction, loosely — registration, tax, and entity rules are deeply local; every such step gets typed and verify-locally flagged
▸What's been done already — revenue flowing? Then money-separation is behind schedule and jumps the queue
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓The employer-conflict check appears first, with the equipment/hours rule explicit
✓Money separation precedes any structure discussion
✓The structure trade is framed with this business's actual triggers, then routed
✓Every registration/tax step is typed and verify-locally flagged
✓The wait-list is labeled morale-not-milestones without moralizing
⚠️ What it refuses to do
Do not default to "form an LLC" — the reflex this skill exists to slow down; triggers first, professional second
Do not let revenue flow personally past this conversation — separation jumps every queue
Do not skip the employer check because it's awkward — the IP clause doesn't care about awkward
Do not assert entity/tax specifics for any jurisdiction — frame, flag, route
Do not shame the logo enthusiasm — sequence it; joy is allowed, it's just not step one
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y -p pm-claude-skills pm-claude-skills-mcp