What problem does it solve? Designing the data screens of a custom-code Databricks App (AppKit/React) often produces vague design memos that never translate into real components, or dashboards with dishonest scales, missing loading/empty/error states, and untrustworthy AI chat answers. This Skill turns UX intent into a concrete, buildable component plan grounded in AppKit primitives, dashboard design patterns, and IBCS notation. ## Core Features & Use Cases - Component-bound design proposals: Every design element is mapped to an actual component exported from @databricks/appkit or @databricks/appkit-ui, with queryKey bindings, semantic color tokens, and required states (loading, empty, error, partial). - IBCS notation and dashboard patterns: Applies scenario marks (actual/PY/plan/forecast), honest scales, message-in-title rules, and genre/composition patterns from the IEEE dashboard design patterns catalog. - Genie/AI trust surfaces: For apps with a Genie or natural-language chat surface, enforces five trust patterns — authenticated identity, inspectable generated SQL, streaming status, per-answer disclaimers, and truthful execution-identity disclosure. - Use Case: You are building a React Databricks App with a KPI overview page and a Genie chat panel. Use this Skill to produce a component plan specifying charts, palettes, Skeleton/Empty/Alert states, and the required Genie trust UI before writing code. ## Quick Start Use the databricks-app-design skill to design the KPI overview page and Genie chat surface of my AppKit React app with a full component plan.