5 tricks after 5 Projects Deployed with Agent [Important]

Hello friends, today I bring you 5 tricks that I use to make the agent work correctly and be as economical as possible.

  1. Every time you make a new feature, create a new chat with the agent so you have all the chats grouped by feature. I’ve also noticed that the agent is more informed specifically for that feature so he uses the feature implementation chat to polish it as much as possible before starting a new chat.

  2. IMPORTANT: When the agent gets stuck and can’t find the error, tell him to add logs to each action in the code so he can copy and paste the error log so he knows how to fix it.

  3. Sometimes if you ask him to redesign a dashboard, for example, he may break the entire design of the app. Tell him to check that each page has the same design and, above all, introduce the phrase “CONSISTENT DESIGN BETWEEN PAGES” and add it to the log of the main file so that he always takes it into account.

  4. IMPORTANT!!!: When connecting APIs, for example the Meta API, the knowledge is not as extensive as you think. You must rip all the documentation into a .txt and attach it when you do the implementation (THE API VERSION IS IMPORTANT, you must tell it which one you will use v19, v20, v21 etc…). By importing all the documentation, the success rate is 100% for me.

  5. IMPORTANT MONEY SAVING: If for whatever reason you create a project and YOU NOTICE THAT THE AGENT freezes a lot, gets stuck for a long time, doesn’t finish fixing errors, (!!!) DOESN’T STOP REINSTALLING PACKAGES over and over again even though they are already installed (YOU CAN SEE THIS IN THE PROGRESS TAB) my advice is to delete the project and start from scratch. If you keep the bug project it may take more steps than normal, and cost you more money than starting the project from scratch.

10 Likes

Great advice. Especially #1 and #2.

Can you say more about #3? What does this mean? How would I do it?

1 Like