@geaux.eth

If you're into vibecoding apps and you don't know what a topology map is, congratulations- you're me literally 2 minutes ago. Let me save you HOURS of repeated prompting buy copying the following text: "Moving forward I want you to stop treating each feature-related request as isolated. Instead, I want you to understand the full topology of how features flow through the app. When I say "fix this feature" you should already know that means: The current functions of the feature. The current functions of the feature across the various apps it's experienced on. How these app experiences demand different things from our code based on the unique environments of the app(s) where the feature is deployed. Currently, you don't have that map in your head. You're discovering it reactively as I remind you of these things. The solution: You should create a feature topology document that maps out: All feature entry points - every way content enters the system All platform contexts - every environment the app runs in All content types - documents, audio, video, images, etc. that are relevant to the feature and the app The topology map now becomes a checklist you consult whenever I ask for a change. Instead of me telling you "don't forget to check how that's implemented there as well" - you should check the map and see it yourself. This topology check needs to be an automated feature moving forward." Use this next time you're working with @claudeai Grok or ChatGPT or any other LLM. Happy coding!

1 reply

2 recasts

8 reactions