---
name: status-text-usage
description: >
Use after component-usage-ux when an app needs @techsio/ui-kit StatusText
for inline validation, success, warning, or default status messages with
default-on state icons and size/alignment props.
metadata:
component_version: "1.2.0"
type: "core"
library: "@techsio/ui-kit"
library_version: "0.3.2"
requires: "component-usage-ux app-token-overrides ux-guidelines"
resources: "references/ux.md ../../references/component-contracts.md ../../references/consumer_app_usage_rules.md"
sources: ""
contributor_sources: "libs/ui/src/atoms/status-text.tsx libs/ui/src/tokens/components/atoms/_status-text.css libs/ui/stories/atoms/status-text.stories.tsx libs/ui/src/atoms/status-text.figma.ts"
audience: "consumer"
---
> Portable scope: Use the installed package's exported types and bundled sibling skills. Repository source paths are optional contributor evidence, not consumer prerequisites; use the consuming app's own checks. Resolve ../../references/ paths from this skill's folder, not the app working directory.
# @techsio/ui-kit StatusText Usage
Use StatusText for short inline messages that describe a nearby field, section,
or operation result. Default error, success and warning icons use distinct solid
circle, check and triangle silhouettes; keep `icon` for deliberate caller overrides.
Business neutral hints share the validation text column without adding an icon or
live role. Other brands retain their alignment; caller padding classes and explicit
icons override the neutral prefix.
## UX/UI guidelines
House rules come from the `ux-guidelines` skill (writing, formatting, states,
where actions and feedback live). This section applies them to `StatusText`.
**Use it when**
- Short inline messages tied to a nearby field, section or operation: validation hints, section-level warnings, `Last saved 2 minutes ago`.
**Use something else when**
| Need | Use instead |
| --- | --- |
| Transient confirmation of an action | Toast |
| List of form errors after submit | FormErrorSummary |
| Short state label | Badge |
| Blocking decision | Dialog |
**Do**
- Place it directly under/next to what it describes.
- Use `status` by meaning: `error` blocks, `warning` informs of a consequence, `success` confirms, `default` neutral.
- Keep the icon — colour must not be the only signal.
**Don't**
- Stack many status texts; summarise.
- Use it for long instructions — use help text or docs.
**Copy and states**
- One sentence: what + how to fix for errors (ux-guidelines/ux-writing#messages).
**Behaviour (from the UX spec)**
- A service failure is never phrased as a user input error (`Couldn't check the SKU. Try again.`, not `Invalid SKU`).
- `status` doesn't validate: the app decides when and links the message to its field (`aria-describedby`, `aria-errormessage`). The kit only sets the live role.
- `success` confirms the checked value, not a saved form or transaction. Product availability is `AvailabilityStatus`, not StatusText.
**Figma → code**
| Figma | Code |
| --- | --- |
| `status=default\|error\|success\|warning`, `size=sm\|md\|lg` | same prop names and values |
| — | `align="start" \| "center"`, `showIcon`, `icon` |
Full UX page (anatomy, states, behaviour, edge cases): [references/ux.md](references/ux.md). The same page renders in Storybook as *Atoms/StatusText → UX guidelines*.
## Setup
```tsx
import { StatusText } from "@techsio/ui-kit/atoms/status-text"
Email is required.
``` Correct: ```tsx]*className=.*(text-red|text-green|text-warning|text-success)" apps
rg -n "