Actions & selectionExplore · Adapt · Compose
Button
Primary actions with variants and sizes; icons via data-icon; asChild for links; pairs with ButtonGroup and Spinner (shadcn Button pattern). Make the next action easy to recognize. Use visual emphasis deliberately and distinguish an action from a persistent selection or a navigation link. Explore the live examples, inspect their source and choose the composition that fits your interface before connecting it to your application's data.
The examples use @/components/kamod-ui/button in a Preact project. Follow the live result and its source together: compare supported options in the API reference, refine presentation with the component styles guide, and use shared theme tokens for consistent colors and surfaces. Preserve keyboard behavior and meaningful labels as you replace the sample content.
In this guide 7 sections
Installation
Import Button from @/components/kamod-ui/button. Use variant and size props; optional asChild to merge styles onto a child element (for example an anchor).
pnpm add @kamod-ch/uiThe @/components/kamod-ui/… imports in these examples refer to local source files. Configure that alias when copying source, or use the corresponding exports from @kamod-ch/ui when installing the package. Connect the global theme CSS and Tailwind source detection before your first render.
import { Button } from "@/components/kamod-ui/button";<Button variant="outline">Button</Button>Usage
Primary actions with variants and sizes; icons via data-icon; asChild for links; pairs with ButtonGroup and Spinner (shadcn Button pattern).
import { Button } from "@/components/kamod-ui/button"
import { Spinner } from "@/components/kamod-ui/spinner";<Button disabled>
<Spinner size="sm" data-icon="inline-start" />
Generating
</Button>Component examples & variants
Explore Button in different contexts, from the starting pattern to the compositions below. Begin with Cursor, 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.
Cursor
Tailwind v4 defaults buttons to cursor: default. Kamod Button sets cursor-pointer (and disabled:cursor-not-allowed). If you use native buttons outside this component, you can mirror shadcn’s base layer snippet:
@layer base {
button:not(:disabled),
[role="button"]:not(:disabled) {
cursor: pointer;
}
}Size
Use the size prop to change height and padding. Icon sizes pair with text sizes (xs → icon-xs, and so on). Kamod also supports size="xxs" for ultra-compact UI (not shown in the grid below).
Default
Primary emphasis — default variant.
Outline
Bordered surface; works well in dense toolbars.
Secondary
Supporting actions with muted fill.
Inverse
High-contrast filled control using foreground on background (for example Cursor marketing dark CTA in light mode; flips in dark mode).
Ghost
Minimal chrome until hover.
Destructive
Dangerous or irreversible actions.
Link
Underline-style control while keeping button semantics.
Icon
Icon-only control; always set aria-label.
With icon
Add data-icon="inline-start" or data-icon="inline-end" on the icon so horizontal padding stays balanced.
Rounded
Use rounded-full (or other radius utilities) for pill or circular buttons.
Spinner
Show loading state with Spinner plus data-icon placement (start vs end).
As child
Merge button styles onto another element — common for links that should look like buttons.
Props and data
Configure Button 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.
Button props and accepted values.
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.TypeScriptComponent 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.Button
Wrapper around button (or anchor with href) that applies variant and size tokens.
| Prop / type | Description |
|---|---|
variant | Documented variant option for Button. Check its type alongside the usage examples before supplying a value. Documented default |
size | Documented size option for Button. Check its type alongside the usage examples before supplying a value. Documented default |
asChild | Documented asChild option for Button. Check its type alongside the usage examples before supplying a value. Documented default |
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.
CommonPropsButtonPropsAccessibility
Build the complete interaction, including the parts outside Button. The notes below distinguish the current implementation from the labels, content and behavior your application supplies. Start with the live preview, check the props and data reference, and test the finished composition with real content rather than assuming that an unchanged visual example covers every use case.
Built-in behavior and defaults
Button renders a native button, an anchor when href is supplied, or the provided child with asChild. Its variant changes appearance, not semantics. The native button path does not set a default type, so browser form-submission behavior still matters.
Labels and relationships
Use visible action text wherever possible. An icon-only button needs a name describing its result, such as Download invoice. Decorative icons should be hidden from assistive technology, and a tooltip should supplement rather than supply the only dependable name.
Keyboard and focus
Native buttons activate with Enter and Space; links retain normal navigation behavior. Set type="button" for secondary form actions and type="submit" for submission. With asChild, choose an element that already supports the required interaction.
States and integration details
A disabled-looking anchor is still a link unless your application handles it appropriately. Avoid replacing a button with a clickable div, hiding the focus ring or using loading feedback that erases the action's accessible name.
Verify the complete interaction
Check behavior as well as markup. Work through these scenarios in the application where the component will be used. Automated checks can help find structural problems; also review the reading experience with a screen reader, keyboard focus and the actual feedback from your application.
- Activate each variant by keyboard and verify a secondary action does not submit its surrounding form.
- Inspect icon-only names and loading/disabled states without relying on a tooltip.
- Check that links have real destinations and that custom children preserve one interactive element.
Recheck the result after changing theme tokens, translations or class overrides. Include text enlargement, narrow layouts and reduced-motion settings where animation is present. Inspect the component source when a behavior differs from your expectation; a role or state attribute does not implement keyboard interaction by itself.
For background, read the WAI-ARIA authoring guidance and keyboard interface guidance. These explain the patterns; verify browser and assistive-technology behavior for the implementation and audience you actually support.
Build it into your interface
Use the Button examples as a starting point, then review the behavior in the context of your own screen. Layout, state and content should work together.
Connect the behavior
Use an action label that describes the result. Within a form, choose button types deliberately so a secondary action does not submit accidentally. Use the supported selected or pressed state for persistent choices, and provide an accessible name for icon-only controls.
Copy the composition, then connect its intent. Replace sample records and callbacks with your own data flow. For options such as value, defaultValue, open or onChange, use only those documented in this component's API; different components expose different contracts.
Give each piece of state one owner. Keep a temporary selection inside the interface when nothing else needs it; lift shared values into a parent when other controls depend on them. Read the prop reference before combining controlled values with defaults. A default normally initializes a control; it is not a substitute for updating its current value.
Connect requests in an event handler or your application’s data layer, never as a side effect of rendering. Keep pending, completed and failed outcomes distinct, preserve useful input after an error, and offer a clear recovery action. If the integration subscribes to an external source, remove that subscription when its owner unmounts; cancel or ignore obsolete requests so an earlier response cannot replace newer results.
Start with the live preview, then exercise the same interaction with your actual data. The type definitions describe accepted values; they do not implement persistence, navigation or server-side validation for you. Keep those responsibilities in the application that composes the UI.
Refine the presentation
Let a parent own the surrounding spacing. Keep related elements together with gap and use semantic surface/foreground pairs so the composition follows the active theme. The wrapper below changes the surrounding layout without assuming extra props on Button.
import type { ComponentChildren } from "preact";
export function ExampleSurface({ children }: { children: ComponentChildren }) {
return (
<div class="grid min-w-0 gap-4 rounded-lg border border-border bg-card p-4 text-card-foreground sm:p-6">
{children}
</div>
);
}Put the chosen example inside ExampleSurface, then refine supported variants and sizes using the API above. For application-wide changes, adjust theme tokens instead of repeating fixed colors. See Component styles for hierarchy, density and focus treatments.
Review the complete interaction
- Check hover, focus, pressed and disabled states using both pointer and keyboard.
- For asynchronous actions, prevent duplicate submissions and show a useful pending label.
- Keep the primary action recognizable when labels wrap, text is enlarged or the theme changes.
The preview's narrow control changes its container width. Also resize the browser when checking viewport-based Tailwind utilities such as sm: and md:, and test overlays in the full page where their portals render.
Compose a complete interface
Button is one part of the interaction. Choose companion components for the information or actions that still need a place on the screen. The references below are suggestions to compose deliberately, not extra dependencies you must add to every example.
Keep one source of truth for the operation and let each component communicate a different part of it. For example, waiting, no results and failure need different explanations. Avoid showing contradictory states together, and keep recovery actions close to the message that explains them.
Start with the smallest composition that explains the task. Browse the component library for individual controls or the block collections for complete layouts. Reuse shared theme tokens so these pieces feel consistent in light and dark mode.
Sources & design references
Follow Button from its implementation to the ideas behind your own composition. Start with the local API, explore a visual direction, then bring the result back to your app’s shared styles.
Bring it back to your app
A reference becomes useful when it fits your real content. Work through these decisions in order:
- Keep the behavior grounded. Start with the interactive examples, then connect your data and callbacks using the integration guidance. Preserve labels, keyboard access and disabled states as you change the presentation.
- Make the styling repeatable. Use the styles guide for local
classadjustments and theming documentation for shared color decisions. Keep semantic surface and foreground pairs together in both light and dark mode. - Check the complete screen. See how components combine in the block collections, then try long labels, loading states and narrow layouts in your own composition. The Theme Toggle guide helps you expose a scheme switch in the finished interface.