Hi everyone! I am excited to show you what I managed to make with Claude now that i am learning how to use it. FOR A LITTLE CONTEXT: I'm a social media and content strategist, and I have a bad habit of saving ideas I never actually organize or develop. Too many notes apps, too many emails I send to myself but never opened or organized and too many notebooks I carry around with ideas that i probably won't go through. So I built something to fix that. What I built: One tap on my iPhone → I type the idea, format, and emotional outcome → email sends automatically. From there: - Make.com catches it, fetches my script library, and checks existing ideas - Claude writes 5 angles + a full production script + a priority score + flags related ideas - Everything lands in my Google Sheet, organized and ready for content writing day The workflow behind it: My writing day is Monday. From Tuesday to Sunday, I capture ideas as they come. By Monday, I have a full list waiting for me — each one already with a script, angles, and a priority score. No overthinking, no starting from scratch. Tools used - Make.com - Shortcuts app (iPhone) - Claude + Google Sheets + Google docs Why this works: - No Ideas get lost. I have a designated place to go Monday mornings, AKA Script day. - No formatting friction. - I am not starting from scratch, which leads momentum on writing days - and no more overthinking - The priority score helps me define what's worth working on first. - It keeps my content consistent: with the script library, tone and guidelines, that first draft doesn't feel like was made by ChatGPT from 2023😂 It is worth mentioning this is content for my account and I want to polish this to be able to set something like this for my clients content banks.

If we haven't met or read any of my posts here. Me: Computer user before PC's were available. Built my 1st one in 78 with a soldering pencil, think rotary phones. Now WebDev and Marketing consultant. Why your here. I develop full stack websites with PayloadCMS after switching from years of WordPress. What I'm sharing here is a PayloadCMS Project Development workspace template. To use it's as simple as cloning/forking a repo and including the folder in your local dev project. Once opened in your ide of choice, run setup. Key Benefits of This Approach - Consistency: Repeatable process ensures quality across projects - Clarity: Explicit stage contracts prevent misunderstandings - Efficiency: Reusable components and patterns reduce development time - Quality: Built-in validation checkpoints catch issues early - Knowledge Retention: Process captures organizational learning - Scalability: Approach works for both simple sites and complex applications 1st it asks some questions: I'll help you set up your PayloadCMS project development workspace. Please answer all of the following questions in a single message: 1. Project name: What is the name of your PayloadCMS project? (Default: my-payloadcms-site) 2. Website type: What type of website are you building? (Options: Blog, Business site, Portfolio, E-commerce, Documentation, Other) 3. MVP stage: Do you want to include MVP development as an optional precursor stage? (Default: yes) 4. Deployment target: Which deployment target do you plan to use? (Options: DigitalOcean, Vercel, Cloudflare, AWS, Other) 5. Database: What database will you use with PayloadCMS? (Options: PostgreSQL, MongoDB, SQLite, MySQL) 6. Vercel best practices: Do you want to bundle the vercel-react-best-practices skill for frontend optimization? (Default: yes) 7. SEO configuration: Do you want to include SEO configuration in your PayloadCMS setup? (Default: yes) 8. Search functionality: Do you want to include search functionality in your PayloadCMS setup? (Default: yes)

https://www.loom.com/share/a5437be6951c406586be39b5633c879c I spent most of today rebuilding how I organize my work, and I wanted to share it with you guys. The problem I was solving: I've been building production systems with Claude Code for over a year now. My process has always been the same -- use Claude Chat as the architect to brainstorm, build blueprints, figure out the technical approach, then hand those blueprints to Claude Code to execute. That part works great. But my project folders were getting messy. Context was scattered. Every new project started from scratch with no structure. And the stuff I learned on one build wasn't connected to the next one in any useful way. After going through Jake's material on workspace organization and the three-layer system, the light came on. What I built: A single folder structure on my desktop that does three things at once: 1. Obsidian reads it as a knowledge vault -- clients, pipeline, patterns, daily logs, reference materials. The stuff that compounds over time. 2. Claude Code reads it as a structured workspace -- each project has its own CLAUDE.md, its own planning folder with blueprints, its own source code directory. Claude Code knows exactly where to go and what the conventions are. 3. It's the onboarding manual for anyone I bring into the business. My daughter is ramping up to help with prospecting. She reads the client CONTEXT files and the pipeline folder. She doesn't need me to explain everything verbally. The flow: - I architect in Claude Chat (inside a Claude Project with all the client context loaded). The output is a requirements doc and a technical blueprint. - I duplicate my project template into the builds/ folder, rename it, fill in the CLAUDE.md, and drop the blueprint into planning/. - I open Claude Code in that project directory. It reads the CLAUDE.md, reads the blueprint, and starts building into src/. - As I code and add features, I come back to Claude Chat to architect new blueprints, and Claude Code updates CLAUDE.md along the way. It's a living document. - After delivery, I update the client folder, write a retrospective, and extract any reusable pattern back into my patterns library. Next project that needs a similar approach? The blueprint references the pattern instead of re-architecting from scratch.

Most of what I share here and on Instagram is practical. Folder systems, workflows, how to build things that work. That's the mission of the Skool side of Clief Notes and it always will be. But I also write about the bigger picture. Where AI is actually heading, what it means for governance, for knowledge, for who gets to say what counts as credible. I've been working on a treatise called Rise of the Virtual Vanguard for the last three years and I'm serializing it on my Substack alongside essays on consciousness, academic gatekeeping, computational orchestration, and the economics of expertise. This is the opinionated stuff. The long-form thinking that sits underneath everything I teach here. If that interests you, the first installment is live. https://jakevanclief.substack.com/p/before-the-singularity No paywall on this of course. Read it, disagree with it, tell me where I'm wrong. The best ideas get sharper in conversation.

I'm about to start recording videos about my software development workflow. I keep telling people about it but i realized after a meeting today about setting up a local vibe coding competition that i should just pump out a program or two on a live stream and then figure out how to edit it down into actual educational videos(I am NOT a teacher). The question i have is would anyone be interested in knowing about when I'm going to be on so they can sit in on the process? This is not going to be an ongoing thing. Just making a few videos to show how I do things.