Hoping to get a few questions answered on skills/tools based on the resource materials and examples from the classroom. 1. Do you guys keep a "global skills" folder at the project level (ie. for skills used for multiple workspaces)? That way you don't have to maintain the same skill in multiple places? 2. In the workspace-blueprint example, it says "skills work best when they're wired into the CONTEXT.md files. I asked Claude how to "wire" (which I assume just means making it accessible via backslash) and Claude said it needs to exist in the .claude/ folder, but I don't see this in the example. 3. The example also states "you can wire up to 15 skills per workspace". I don't see this limitation in any documentation - is this just a suggestion? If so, why? If you invoke a skill by name or md, why would you want to limit the number of skills in a workspace - if the ICM works as intended, it should only load in the specified skills.

Made it to Level 2!! I'm working on some ideas and folder structures that I'd like to share. Are we allowed to share github repo's here? Not sure of the rules, couldn't see any posting guidelines.

An ex Anthropic researcher just leaked 10 prompts to help you optimize your prompting. ## Prompt 1: Context Brief (The Map Claude Actually Needs) Never jump straight into a question. Start with rich context: ``` You are helping me with [specific goal]. My background: [your role + company/project + constraints]. I've already tried [X and Y]. I'm stuck on [Z]. First, confirm you understand the full context before suggesting anything. ``` Internal tests showed this single change boosts output quality by 41%. Claude isn't psychic — give it the full map. ## Prompt 2: Force Visible Reasoning (Chain-of-Thought on Steroids) Don't ask for answers. Demand the process: ``` Before giving any final recommendation: - show your full step-by-step reasoning - explicitly list every assumption - flag uncertainties and confidence levels (low/medium/high) - only then deliver the polished answer. ``` This pulls out Claude's hidden reasoning layers. You don't just get an answer — you get an auditable thought process you can actually trust. ## AND MORE - see attached files. From @kyronis_talks on X

Claude design is fully released. It burns up tokens but it works very well, and allows you to automate the folder design process that I've been showing you all. My video will go on to how not to use it as I think there's still some limits to what it can be done, but it's the step in the right direction. Again, I've been telling you about building systems that will be amplified by updates, not replaced. This is a perfect example. I'm going to go ahead and make a nice long form video out about this. What do you want out of the YouTube video? Comment below what use cases you want me to explore in the long-form (and eventually course addition of course !) For those of you that have been studying this the past few months, how does it feel to be ahead for once!?

When you move from building a static knowledge base to running an active, agentic workflow, something interesting happens. Jake's method proves once again you don't need bloated apps and proprietary solutions to get results. In this approach, you don’t need a specialized app to manage your AI. The folder system itself becomes the agent architecture and the user interface. Here’s how it plays out in practice. The Filesystem Is the Orchestrator In advanced agentic workflows, you are not just storing notes. You are running multi-step production pipelines — turning a script into animation, video creation pipelines, or handling complex sequences. Jake’s ICM handles this with the basic operating system filesystem. Numbered folders manage stage sequencing. Folder hierarchy controls context scoping so the AI only sees exactly what it needs. The output of one folder flows naturally into the next as input. Because the folder structure already organizes the logic, routing, and execution, adding Obsidian creates a redundant interface layer on top of a system that is already complete. As Jake puts it, what is simpler than a folder. VS Code Gives You a Leaner Setup For directing these workflows, many move to Visual Studio Code paired with Claude Code. VS Code shows you the raw folder tree and gives direct terminal access without extra layers. Obsidian is built as a personal knowledge management tool with a visual, plugin-heavy interface. When your setup is busy running Python scripts, scheduled checks, and processing files, a lightweight developer environment fits the factory floor better than a note-taking app. Plain Text Keeps Everything Clean A key principle here is plain text as the interface. Any tool that can read a text file should be able to participate without proprietary formats or hidden databases. Obsidian can alter how your files work by adding its own metadata and formatting requirements. Staying purely in local folders keeps the entire workflow transparent, untouched, and fully portable.