shadcn_ui-toast
Shadcn UI — Toast
Instructions
Toasts are succinct temporary messages. Ensure a toaster is in the tree (e.g. ShadToaster). Get it with ShadToaster.of(context). Call toaster.show(ShadToast(...)) to show a toast; use toaster.hide() to dismiss (e.g. from an action button). Use ShadToast with optional title, description, and action. Use ShadToast.destructive for error-style toasts with a destructive action button (use ShadDecoration to style the action border).
Simple
ShadToaster.of(context).show(
const ShadToast(
description: Text('Your message has been sent.'),
),
);
With title
ShadToaster.of(context).show(
const ShadToast(
title: Text('Uh oh! Something went wrong'),
description: Text('There was a problem with your request'),
),
);
With action
ShadToaster.of(context).show(
ShadToast(
title: const Text('Uh oh! Something went wrong'),
description: const Text('There was a problem with your request'),
action: ShadButton.outline(
child: const Text('Try again'),
onPressed: () => ShadToaster.of(context).hide(),
),
),
);
Destructive
final theme = ShadTheme.of(context);
ShadToaster.of(context).show(
ShadToast.destructive(
title: const Text('Uh oh! Something went wrong'),
description: const Text('There was a problem with your request'),
action: ShadButton.destructive(
child: const Text('Try again'),
decoration: ShadDecoration(
border: ShadBorder.all(
color: theme.colorScheme.destructiveForeground,
width: 1,
),
),
onPressed: () => ShadToaster.of(context).hide(),
),
),
);
More from serverpod/skills-registry
riverpod-codegen-and-hooks
Use Riverpod code generation (@riverpod, riverpod_generator) and hooks (hooks_riverpod, HookConsumerWidget, flutter_hooks with Riverpod). Use when the user asks about @riverpod, code generation, riverpod_generator, when to use codegen, or using flutter_hooks with Riverpod (HookConsumerWidget, HookConsumer).
25riverpod-providers
Declare and use Riverpod providers (Provider, FutureProvider, StreamProvider, NotifierProvider, AsyncNotifierProvider, StreamNotifierProvider); unmodifiable vs modifiable, top-level declaration, Ref, Notifier build method. Use when creating providers, choosing provider type, writing Notifier classes, or understanding Riverpod state. Use this skill whenever the user asks about Riverpod providers, provider types, or notifiers.
24riverpod-consumers
Use Riverpod Consumer, ConsumerWidget, and ConsumerStatefulWidget to read and watch providers in widgets; WidgetRef, builder ref parameter. Use when building widgets that need to access Riverpod providers, ref.watch or ref.read in the UI, or converting StatelessWidget to ConsumerWidget. Prefer this skill when the user asks how to use providers in Flutter widgets or why ConsumerWidget is required.
19riverpod-getting-started
Install Riverpod (flutter_riverpod or riverpod), wrap the app in ProviderScope, run a hello-world provider, and optionally enable riverpod_lint and code generation. Use when starting a Flutter or Dart project with Riverpod, adding the Riverpod dependency, or setting up ProviderScope and a first provider. For version highlights see the official Riverpod docs.
18riverpod-auto-dispose
Enable automatic disposal of Riverpod providers when they have no listeners; keepAlive, onDispose, invalidate, ref.keepAlive. Use when preventing memory leaks, caching only while used, or cleaning up resources when a provider is no longer needed. Use this skill when the user asks about auto-dispose, keepAlive, or when to dispose Riverpod state.
17riverpod-refs
Use Ref and WidgetRef to read, watch, listen, invalidate, and refresh providers; onDispose and onCancel lifecycle; ref.read vs ref.watch vs ref.listen, ref.invalidate and ref.refresh. Use when interacting with Riverpod providers from widgets or other providers, when to use watch vs read, or when resetting provider state. Use this skill whenever the user asks about ref.watch, ref.read, ref.listen, ref.invalidate, or Riverpod lifecycle.
16