April, 2026
I usually copy/paste my framework into the new project’s directory.
I have a subdir called /app that contains the generic structure for auth, security, etc.
I delete all the project-specific controllers/models/helpers. I keep just the skeleton. Some views and partials are useful, so I leave them as-is.
Then I write an initial prompt that usually takes me 1–2 hours to craft. I put all the details there and how I imagine the integration with the elements in /app, the basic structure of controllers and models, and a few views, starting with the “core business” ones — the central value-aggregation point of the product.
Next I ask the agent to analyze and ask follow-up questions. Once everything is broken down in implementation terms, I authorize the first build.
That build generates a few hours of analysis and follow-up questions to the agent.
Meanwhile, I take that time to study documents related to the business processes the app supports, and often times, some legal aspects and impacting laws.
I request a review and a second build. I finish by asking for a GEMINI.md checking in English with all project details, from architecture to business rules. It needs to be a mirror of my initial prompt with the refinements.
Work continues from there with the usual iterations with the agent — much more “micro” or “granular” than the initial phase. Before each PR the GEMINI.md is updated and the commit message is generated.
++ I noticed that if I fail to update GEMINI.md or if it is not correctly updated by the model, this may generate issues in future interactions when the model reads the documentation.
March, 2026
I usually copy/paste my framework into the new project’s directory.
I have a subdir called /app that contains the generic structure for auth, security, etc.
I delete all the project-specific controllers/models/helpers. I keep just the skeleton. Some views and partials are useful, so I leave them as-is.
Then I write an initial prompt that usually takes me 1–2 hours to craft. I put all the details there and how I imagine the integration with the elements in /app, the basic structure of controllers and models, and a few views, starting with the “core business” ones — the central value-aggregation point of the product.
Next I ask the agent to analyze and ask follow-up questions. Once everything is broken down in implementation terms, I authorize the first build.
That build generates a few hours of analysis and follow-up questions to the agent.
Meanwhile, I take that time to study documents related to the business processes the app supports, and often times, some legal aspects and impacting laws.
I request a review and a second build. I finish by asking for a GEMINI.md checking in English with all project details, from architecture to business rules. It needs to be a mirror of my initial prompt with the refinements.
Work continues from there with the usual iterations with the agent — much more “micro” or “granular” than the initial phase. Before each PR the GEMINI.md is updated and the commit message is generated.