carls-product-os

A Personal Operating System for Claude Code

Introduction

The biggest question I get after people finish my Claude Code for PMs or for Everyone 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]

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.
• Workflows provide process. They're instructions for Claude to follow.

A template says what the output looks like. A workflow says how to create it.

Knowledge vs Project Research

• Knowledge is persistent. It's reference material useful across many projects.
• Project research is scoped. It lives inside the project folder and gets archived with it.