Directions for AI to use wappler native functions

hello,

It’s been a while since I code with AI, now mostly I use claude opus advanced, but I see a problem that AI is constantly shifts to custom .js rather than wappler native functions so I end up with messy custom .js with 5k+ code lines eventualy, maybe any of you have a transcript or directions for the AI agents to improve their coding to use native wappler functions, or maybe some directions to any wappler docs as .pdf or similar. Thank you!

From a previous similar thread, this was George's recommendation.

I tested Opus 4.7 also well, and it is ok for creative/design work (although too expensive 7.5x requests), but for programming work it still does too complex solutions and GPT 5.4 is still the best.

I just use the web version, because wappler integrated one eats too many credits, but the question is, any directions for AI to avoid it getting custom .js and build with native wappler supported code?

We optimized the AI integration a while back, and it no longer uses a lot of credits, so please check it again. Just make sure to enable the experimental options for AI.

thanks, I will try it, but maybe you have any directions for the AI to make it push coding more native Wappler instead of custom .js as it does now?

Do you specify tgatcyou arevus8ng wappler app connect in questions? Also say "use native wappler solutions where possible"

yes, but still it seems that it tries to shift to custom .js and stleast some are always custom, but I do it on online version, maybe using wappler native lets it understand wappler supported coding?

A good place to start is to have the LLM review the entire contents of the lib directory (in your Project) and create a summary of the files and their purpose in to a text file. Then direct the LLM to the text file when starting a new session.