๐ ๐ ๐๐ ๐๐ผ๐ฑ๐ฒ ๐ช๐ฎ๐ ๐๐ถ๐ป๐ฒ. ๐ ๐ ๐๐ป๐ถ๐๐ถ๐ฎ๐น ๐ฃ๐น๐ฎ๐ป ๐ช๐ฎ๐ ๐ ๐ ๐ฒ๐๐. I used to hit the same wall. I'd get excited about an app idea and start building with no plan. Halfway through, I'd get stuck and have to rewrite or throw away code. I blamed the tools, but the problem was me. Without a proper plan, the AI designed things its own way. I'd spend the rest of the project fixing things. I asked for help and got advice that changed how I work. Here's my new workflow:
- Keep your first plan short and simple
- Include user type, main job, screens, data objects, and what not to build yet
- Write down what the app should not do - this helps prevent the AI from inventing scope you didn't ask for I now let the plan emerge through conversation with the AI. I describe my idea and ask the AI to propose a data model and screens. I give the AI rules to push back and ask for pros and cons. This helps me get a design partner, not a cheerleader. The AI's Plan Mode works even with no code. I open an empty folder, describe my idea, and let the AI propose a structure. I review the plan, push back, and approve it when it matches my idea. My new steps:
- Open Plan Mode and describe my idea
- Let the AI propose a short plan
- Demand pros, cons, and alternatives
- Capture non-goals and move them to a permanent file
- Approve the plan, then build I'm not trying to write the perfect plan. I bring the intent, and the AI helps me find the plan. Source: https://dev.to/stkremen/my-ai-code-was-fine-my-initial-plan-was-a-mess-58m7 Optional learning community: https://t.me/GyaanSetuAi