It seems there is an issue with the link in the main post. Therefore here now the correct link to the article with the details: www.linkedin.com/pulse/lets-t...

Gemini 2.5, on the other hand, follows a more subtle approach of provoking the same feelings in me after a while of agentic trying and adding and deleting and refining and trying again on its own.

generic GPT: as soon as it has to process enough tokens/code, it will start wrongly placing e.g. the DynamicPage control in the "sap.m" namespace.

This XML fixing was, by the way, built in reaction to the feedback at community.sap.com/t5/sap-busin...

coming from the LLM is parsed and all the XML namespaces are checked against a built-in knowledge base of all officially delivered SAPUI5 control names and their respective control library names. Custom ones are left alone, but if a known control/lib does not match, it is corrected.

Try asking e.g.

There's definitely SAP-specific improvements on top. What exactly, depends on the use-case. Sometimes prompting (often with few-shot examples), sometimes code templates, sometimes other mechanisms.

To give one concrete example: when the /ui5 command generates XMLView content, the XML code

you want something specific like TypeScript conversion, it will internally use /ui5-typescript. This only works for topics within the "/ui5 realm", but as @marian.marianzeis.de mentioned, the idea is to provide this on a more general level.

Ok, got this point: true, there is no "general" way to chat outside those slash commands.

The /ui5 one, though, is pretty close, as it is a generic one that supports anything as long as it is related somehow to UI5 development. It is not focused on a specific use-case.
But still, when it detects

It's there.

LLMs doing LLM things. 🤷‍♂️

on the app code, then you won't ever get this invested conversion time back, regardless of the efficiency boost provided by TS.
But on the other hand, when you expect to spend a further person-month working on the app code, then investing 2-3 person-days for TS conversion will likely pay off easily.

Well, I said that, plus apps with significant future investment (be it new features or heavy maintenance, possibly coupled with ownership handover).

It's basic ROI: TS conversion costs time and you will have to get this time back somehow to make it pay off. If you won't spend any future time

As seen on me.sap.com/notes/3437766, SAP has contracts with various AI vendors incl. Anthropic, Google, Mistral. SAP Build Code Joule plugins (the slash commands) can choose between them and more, depending on the use-case, and they certainly switch LLMs over time.

No, the slash commands in the Joule chat window are not meant as restriction, but the opposite: they are custom-built enhancements on top of generic LLM capabilities by the respective teams. (used LLMs are different between them and changing over time)

but usually a good start for conversion)

This very error indicates that the version you got to use unfortunately contains a bad interim state with a change in base Joule that broke certain plugin features.
Fixed soon after, plus further improvements, but result will remain GenAI-level (never 100% correct, sometimes better, sometimes worse,

And of course the STL files for the #UI5 Cookie Cutter:
github.com/akudev/UI5er...

No requests? Ah, here is the recipe, nevertheless:
github.com/akudev/UI5er... :-P

I see you are already discussing with @ui5.bsky.social
But a related thing most might not know yet: openui5versiontracker.cfapps.eu10.hana.ondemand.com/OpenUI5Relea... is powering the releases page on openui5.org. Not sure it is useful for anything else, but it lists current releases with dates.