Carls Product OS — Development skill for Claude Code

Carl's Product OS

**A Personal Operating System for Claude Code**

Introduction

The biggest question I get after people finish my [Claude Code for PMs](https://ccforpms.com/) or [for Everyone](https://ccforeveryone.com/) courses: **"How should I set up my space?"**

Claude Code is infinitely flexible. There's no single right way to organize it, which is both liberating and paralyzing. This repo shows how I personally use Claude Code day-to-day, plus the principles behind each decision.

This setup is battle-tested across content creation, product work, and running a small business. But it's not gospel. Try things, break things, and see what actually works for your workflow.

Structure Overview

*[Screenshot placeholder - will add image]*

Folder/File	Purpose
CLAUDE.md	Entry point. Claude reads this automatically on every conversation.
GOALS.md	Your identity, what you own, and current goals.
Tasks/	Simple backlog → active → archive flow.
Projects/	Discrete work with its own context, research, and outputs.
Workflows/	Repeatable processes. Mini-workspaces you run again and again.
Meetings/	Notes organized by meeting type.
Knowledge/	Persistent reference material that spans projects.
Templates/	Document structures for consistent outputs.
.claude/skills/	Slash commands. Type /skillname to trigger.
Tools/	Scripts, utilities, and automations.
_Registry/	System reference and documentation.
_temp/	Drop zone for files in transit.

Key Concepts

Projects vs Workflows

• Projects are one-off. They have a clear end state. When done, they're archived.
• Workflows are repeatable. They're processes you run many times with different inputs.

*Example: "Launch newsletter" is a project. "Write weekly newsletter" is a workflow.*

Templates vs Workflows

• Templates provide structure. They're the skeleton of a document.
• **W