Hey Clief Notes fam! 👋 I'm Chris and I'm stoked to be here. 🙋 A little about me: So I'm a custom car builder in south Florida, I started using Ai to help me manage my business faster and give me a competitive edge. 🎯 My current goal: My goals are to learn how to file and sturture my projects to be more organized and reduced sloppy results. 💪 What I'm currently building/working on: I'm currently setting up an autonomous social media operating system, Projection Mapping shows, Ai phone agent, seo and llm seach agent, Google ads agent, investment agent. 🤔 My biggest struggle or question right now: Trying to figure out if I shouyld start over or ask how to restructure my current projects that I have built so far. And I work from several computers thro the day including my phone, so do i make repos for everything moving forward? Let's get it! 🚀

This is the website I created for them — pikolhaus.com. Small start, but officially my first real client project. More to come.

Tell us three things: 1. What you do (job, industry, student, career-changer, whatever) 2. What brought you to Clief Notes 3. One thing you're trying to figure out right now related to computing or AI I'll respond to every single one. And read each other's intros too because the person who's stuck on the same problem as you might already be in this thread. I'll go first I am Jake, I have been working in tech for 15 Years, building with Generative AI for 3 Years straight now! Excited to teach and learn! That's it. Simple, scannable, gives you data on who's joining and what they need, and keeps the feed clear for content that retains people past week one.

I created a CLAUDE.md file for my AI-Workspace, a project I've been building as part of my AI learning journey. It's a portable "Second Brain" that organizes what I'm learning, manages AI projects, and maintains reusable context across tools like Claude, ChatGPT, and Perplexity. CLAUDE.md Project Overview AI-Workspace is a Markdown-based knowledge and project management system. It stores learning materials, project documentation, and shared instructions so AI tools can understand my work without starting from scratch every session. Tech Stack - VS Code and Claude Code - Markdown and Obsidian - GitHub and GitHub Desktop Commands - Read the root CLAUDE.md and shared AI instructions. - Read the project's PROJECT.md and STATE.md before working on a project. - Follow relevant workflow documents and review checkpoints. - Use Git to review changes before committing. Conventions - Keep information in one authoritative location. - Use PROJECT.md, STATE.md, and DECISIONS.md for structured project management. - Keep instructions short and load only the context needed. - Separate source material from AI-generated interpretations. Avoid - Don't invent missing project information. - Don't duplicate instructions or create unnecessary files. - Don't make destructive changes without approval. - Don't commit or push changes without permission. One way I expect Claude to behave better: Instead of guessing how my projects are organized or requiring me to explain everything again, Claude can navigate to the right files, follow established workflows, and respect my approval boundaries. My biggest takeaway: The real value of CLAUDE.md isn't telling Claude everything. It's helping Claude find the right information when it needs it.

I built a front door to my ICMs because I was tired of hunting through chats to find my own work. One place to see what each project is for, when to use it, its recorded status, and the next step. The work stays in its existing project. Untested skills stay separate until I test them. For now, it’s navigation and instructions, not an autonomous launcher. The goal is less remembering where everything lives and more actually using it. Clear steps. Less blah blah blah. Just show and tell. 😊