SAP-samples

Ui5con 2026 Chrome Built In AI — AI skill for Claude Code

AI community

A hands-on workshop repo that teaches UI5 developers how to add on-device AI to a small UI5 (TypeScript) app - summarize, detect, translate, and classify support tickets in the browser with Chrome's b.

How to install Ui5con 2026 Chrome Built In AI

This entry records only its repository, not the path inside it, so there is no exact command to give. Open SAP-samples/ui5con-2026-chrome-built-in-ai and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Ui5con 2026 Chrome Built In AI does

Alternatives in AI

Openase — Ticket-Driven Automated Software Engineering 265 ★
Laravel AI Translator — High quality automatic translate your language files into many languages using AI like Claude, GPT and etc 250 ★
Fallow Skills — Agent skills for fallow, codebase intelligence for TypeScript and JavaScript 116 ★

README

UI5 Chrome AI Workshop — Hands-On

[![REUSE status](https://api.reuse.software/badge/github.com/SAP-samples/ui5con-2026-chrome-built-in-ai)](https://api.reuse.software/info/github.com/SAP-samples/ui5con-2026-chrome-built-in-ai)

Build a multilingual customer-feedback triage app in UI5 that uses Chrome's built-in AI APIs — **no backend LLM, no API key, no cost**. Every model runs on-device. Ticket data is served by a small OData V4 service that ships ready-made in the starter — the workshop focuses on **UI5 + the Chrome AI APIs**.

What you'll build

A UI5 List/Detail app where support tickets in mixed languages (DE / ES / FR / EN) get:

Auto-detected language (LanguageDetector API)
One-line TL;DR summary (Summarizer API)
Structured metadata: sentiment, category, priority (Prompt API + JSON Schema)
On-demand translation to English (Translator API)
A drafted reply in the customer's language (Writer API + Prompt-API fallback)

Two ways to build it — pick your track

Both tracks clone the same starter (a runnable base UI5 app + data service) and end at the identical finished app. Every step gives you the exact change (or the exact prompt) to reach the next — no step is left implicit.

🅐 [Manual track](docs/manual/README.md) — apply diffs, no assistant

Each AI feature is a small **diff** you apply to a file, with the full file one click away in a collapsed section for recovery. Best if you want to understand every line, or you don't have an MCP-capable assistant.

→ **[Start the manual track](docs/manual/README.md)**

🅑 [AI-assistant track](docs/ai/README.md) — prompt-driven with MCP

You drive Claude Code / Cursor / Copilot with UI5 MCP wired up. Each exercise gives you a precise prompt, then points you at the matching manual exercise as the **answer key** to diff against. Best if you want to learn MCP-augmented UI5 development.

→ **[Start the AI-assistant track](docs/ai/README.md)**

Both tracks share the same steps:

| Step | Chrome AI AP