Generates the complete scaffolding of a CAP entity following the loaded conventions: CDS model, service projection, annotations.cds (labels + UI.LineItem), mock CSV header and i18n in two languages. Returns the content so you write it with cap_write_files and validate it with cap_validate.

Writes one or more files into the given CAP project. Creates folders when missing.

The validation loop. Runs cds compile on the project and returns the errors so the agent can fix them. A clean compile means the scaffolding is valid.

Second validation layer: runs cds lint (@sap/cds eslint plugin) on the project and returns anti-patterns and best-practice warnings that cds compile does not catch. Requires @sap/cds installed in the project.

Third CAP validation layer: deploys the model to a throwaway sqlite database and loads the db/data CSVs. Catches what cds compile cannot: CSV columns that do not exist on the entity, malformed data and duplicate keys. Requires @cap-js/sqlite installed in the project. The throwaway database is deleted afterwards.

Compiles the real project to CSN and returns a digest of the existing model: services, entities, fields with types and keys, associations and compositions. Call it BEFORE generating code so you reuse what exists instead of inventing fields or entities.

Analyzes a legacy freestyle UI5 app (manifest, XML views, controllers, i18n) in READ-ONLY mode and returns the migration inventory: OData datasources, sections, tables and columns, bound fields per model, value helps, actions and OData calls from the controllers. Use it as the starting point to migrate to modern CAP/Fiori together with cap_project_context and the conventions://cap knowledge.

Generates an ObjectPage section for a freestyle UI5 app following the real pattern: fragment with uxap:ObjectPageSection, SmartTable (table mode, with per-column p13nData) or SimpleForm (form mode), dotted i18n keys, handler stubs and i18n lines. Returns the content so you review it, write it with cap_write_files and validate it with ui5_validate_view.

The UI5 validation loop: checks that the XML is well-formed and that ALL declared event handlers (press, change, select...) exist in the controller. Returns the failures so the agent can fix them.

Third UI5 validation layer: runs SAP's official ui5lint on the app and returns deprecations and anti-patterns on the road to UI5 2.x that view validation does not catch (obsolete APIs, deprecated libs, CSP). Requires @ui5/linter installed in the app and a ui5.yaml at the root.