클로드 코드로 제품 업무 환경 구축하는 법

How to organize Claude Code for product work Download the starter workspace. Run the setup skill. Sort files by how fast they change. Turn repeated work into skills. File every correction once. Adam Faik Aug 10, 2026 3 Share My Claude Code workspace for my product job is a folder with almost no code in it. It holds a context folder with everything about the company: the product, the users, the competitors, how I like to work. One folder per project, with the tasks separated from the deliverables. A set of skills that each do one recurring piece of work: the status update, the PRD review, the interview synthesis. When I give feedback once, it lands in a file with a note on why, and I never give that feedback again. I didn’t design this system. I arrived at it, mostly by getting it wrong first. Getting it wrong taught me the lesson that runs this whole article. Past the basics, your results in Claude Code stop depending on how well you prompt and start depending on how well you file. A good prompt improves one session; a good file improves every session after it. The prompt-tuning advice you’ve already read stops helping at exactly the point where the filing starts to matter. So instead of describing my system, I packaged it. The starter workspace is public on GitHub: the folders, the context templates, and five PM skills, personalized by one setup interview. You don’t need to be technical to follow along; every step is spelled out, including installing the tools. And while my example is a product job, the same architecture fits any context-heavy work: a design lead’s research library, a data team’s metric definitions, a founder’s everything-folder. Here’s the route. The switch. I’ll show you what chat mode and Cowork can’t give you, and why the terminal is worth it for a product manager. The starter workspace. Download it, run one setup skill, and give it a real task: six steps, each shown on screen. The practices. Six moves that make the system compound, each one naming the exact thing to do and what you get back. The rhythm. Here’s what a normal workday looks like inside the system, from the first short prompt to the two-minute filing habit. The payoff is concrete. One sitting gets you running: install the tools, download the workspace, answer the setup interview, hand over a first real task. You stop re-explaining your company every session, and every correction you make becomes permanent. Every step is below. Time to open the filing cabinet. What chat mode can’t give you You probably run your product work through Claude’s chat today: a browser tab or the desktop app, maybe Cowork for the agentic tasks. It works, and that’s exactly the trap. Every conversation starts from zero. The strategy doc you uploaded last time is gone, the context you patiently explained lives in a thread you’ll never find again, and the output you liked is trapped inside a conversation instead of sitting in a file. Chat is a great place to think and a terrible place to accumulate. For occasional questions that’s fine. For daily product work, it means paying the same setup cost every single morning. Claude Code is the same Claude with a different home: a folder on your machine that it can read, navigate, and write to. Context lives in files that persist. Recurring work lives in skills that run on command. Outputs land as documents you keep, not messages you scroll for. In my daily use, everything I used to do in chat or Cowork runs better here, because nothing is ever explained twice. That’s an observation from my own work, not a law, but it’s held for months. The part that actually changed my job is the terminal underneath. Claude Code speaks to GitHub natively, no connector needed: it can pull a company repository and answer questions about it, and it can push your own work. Ask it to fetch the repo behind your product and explain what a feature flag actually does. Push your workspace to a private repository and a teammate can clone it and inherit your head start. For a product manager, that’s a direct line into the codebase and a way to share your whole system, both of which chat simply doesn’t have. What nobody hands you is the filing system that makes all this compound. Anthropic’s best-practices guide is written, in its own words, “for engineers using Claude Code across various codebases, languages, and environments,” and engineers get their structure free: the codebase is already organized context. The PM guides that exist, Sachin Rekhi’s being the best known, rightly tell you to “store all of your product data and documentation in local markdown files,” then move on. Organized how? Try it without an answer and you get what I had: forty loose files and a stale setup. The starter workspace is that answer, prebuilt. Let’s set it up. Start with the starter workspace The starter workspace is the structure I run my own product work on, cleaned into a template: the folders, the context files with guided placeholders, an example project, and five skills already installed. The whole thing is free and public: claude-code-pm-starter . Six steps take you from nothing to a first real task, and none of them assume a technical background. One prerequisites note before you start. You need a paid Claude plan for Claude Code. Everything else, including the two tools you’ll install, is free and covered in the steps. Step 1: Install VS Code Claude Code runs in a terminal, and a terminal alone is a bad home for a product manager: you can’t see your files. The fix is an IDE. An IDE is just an editor that shows your folder as a panel of files while you work; developers live in one all day, and you’ll borrow it for the file panel alone. Download VS Code , the free standard, and install it like any app. You won’t write code in it. You’ll watch your workspace organize itself in the left panel, which is exactly the visibility chat mode never gave you. Step 2: Download the workspace Open the repository page , click the green Code button, and choose Download ZIP . No git, no account needed. Unzip it and move the folder wherever you keep your work. This folder is about to become the place your product work lives , so pick somewhere you’ll find it again, like a work folder in your home directory. Step 3: Open it in VS Code, terminal on the right Open VS Code, choose File > Open Folder , and pick the unzipped folder. The left panel now shows the whole structure: context/ , projects/ , operations/ , the skills. Then open the terminal inside VS Code with Terminal > New Terminal , and here’s the small trick that changes how the whole thing feels: right-click the terminal panel’s header and choose Move Panel Right . Files on the left, agent on the right: it stops feeling like a command line and starts feeling like a colleague sitting next to your documents. If you don’t have Claude Code yet, install it now from the official guide ; it’s one command pasted into that terminal. Then type claude and press Enter. Claude Code starts inside the folder, reads the map file, and knows where everything lives from your first message. Step 4: Say hello, then learn four commands One distinction saves beginners a lot of confusion. The terminal wants exact commands; Claude wants normal language. Before you typed claude , you were talking to the terminal, where spelling and syntax matter. Now that Claude Code is running, you’re talking to Claude, exactly like in the chat app. So do the natural first thing: type hello and ask it what it can see in this folder. It will answer like a colleague who just read your files. A few slash commands are worth knowing on day one, typed directly into Claude Code: /model - shows which Claude model you’re running and lets you switch. /effort - sets how much thinking Claude puts into each answer; higher effort for hard work, lower for quick drafts. /mcp - lists your MCPs, the live connections into tools like Jira, Slack, or Confluence, and lets you manage them. /plugins - opens the pl