User
Write something
Vibe Film Session is happening in 22 hours
Am I misunderstanding "build inside your workspace"?
Subject: Am I misunderstanding "build inside your workspace"? I'm working through "Building Your Stack" and stuck on something Jake says in lesson 1.1: "Build inside your workspace. Don't create a separate folder. Build where your context already lives." Right now, every time I start a new project, I create a new folder and ask Claude to use the ICM architecture to design it. But based on this lesson, it sounds like I might be doing something wrong. My current approach: - New project = new folder - Each folder gets its own CLAUDE.md and structure - I reference ICM architecture in the setup What I think Jake is saying (but not sure): - Build tools and projects inside an existing workspace that already has context - Don't spin up a new isolated folder every time Questions: 1. Is there a "main workspace" I should be building everything inside of? 2. Should custom tools live alongside my regular AI work files, not in separate repos? 3. Am I overthinking this, or am I actually setting things up wrong? Would appreciate any clarity from people who've gotten this working.
Am I misunderstanding "build inside your workspace"?
Pre-made Assets for Claude
Is there some kind of place or repository that Claude can draw upon to build things using premade assets? I want to really make use of Claude Design and Claude Code's website building capabilities but I have no idea what to work with or make. Ideally, I like to generate a kind of base and flesh out some ideas from there if you know what I mean.
Refresh time - Chatbox w/ my domain knowledge.
Hello all, I been away from ICM for a few months and want to dive in back but I notice a lot has changed here! Are the materials in the classroom still current or is there a diff process now? I am currently putting all my domain knowledge in an ICM repo that I hope to leverage into a chatbot at work so support and my other engineers can use it to get information on our BU instead of pinging me as my responsibilities at work just 2x itself. In context the idea is simple. Make folders and markdown files for each topic and in the claude file make sure to have the map pointed to those top level folders but wondering if others have done this for their job or personal life and have suggestions or potential issues?
New here: how do you hand off an AI workflow so it works without you?
Hey, I’m Eddy. Product and tool design engineer at an injection molding company in the Allgäu, Germany — automotive components, mostly CATIA V5. Right now I’m turning raw meeting recordings into a real company knowledge base before a colleague retires, and building a tool-agnostic AI workspace system around it. Two years of daily AI use. Clief’s videos pushed me from Cowork into Claude Code, and that opened a lot of doors. My question: how do I hand this off so it works without me?
do we need VS code?
just discovered (sorry if this is old news) you can browse the file tree in claude code, do we need VS code anymore?
1-30 of 328
Clief Notes
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
Powered by