Status & Feedback
Badge
Compact labels with shadcn-aligned variants (destructive, ghost, outline), optional asChild link, icons via data-icon, Spinner states, and extra semantic variants. Explain what is happening, what changed and what someone can do next. Pair visual status with language that still makes sense without its color. Import it from @/components/kamod-ui/badge.
Source · Design reference · API reference · Theming · Styles
Interactive preview
Preact example Local preview theme · Responsive styles follow the preview widthFull widthInstallation
Import Badge from @/components/kamod-ui/badge.
pnpm add @kamod-ch/uiCopy an example with @kamod-ch/ui or the matching @kamod-ch/ui/… subpath. The code block switches between those two installs. Connect The Global Theme CSS and Tailwind Source Detection before your first render.
import { Badge } from "@kamod-ch/ui";Usage
Pick a variant for status. Use a link or button when the badge should navigate or act.
import { Badge } from "@kamod-ch/ui";Choose a complete composition from the examples below; required child components and props vary by pattern.
Interactive preview
Preact example Local preview theme · Responsive styles follow the preview widthFull widthComponent Examples & Variants
Explore Badge in Different Contexts, from the starting pattern to the compositions below. Begin with Variants, then compare the examples that match your content, state and layout. These are working patterns to adapt, not a list of interchangeable variant values: check the API Reference before using a prop or combining behaviors. Look at the surrounding labels, supporting text and spacing as well as the component itself.
Read the Result and Its Implementation Together. Use each showcase’s Code view to inspect imports and composition, or its Prompt view to prepare a setup or adaptation brief. Try the narrow preview and local theme controls before connecting real data, and use Reset to return an example to its initial state. Keep layout changes in class utilities where appropriate; follow the Component Styles Guide for hierarchy and the Theming Guide for shared surfaces and colors. The Accessibility Notes explain what to preserve when making those changes.
Variants
Choose variant for the status. Use Link when the badge should navigate.
Interactive preview
Preact example Local preview theme · Responsive styles follow the preview widthFull widthIcon and Spinner
Mark an icon or Spinner with data-icon="inline-start" or data-icon="inline-end".
Interactive preview
Preact example Local preview theme · Responsive styles follow the preview widthFull widthLink
Use asChild or href when the badge is a destination. Use a button when it only changes local state.
Interactive preview
Preact example Local preview theme · Responsive styles follow the preview widthFull widthSizes
Set size from xxs to lg to match the surrounding metadata.
Interactive preview
Preact example Local preview theme · Responsive styles follow the preview widthFull widthProps and Data
Configure Badge using the contracts below. Read the documented options alongside the Source Definitions to understand which values your application supplies and which details the component owns. Start with a prop or helper, then follow its type link to inspect the declaration without leaving the page.
Badge props and accepted values.
Type cards are extracted from this checkout’s TypeScript source at build time. Props inherited through HTMLAttributes, Omit or variant helpers remain references in those declarations; their fields are not flattened here. Match the reference to your installed version, and check a package’s exports before writing an import type. A type exported by a source file is not necessarily re-exported by @kamod-ch/ui.
Component Props
? means a field can be omitted; it does not promise a fallback value. Existing documented defaults remain alongside the descriptions. For callbacks, check the argument and return types before connecting your own state or services.Badge
BadgeProps
| Prop / type | Description |
|---|---|
asChild | Configure
|
children | Configure
|
class | Configure
|
href | Configure
|
size | Configure
|
variant | Configure
|
Data Type Reference
Expand a card to inspect and copy the exact declaration. The code header identifies its repository file; follow imported or inherited types in the Implementation Source when you need the complete dependency chain. Required-field summaries cover fields declared directly in that type. Source-only helpers and inferred schema outputs describe the local implementation, not additional props you can pass to every component.
Badge Props
DeclarationBadgePropsBadge.tsx. Referenced types retain their original names; inspect that file for imports and supporting definitions. Inspect the Complete Definition of BadgeProps before adapting it.Accessibility
Badge provides compact visual emphasis; it does not automatically announce state changes or turn its label into a control. Its color and variant remain presentation choices rather than a complete status description.
You have the pieces. Put them into one real interaction, keep its state in one place, and check the result with the content your application will actually show.
Connect the Foundation
Return to Choose and Compose Components to connect this reference to a working screen. Keep global CSS in one entrypoint and import only the components that screen needs.
Build the Surrounding Screen
Find a neighboring interaction in the Component Library, or start with a complete Block. Replace sample content and destinations before refining the layout; a local class change can stay with the composition.
Make the Result Hold Up
Use shared theme roles for changes that belong everywhere. Then review the whole journey: keyboard focus, long labels, narrow screens and a clear way to recover when something fails.
Keep a link to the source and note your intentional changes. Your next edit should begin with a clear decision, not another search.