Title: My First Structured Prompt: Making Complex Financial informations Easy to read digest I just applied the five-part prompt framework to a real project: creating a financial dashboard for a condominium general meeting. My original prompt was simple: "Can you create a clear dashboard for a condominium general meeting so that property owners can easily understand the different expense categories and make financial discussions more efficient? What would be the most appropriate tool to build it?" The intention was clear, but I hadn't defined the audience, functionality, constraints, or expected deliverables. Here's how I restructured it using the five-part framework. 1. Identity / Act as a financial data visualization specialist and UX/UI designer with experience in condominium management, financial reporting, and making complex financial information accessible to non-experts. Your approach should combine financial accuracy, visual clarity, and intuitive information design. 2. Task / Design a clear, interactive financial dashboard for a condominium general meeting. The dashboard must help property owners understand how their money is spent, identify major expenses, compare budgets against actual spending, and make informed decisions during the meeting. Evaluate and recommend the most appropriate tool or technology to build and present this dashboard. 3. Context / The audience consists of condominium property owners with different levels of financial literacy. Most not accounting experts. During meetings, financial discussions become lengthy and traditional financial statements are difficult to interpret. The dashboard should transform accounting tables into accessible visual information. The source data will come from accounting spreadsheets, annual budgets, expense reports, and financial statements provided by the property management company. 4. Constraints - Prioritize simplicity and clarity over visual complexity. - Use a clean, minimalist design inspired by Swiss editorial and information design. - Avoid unnecessary animations, decorative graphics, or excessive colors. - Clearly distinguish approved budgets, actual expenses, and financial variances. - Ensure financial calculations remain accurate and traceable to their source data. - Avoid technical jargon and explain financial terms when necessary. - Prefer affordable, maintainable solutions that do not require advanced technical knowledge. - Do not invent missing financial data. - Protect confidential financial information.

Franck here, sharing my AI journey. I'm currently using AI for automation for Pre-Prodution (Paper work for prepping a filmmaking project, contract etc...) and post production (video editing), and right now I'm at the exploration, building and fixing stage. One thing that caught my attention is how it is easy when you have the information in the right folder, it allows for more predictable actions and already see what might create friction in a project. For exemple there is no minim wage specific to my industry. So i pulled out all the minimum wage in my industry from different market put in a folder, then based on my economic reality i specify what my company do and where is it located and under Claude code told it to always refer to the general minium wage and the data base i fed it to make a proposal for each lead on filmmaking project. I'm eager to understand better and to learn how to make it the full system i need so the company grows. As a solo-preneur at this point it is life saving and allows for less complexity in running the day to day activity.

Title: MVP as a working ICM Test I created my first file folder system for OWANGA OS. My CLAUDE.md included my role in the company and how i plan to organise it so i stop doing 5 jobs as one.. My CONTEXT.md explained the system behind the production system and the first 3 most important task redundant enough to be automated, such as quoting, budgeting and contracts. My REFERENCES.md provided different union documents from different countries since in my country we don't have yet and we can't call it an industry, so it's a mix of international best practices and exemples of past projets i did locally to have claud help build a unifed understandable local standard. When I asked Claude about how organized my system is, the response was different because everything was clear and concentrated with clear instruction supporting a specific goal. Before that it was scattered informations with vague memory but with an output of everything possible but without specific context based of my market. Before, I had to explain everything specific to each proejct and making nuances here and there because it would recall other markets way of working and suggestions based on it. Now Claude already has the right information. Key takeaway: The minute you wrap your head on how to adapt it to your need it becomes crystal clear and it evolves as you implement few changes based on projects so it learns to get better at optimisation of the said system.

Title: when the simple waterfall folder ask rigor. I just watched the Jake Van Cleef breakdown, and the biggest thing that stood out to me was how do i make it mine within the film industry. When starting a project the voice and tone can be part of something you cant recall each time. But as you develop different stories you have to feed it a new voice. Interesting enough each project ask for a specific way to produce it. It clicked because it forced me to build a system i can replicate not based on the stories i develop but on the environment i'll have to produce them in. Building a system based on shielding the project on things out of my control. Like a sketchy power grid made me saved and organized a lot of documentation locally to reduce the need for online search. My main takeaway was as simple as it is, it is by far the most complex system i have to make work as i see all the benefits on the long game. The experiment at the end helped me understand the strengh (and my weaknesses) of a simple way to make the time early so i can save it later. Going forward, I'm going to iterate again and again as i'm not there yet. I just build stand alone promotional offline accessible mini site to promote movies and documentaries. Still some of the content didn't work i have to see how i can build a better system to make it work

Hey fam, Franck Onouviet here, A little about me: I'm a cinematographer and founder of an indi production company in Gabon. My current goal: Is to build my company system and let what possible run by itslef as there is many different things that are repetitive. What I'm currently building/working on: Trying to understand better ICM and figure out the following: Being in a country with a sketchy power grid and unstable internet connection: even if it will evolve, my margin for error starting is limitted. That being said. My goal is to go may be Odoo then plug Claude (using Claude code) then using hostinger or infomaniak(unless there is better solutions). My biggest struggle or question right now: Making an educated guess that won't come bite me strong..Making mistakes isn't the issue here, more like starting strong and setting it up for sucess. Happy to share and discuss more with more educated people here.Thank you P.S. English not being my first language sometimes makes it a little challenging with the tech Cheers