None of this existed in my OS, only the governance layer systems and procedures. On my drive to the gym, I remote-accessed my Mac with Codex and spun up a complete source-backed workout and nutrition planner. Then dropped in one PDF workout plan. Took 3 prompts with less than 2 sentences each. What will you build next? Round 2 is the UI/UX

Context: i currently working on building a Real estate comprehensive CRM, that runs 80% locallly on the realtor machine, for one user though. i need your input to look at the attached folder structure, i feel somethings are missing and some are not much needed. Also attached is a summary of the project od what it will look like for the user.

So I haven't had the chance to dig into the classroom yet so I'm not sure if this is covered anywhere.. but this is my set of general vibe coding rules that I have been working on to use across all projects. This way I have a single "source of truth" for best practices to include on all builds and try to keep things clean. So far it has been working pretty well (from an amateurs perspective haha) and looking forward to stress testing it more. Please take it and use it for yourself if you don't have anything similar yet. Also, I would really appreciate any feedback from the more experienced devs/engineers in the group. 🙏 Edit for clarity: this doc is something I have been applying to all vibe coding projects. Not all projects in general. Another edit for clarity: I am just getting through Jake‘s ICM paper now along with the classroom material. I was not aware that he also refers to the claude.md as a global file to be handed off to the highest level orchestrating agent. This global.md would be better named something more specific and placed around layer 3 of the workflow (someone please correct me if I’m wrong). Anyways, hope this clears up any confusion there may be. Decided to change the name to vibe-code-rules.md for clarity =)