docs: consolidate AI guidance on the AI page only

Author: claude

docs/cookbook/view/definition.md

@@ -132,10 +132,6 @@ Every fluent helper ultimately produces an XML element. The lowest-level method
 
 This maps **1:1** to the UI5 XML/SDK API — control names, property names, and aggregation names are written exactly as they appear in the [UI5 SDK](https://sapui5.hana.ondemand.com), in their original camelCase. There is no abstraction layer guessing what to call things.
 
-::: tip Recommended for AI-assisted Development
-For AI-assisted coding, prefer the generic builder. It removes the need for the model to know the abap2UI5 naming conventions or guess which controls and properties are wrapped — the SDK documentation can be used directly. The fluent API in `Z2UI5_CL_XML_VIEW` is convenient for humans but its inconsistencies and incomplete coverage make it a poor target for code generation.
-:::
-
 The rest of this documentation uses the higher-level fluent API (`->page( )`, `->button( )`, `->multi_combo_box( )`) because it reads better in examples. Both styles can be mixed freely in the same view.
 
 #### Next Steps

docs/get_started/ai.md

@@ -104,7 +104,7 @@ Views are UI5 XML strings passed to `client->view_display( ... )`. The framework
 - **`z2ui5_cl_util_xml`** — generic XML builder. Element name + attributes as strings → maps **1:1** to the UI5 SDK. **Recommended for AI-generated code.**
 - **`z2ui5_cl_xml_view`** — fluent builder with one ABAP method per UI5 control (~446 methods). Convenient for humans, but has naming inconsistencies and incomplete coverage → harder for an AI to use correctly.
 
-→ [View Definition + AI Tip](/cookbook/view/definition#recommended-for-ai-assisted-development)
+→ [View Definition](/cookbook/view/definition)
 
 ## Recommended Builder for AI: `z2ui5_cl_util_xml`