Android
AuraScore 81/100

Wealth Management Android Compose Design System Governance Brief

Standardize high-density financial charting and accessible Jetpack Compose design systems for trading apps.

Use this prompt when building or auditing a declarative UI component library for brokerage, crypto trading, or wealth management interfaces requiring rigorous WCAG AAA compliance and high-frequency real-time updates.

Template

Role: Lead Android UI/UX Systems Engineer specializing in Jetpack Compose, high-density financial data visualizations, and accessibility standards.

Context

  • Trading Platform: {{brokerage_platform}}
  • Target Accessibility Mandate: {{target_wcag_level}}
  • Theme Engine Specification: {{theme_engine_spec}}
  • Financial Data Density Profile: {{data_density_profile}}
  • Architectural State Management: {{state_management_pattern}}
  • Target Screen Surfaces: {{multiplatform_surface}}

Task

Generate a comprehensive Jetpack Compose Design System Governance Brief that establishes architectural contracts for high-frequency ticker displays, real-time interactive financial charts, and accessible multi-theme trading components for {{brokerage_platform}}.

Method

  1. Define Compose atomic design tokens (Colors, Typography, Elevation, Shapes) governed by {{theme_engine_spec}} with automated contrast validation.
  2. Architect immutable state holders conforming to {{state_management_pattern}} to eliminate unnecessary recompositions during real-time order-book streaming.
  3. Standardize dynamic financial chart components (Candlestick, Depth Chart) optimized for {{data_density_profile}} utilizing custom DrawScope rendering.
  4. Specify screen reader (TalkBack) semantic tree traversal rules for complex financial tables and chart touch exploration under {{target_wcag_level}}.
  5. Design high-contrast and color-blind safe palettes for market volatility indicators (gain/loss/neutral states) within {{theme_engine_spec}}.
  6. Formulate testing guidelines incorporating Compose UI automated semantics assertions, screenshot regression tests, and Layout Inspector recomposition tracking.
  7. Detail layout adaptation patterns across {{multiplatform_surface}} to preserve critical order execution actions without clipping.

Constraints

  • MUST guarantee that all interactive touch targets meet or exceed minimum {{target_wcag_level}} surface specifications (48dp minimum).
  • MUST NOT trigger full layout passes or recompositions of parent containers during sub-second price ticker mutations.
  • Custom canvas drawings must provide fully synchronized accessible semantic nodes for TalkBack users.
  • Design tokens must strictly separate styling primitives from domain-specific trade logic.

Output format

An engineering design system brief containing the following explicit sections:

  1. Compose Token & Theming Architecture (covering {{theme_engine_spec}})
  2. Real-Time Canvas Charting & Recomposition Performance Model
  3. Accessibility & TalkBack Semantics Contract (mapped to {{target_wcag_level}})
  4. Multi-Surface Form Factor Adaptation Strategy Deliver as a structured technical brief between 750 and 1100 words.

Self-review

  • Ensure custom Canvas charting explanations specify @Stable / @Immutable data model bindings to prevent recomposition cascades.
  • Check that color-blind alternate indicators (e.g., shape and glyph support alongside green/red) are explicitly mandated.
  • Verify TalkBack traversal orders are unambiguously mapped for two-dimensional market tables.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-android
financial-services
android
jetpack-compose
design-system