User
Write something
Afternoon Tea is happening in 5 days
Pinned
START HERE
Glad you made it in. Before you go anywhere else, work through the steps below. They will get you set up and ready to start. โœ… Introduce yourself in the comments. Tell us what you do and why you are here. โœ… Watch the Getting Started overview ๐Ÿ“šNavigating The Course - Getting Started ยท Clief Notes โœ… Start with the Foundation course 0.1: Where All Of This Leads - The Foundation ยท Clief Notes โœ… Fill out your profile so people know who you are โœ… Join the next competition โญ Competitions Mega Thread - Getting Started ยท Clief Notes โญ On Competitions (and why I love them) We host a competition every two weeks. These are some of the most powerful places to learn and build here. Also Cash prices (often over $200) for the winners. Learning how to do something is one part of it. The real learning starts when you put it to work. That is what the competitions and the build sessions are for. On top of this they act as a portfolio a place to not just show us but show others (clients, bosses, your best friend) what you have been building and that you really CAN build. In order to win a competition you must be a paying member (It takes me hours to review submissions sometimes days. But if you win ONCE you can pay for a whole year of membership so I think that's only fair!) Watch the videos, then go make something.
START HERE
Pinned
๐Ÿ† WEEKLY COMP #8: THE WILDCARD ๐Ÿ†
๐ŸŽŸ๏ธ PRIZE: FREE SEAT IN THE LYCEUM ๐ŸŽŸ๏ธ Pick your cohort. Technical, Business, or Creator. Your call. ---- ๐Ÿ“‹ THE CHALLENGE You are the client this week. No fictional Marcus. No fictional Sarah. No fictional Devon. Pick a real problem in your own life or work. Build the folder-based specialist you wish you had. This is the capstone of Month 2. The challenge flips. Instead of building for someone else, you write your own brief and solve it for yourself. ---- ๐ŸŽฏ THE TWIST The hard part isn't building. The hard part is scoping. Picking the right problem is harder than solving the wrong one. Most people pick problems that are too small or too vague. The skill this week is treating yourself like a real client. Be specific about what's broken. Be specific about what you need. Don't pick "I want to be more productive." Pick "I waste two hours every Sunday night writing the same kind of LinkedIn carousel posts and I need a folder that handles 80% of the draft work so I can focus on the hook and the visuals." That's a real brief. Specific problem. Specific scope. Specific desired output. ---- ๐Ÿ—‚๏ธ TWO DELIVERABLES THIS WEEK This is the only week with two pieces: 1๏ธโƒฃ Your own client brief. 250 words or less. Describe the problem you're solving for yourself. Treat yourself like a real client. What's broken? What have you already tried? What do you need? 2๏ธโƒฃ The folder system that solves it. Same structure as every week: - ๐Ÿ“„ identity.md - ๐Ÿ“ rules.md - ๐Ÿ’ฌ examples.md - ๐Ÿ“š reference/ - ๐Ÿ“– README.md Your brief lives at the top of the repo as brief.md so judges can read it before they look at the folder. ---- ๐Ÿ”ฅ THE ANGLE THIS WEEK Anyone can follow a brief. Writing your own, then solving it, then shipping it as a usable folder is a portfolio piece that demonstrates judgment, not just execution. This is the skill that separates "AI hobbyist" from "AI builder." Anyone can prompt their way through a problem someone else handed them. Scoping a problem, designing the solution, and shipping it as a system is what real work looks like. ๐Ÿ’ช
Pinned
Have not written a proper article in a while, I changed that today.
This will tell you a lot about the future and the way I think, give it a read if you have time. https://jakevanclief.substack.com/p/the-machine-is-smart
Business card + ICM + NFC
I've been trying to figure out how to show someone what ICM actually looks like in under 30 seconds. You know how it goes โ€” you start explaining numbered folders and stage contracts and human review surfaces, and their eyes glaze over around "stage contracts." So I built a demo that fits on a business card. Tap it to your phone, type what you do for work, and a live three-stage ICM pipeline runs in your browser. You watch each stage complete, read the output, pick what you want built, and walk away with a real workspace folder tailored to your work. All in about 20 seconds. ## The NFC Part I put an NFC chip on the card. That's it. Each chip stores a short random ID โ€” think license plate number. Tap the card, your phone reads the ID, sends it to a server, and the demo starts. I went with NFC over QR because tapping is just easier than framing with a camera. Also lets me tag each chip with context โ€” I can attach "SF Tech Conference โ€” dinner" on the backend and it shows up as a badge when someone taps. The URL carries nothing personal, just the random ID. The chip isn't the point though. It's just how someone triggers the demo. ## How the Pipeline Works Someone taps the card. Their browser opens to a text box: "What do you do for work?" They type something. Then three stages run, each feeding into the next: **Stage 1 โ€” Discovery.** AI looks at what they typed and writes a quick analysis of their work and what parts are repetitive. **Stage 2 โ€” Mapping.** AI designs a multi-step workflow for them. Each step has a note about what they'd want to review before moving forward. **Stage 3 โ€” Opportunities.** AI suggests four specific projects they could build with ICM. Each stage streams back in real time. You can read what the AI produced before the next stage starts. That's the ICM thing โ€” every output is visible and reviewable. Then they pick a project and the AI generates a real workspace. ## What They Walk Away With A folder of markdown files. Usually 5-7 of them. Numbered stages, instruction files per stage, a getting started guide. Download it, open it in Claude Code, type `setup`, and go.
Business card + ICM + NFC
Mind Bending - You Don't Want To Pass This By
I started by searching our community and didn't find anything. As I learned today, this GitHub repo has blown up 0 - 60K stars in less than 6 weeks. UNDERSTAND ANY CODEBASE IN MINUTES! https://github.com/Egonex-AI/Understand-Anything Graphs that teach > graphs that impress. Turn any code into an interactive knowledge graph you can explore, search, and ask questions about. Works with Claude Code, Codex, Cursor, Copilot, Gemini CLI, and more. --------------------------------------------------------------------------------------------------------- EXPLORE THE STRUCTURAL GRAPH Navigate your codebase as an interactive knowledge graph โ€” every file, function, and class is a node you can click, search, and explore. Select any node to see plain-English summaries, relationships, and guided tours. UNDERSTAND BUSINESS LOGIC Switch to the domain view and see how your code maps to real business processes โ€” domains, flows, and steps laid out as a horizontal graph. ANALYZE KNOWLEDGE BASES Point /understand-knowledge at a Karpathy-pattern LLM wiki and get a force-directed knowledge graph with community clustering. The deterministic parser extracts wikilinks and categories from index.md, then LLM agents discover implicit relationships, extract entities, and surface claims โ€” turning your wiki into a navigable graph of interconnected ideas. FEATURES ๐Ÿงญ Guided Tours Auto-generated walkthroughs of the architecture, ordered by dependency. Learn the codebase in the right order. ๐Ÿ“Š Diff Impact Analysis See which parts of the system your changes affect before you commit. Understand ripple effects across the codebase. ๐Ÿ—๏ธ Layer Visualization Automatic grouping by architectural layer โ€” API, Service, Data, UI, Utility โ€” with color-coded legend. ๐Ÿ” Fuzzy & Semantic Search Find anything by name or by meaning. Search "which parts handle auth?" and get relevant results across the graph.
Mind Bending - You Don't Want To Pass This By
1-30 of 1,980
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