Pt. 2: Communicating clearly

☞ CONTEXT IS KING. Sometimes, you and the AI are vibing on the same wavelength. Life is great. Claude is the best coworker you’ve ever had. Then – all of the sudden – you forget to explicitly reference a page, and it decides to rewrite a quarter of the app. Bugs multiply like they’re at a party hostel. Yikes. It seems that the AI sometimes just “forgets” about certain parts of your app. So, when prompting it, there is a way lower likelihood it goes rogue if you take care to always specify pages and elements by their given name. For example, “On the @HomeView, I’d like to change the Time Frame Selector that’s defined on the @BitshadesAppView.” Failure to do so sometimes led Claude to create redundant elements, disorganized code (e.g., centralized style elements defined in multiple places), or bugs.

☞ NAME YOUR AMBIGUOUS ELEMENTS. In order to be specific, you and Claude need to share some vocab. You can simply say, “Let’s call this the ‘Bitcoin price section’.” Claude will add a note in the code. This ensures you stay aligned when referencing parts of the code.

☞ PROVIDE DOCUMENTATION. Don’t forget that valuable context can lie in documentation. When I worked with the Kraken API, I uploaded a PDF of the API documentation and told it to reference the doc to understand how to structure its API calls.