Authoring like Flutter#

Arcane Jaspr lets you decorate a single component instance and have every stylesheet render it in its own idiom. You describe intent; the active theme decides how that intent looks. This is the permeability model, and it is what keeps app code portable across Shadcn, Neon, and Neubrutalism without branching on the theme.

Two per-instance surfaces sit on every decoratable component (Card, Button, the card family, and more):

Reach for decoration: first. It is the surface that stays portable. Use styles: only when a supported literal value must override the theme. Raw CSS, custom filters, custom shadows, custom animations, and gradient backgrounds are not part of this public surface.

ArcaneDecoration#

ArcaneDecoration is the semantic, theme-permeable surface. Its fields fall into three buckets.

Source: lib/core/decoration/arcane_decoration.dart

Universal fields#

Universal fields render literally and identically on every theme. They are compiled straight to CSS by universalStyles().

Card(
  decoration: const ArcaneDecoration(
    color: 'var(--card)',
    borderRadius: Radius.md,
    border: '1px solid var(--border)',
    padding: EdgeInsets.all(24),
  ),
  child: const Text.body('Universal fields look the same on every theme.'),
)

The elevation intent#

elevation is an intent, not a pixel value. The call site names a depth; the active theme's decorationStyles hook maps that depth to its own shadow idiom.

enum Elevation { none, xs, sm, md, lg, xl }

The same Elevation.lg resolves through the selected stylesheet:

Card(
  decoration: const ArcaneDecoration(elevation: Elevation.lg),
  child: const Text.body('One depth. Three idioms.'),
)

The killer example#

One decoration, three idioms. The exact same app code:

Card(
  decoration: const ArcaneDecoration(
    elevation: Elevation.lg,
  ),
  child: const Text.body('Same code, three renderings.'),
)

renders as:

Nothing at the call site knows which theme is active. Swap the stylesheet on ArcaneApp and the same Card restyles itself.

ArcaneStyleData: bounded literal overrides#

styles: accepts a literal ArcaneStyleData. Whatever it sets is applied last and overrides both the theme and the decoration. Use it for values that must be exact regardless of theme.

Card(
  decoration: const ArcaneDecoration(elevation: Elevation.md),
  styles: const ArcaneStyleData(
    borderRadius: Radius.none,
    background: Background.surface,
  ),
  child: const Text.body('The literal styles layer always wins.'),
)

See Styling for the full ArcaneStyleData reference.

How the layers resolve#

Every decoratable component composes its inline style in a fixed order, and later layers win in the CSS cascade:

1. Theme base styles
2. Theme variant styles
3. decoration universal fields (color, borderRadius, border, padding)
4. Theme-resolved decorationStyles (the theme's interpretation of elevation)
5. Bounded literal styles: overrides

That ordering is the permeability contract: intent flows through the theme, and the literal layer is always last.

Source: lib/core/rendering/base/style_layering.dart