Pinned
20h •
I'm dumb. Here's proof.
I was today years old when I realized I did not have some of the most important files that you need in the folder structure that Jake teaches. During today's video call with the VIP group, he went on a deep-dive rabbit trail about the ICM folder methodology that he teaches in his foundations course (free). As he was discussing it, I went to check what my root folder looked like and I did not have a Claude.md or context.md file!!! My productivity skyrocketed ever since I implemented his folder strategy over a month ago, but little did I know that I hadn't even implemented it correctly. 🤯 🤯 🤯 This goes to show that massive action beats over planning every time!
Pinned
Mar 15 •
Welcome to Clief Notes. Here's where to start.
1. Watch the intro video and introduce yourself in the intro post here 2. Start with The Foundation (free course). Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things, move to Implementation Playbooks (Level 2). When you're ready to build your own tools, Building Your Stack (Level 3). 5. Post your work. Ask questions. Help others when you can. What are you here to build?
Poll
4932 members have voted
Pinned
6d •
🏆 WEEKLY COMP #3: THE SPECIALIST 🏆
💰 $325 CASH PRIZE 💰 That's a full year of Premium. Win this and your membership pays for itself. 📋 THE CHALLENGE You just got hired again. Different client this time. Meet Sarah, a freelance copywriter who's drowning in context-switching. 📎 Download the full client brief attached to this post. Short version: She works with three types of clients (SaaS founders, ecommerce brands, local service businesses) and starts from scratch every project. She doesn't need another tool. She needs a system. Your job is to build her a folder-based AI specialist she can drop into any Claude project. The folder IS the deliverable. 🗂️ THIS WEEK YOU LEARN ICM Up until now, comps have been "build a thing." This week you utilize the methodology taught throughout the community. 🧠 Folders as architecture. That's it. That's the whole concept this week. Your specialist is a folder with five things: - 📄 identity.md (who they are) - 📐 rules.md (how they respond) - 💬 examples.md (what good looks like) - 📚 reference/ (source material) - 📖 README.md (how to use it) Drop the folder into a Claude project. Claude becomes the specialist. Reusable. Shareable. Portable. 🎯 PICK YOUR SPECIALIST Don't pick copywriting. That's Sarah's example. Pick something YOU would actually use. A few sparks to get you thinking: - A salary negotiation coach - A meal planner that knows your dietary restrictions - A code reviewer for your stack - A real estate market analyst for your city - A technical recruiter screener - A grant writer for nonprofits in your space The more specific, the better. "Marketing expert" is not a specialist. "B2B email expert for enterprise SaaS targeting CFOs" is. 💼 WHY THIS ONE LANDS ON YOUR RESUME Real talk. Winning a comp in a Skool community doesn't get you a job by itself. But shipping a working folder-based AI specialist with a clean README and a public repo? That's a portfolio piece.
Mar 15 •
🏁 Foundations 2.2 Check-In
You just saw what happens between one line of Python and the hardware. Vote below, then tell us in the comments: what is one thing you assumed about how code works that this video shifted?
Poll
586 members have voted
20h •
The Blueprint for a Global AI Finance Hub: My "North Star" Structure
Even before the meetings happen, preparation is everything. I’ve been brainstorming how to take the principles we learn here and scale them for a global corporation (14,000 employees, 72 countries). This is the "North Star" for my journey toward becoming an AI Finance Manager. It’s a technical skeleton that ensures security, scalability, and—most importantly—the K.I.S.S. (Keep It Simple Stupid) model for the end-user. The Infrastructure (The Engine Room) Using the folder structure we’ve mastered, I’ve mapped out how a global hub would actually look "under the hood":Plaintext/ ├── CLAUDE.md # The Master Router (Direct OData Logic) ├── /identity # ACCESS CONTROL GATE │ ├── global_admins.md # Full access (Admin level) │ ├── DK.md # Validated users for Denmark │ └── [70+ countries].md # Global validation files ├── /library # THE COMMAND CATALOG │ ├── /global # Standard tools (e.g., /extract_ledger) │ └── /local # Country-specific tools (e.g., /dk_vat_report) ├── /core-logic # THE ENGINE ROOM │ ├── date_parser.md # Translates "MMYY" into OData parameters │ └── odata_templates.md # Master OData entity mapping ├── /countries # LOCAL CONTEXT & AUDIT │ └── /DK │ ├── audit-log.md # Record: Date | User | Command | Status │ └── local_settings.md # Local Legal Entity IDs / Currencies ├── /technical # SYSTEM RELIABILITY │ ├── mcp_config.md # OData read-only parameters │ └── health_check.md # System status triggers └── /schemas # EXCEL TEMPLATES └── ledger_standard.xlsx # Raw data structure The User Journey: From Teams to "Done" I want a user (let’s call him Lars) to get what he needs in under 60 seconds without ever touching a complex ERP menu. 1. The Request: Lars types /dk_vat_report 0126 in Microsoft Teams. 2. The Gatekeeper: The system checks /identity/DK.md. Lars is validated. 3. The Health Check: The system pings the MCP (Model Context Protocol). Connection is green. 4. The Data Pull: The AI uses the date_parser to see that 0126 means January 2026. It reaches directly into D365 via OData. 5. Delivery: The AI maps the data into a clean Excel template and uploads it to the chat. 6. Audit: The system silently logs the action for compliance.
1-30 of 1,084
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
1
+860
2
+769
3
+657
4
+571
5
+420
Powered by