Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
ui5 avatar

Ui5 Best Practices Integration Cards

  • 28 installs
  • 32 repo stars
  • Updated August 4, 2026
  • ui5/plugins-coding-agents

ui5-best-practices-integration-cards is a reference agent skill for builders shipping SAP UI5 and OpenUI5 experiences with Analytical Integration Cards.

About

ui5-best-practices-integration-cards is a reference agent skill for builders shipping SAP UI5 and OpenUI5 experiences with Analytical Integration Cards. It enumerates supported chart types and the exact feed UIDs each visualization requires so measure and dimension bindings in card JSON stay valid. Examples spell out `measures`, `dimensions`, and `feeds` arrays—for instance donut and pie charts using `size` and `color`, or heatmaps pairing two category axes with a color measure. Solo developers and small ERP extension teams use it while coding card manifests so agents do not invent incompatible feed identifiers or mis-map data fields. It complements broader UI5 practice skills by narrowing focus to integration-card analytics configuration, reducing rework when cards render empty or fail validation in SAP BTP or on-prem Fiori launchpads.

  • Comprehensive chart-type catalog for Analytical Integration Cards with required feed UIDs per visualization
  • Documents donut/pie bindings (`size`, `color`, `dataFrame`) with copy-ready JSON snippets
  • Documents heatmap bindings (`categoryAxis`, `categoryAxis2`, `color`) for two-dimensional categories
  • Shows measures/dimensions objects wired through `feeds` to chart-specific UIDs
  • Prevents agent hallucination on invalid feed names when generating card descriptors

Ui5 Best Practices Integration Cards by the numbers

  • 28 all-time installs (skills.sh)
  • Ranked #1,476 of 2,245 Frontend Development skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ui5/plugins-coding-agents --skill ui5-best-practices-integration-cards

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs28
repo stars32
Last updatedAugust 4, 2026
Repositoryui5/plugins-coding-agents

How do I configure SAP UI5 Analytical Integration Cards with correct chart feeds, measure/dimension bindings, and JSON card manifests.?

Configure SAP UI5 Analytical Integration Cards with correct chart feeds, measure/dimension bindings, and JSON card manifests.

Who is it for?

Best when you're working on frontend development and need structured help with ui5 best practices integration cards.

Skip if: Teams with no frontend development needs, or anyone wanting a generic chat assistant without this specific workflow.

When should I use this skill?

When you need to configure SAP UI5 Analytical Integration Cards with correct chart feeds, measure/dimension bindings, and JSON card manifests., or when ui5-best-practices-integration-cards is a reference agent skill for

What you get

Structured output aligned to ui5-best-practices-integration-cards: Comprehensive chart-type catalog for Analytical Integration Cards with required feed UIDs per visualization, Documents donut/pie bindings (`size`, `color

Files

SKILL.mdMarkdownGitHub ↗

Best practices for UI Integration Cards development

Rules an agent must follow when creating, modifying, validating, or previewing a UI Integration Card. Adherence is critical for working cards.

When to load each reference

TriggerLoad
Working on or planning an Analytical card`references/analytical_chart_types.md`
dt/Configuration.js exists, is being created, or is being modified`references/configuration_editor_example.md`

If the trigger applies, load before producing any output. Do not work from memory.

1. Core rules

RuleDetail
Prefer declarative cardsTypes: List, Table, Calendar, Timeline, Object, Analytical. Create an Extension only in exceptional cases.
Use create_integration_card MCP toolWhen creating a new declarative card.
Parameter binding syntax{parameters>/parameterKey/value} — single braces, > separator, value suffix.
Destination binding syntax{{destinations.destinationName}} — double braces, dot. Configure under sap.card/configuration/destinations/. Reference by name; never replace with raw URL.
Use destinations for service URLsWrap every external service URL in a destination under sap.card/configuration/destinations/ and reference it as {{destinations.name}}.
i18n bindingBind every non-data, user-visible string to the i18n model.
LinksUse the actions property; never inline <a> or hand-rolled URL handlers.
Validate before declaring doneSee 3. Validation.
Show preview when requestedSee 4. Preview.
Don't modify provided dataUse it as supplied.
JSON responses onlyThe endpoint behind sap.card/data/request must return JSON. For OData services, append $format=json to the request URL or parameters.

2. Data placement

sap.card/data/ is the only correct top-level location for the data request.

PathPurpose
sap.card/data/pathPrimary data path
sap.card/content/data/pathContent-specific path; overrides the primary path if set
sap.card/header/data/pathHeader-specific path; overrides the primary path if set

Forbidden: putting the request itself under sap.card/content/data/ or sap.card/header/data/.

Symptom — "No data to display": typically caused by a content/data block that overrides the primary data path. Verify 2. Data placement before debugging anything else.

3. Validation

RuleDetail
Valid JSONmanifest.json must parse.
sap.app/typeMust be "card".
Schema validationUse run_manifest_validation MCP tool.
No deprecated propertiesIn manifest.json or elsewhere.
Not a UI5 projectExcept for Component-type cards.

4. Preview

If asked to preview, first check the card folder for an existing preview entry point — package.json start script, README.md, or an existing HTML file. Reuse it if present. Otherwise create an HTML page with a <ui-integration-card> element pointing at the manifest, and serve via an http server.

5. Configuration Editor

The editor lets the Administrator, Page/Content Administrator, and Translator personas customize a card without editing manifest.json directly.

Two pieces: 1. dt/Configuration.js — exports a function that returns new Designtime({ form: {...} }). 2. manifest.json — references the file at sap.card/configuration/editor.

Design as the Administrator persona.

RuleDetail
Mirror the manifestEditor reflects the current structure and parameters of manifest.json exactly. manifestpath can target any existing path — a configuration/parameters/*/value for parameterized fields, or a direct path like /sap.card/header/icon/shape for static manifest properties.
All existing fields editableTitle, subtitle, header icon, parameters — make them configurable.
Ask the userBefore deciding which fields to expose, ask: "Make all manifest fields editable? Anything else to add?"
No invented fieldsNever add an editor field that does not exist in manifest.json.
Keep in syncAdd to or remove from the editor when adding to or removing from manifest.json.

Load `references/configuration_editor_example.md` for the canonical paired example.

6. Analytical cards

Load `references/analytical_chart_types.md` for the full chart-type catalog (UIDs and per-type examples).

RuleDetail
Set chartTypesap.card/content/chartType is required.
Match feeds to chart typemeasures, dimensions, and feeds must match the UIDs the chart type expects. The reference file lists them per chart.
Each feed needs three keystype (Dimension\
chartPropertiesUse it for labels, colors, legend, etc. Do not invent keys. Omit entirely if defaults are fine.

Minimal feeds example (donut/pie):

"feeds": [
  { "type": "Dimension", "uid": "color", "values": ["Store Name"] },
  { "type": "Measure", "uid": "size", "values": ["Revenue"] }
]

7. Card Explorer (reference)

  • Schema docs and live samples: <https://ui5.sap.com/test-resources/sap/ui/integration/demokit/cardExplorer/webapp/index.html>
  • Sample sources: <https://github.com/UI5/openui5/tree/master/src/sap.ui.integration/test/sap/ui/integration/demokit/cardExplorer/webapp/samples>

Related skills

FAQ

What does ui5-best-practices-integration-cards do?

ui5-best-practices-integration-cards is a reference agent skill for developers shipping SAP UI5 and OpenUI5 experiences with Analytical Integration Cards.

When should I use ui5-best-practices-integration-cards?

When you need to configure SAP UI5 Analytical Integration Cards with correct chart feeds, measure/dimension bindings, and JSON card manifests., or when ui5-best-practices-integration-cards is a reference agent skill for developers shipping sap ui5 and openui5 experiences with analy

What are the main capabilities?

Comprehensive chart-type catalog for Analytical Integration Cards with required feed UIDs per visualization; Documents donut/pie bindings (`size`, `color`, `dataFrame`) with copy-ready JSON snippets; Documents heatmap bindings (`categoryAxis`, `categoryAxis2`, `color`) for two-di

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.