@nanisoft/prism-llms 0.4.0 → 0.5.1

package/dist/md/components/accordion.md

@@ -0,0 +1,108 @@
+# Accordion
+
+The stack of headers that each reveal a panel in place.
+
+```tsx
+import { Accordion, AccordionItem, AccordionTrigger, AccordionContent } from '@nanisoft/prism-ui/components/accordion'
+```
+
+## Overview
+
+An Accordion is a stack of headers that each reveal a panel in place. It ships
+as `Accordion`, `AccordionItem`, `AccordionTrigger` and `AccordionContent`, all
+from the same module. Only one item is open at a time unless `multiple` is set.
+
+Each trigger is a real button, and the library ties it to its panel, so the
+header announces whether the item is expanded. Enter or Space opens the focused
+item, and the header text stays visible when the panel is closed.
+
+## Guidelines
+
+### When to use
+
+Use an Accordion when a page holds several long sections that a reader opens
+selectively: frequently asked questions, advanced settings, or a policy split
+into questions.
+
+### When not to use
+
+Do not use an Accordion when the reader needs two sections side by side. Only
+one is open at a time by default, so comparison is impossible.
+
+Do not use it to hide the primary content of a page. If a section is essential,
+it should be open, not behind a click.
+
+Do not use an Accordion for a short list of statements. A definition list reads
+better and needs no interaction.
+
+### Best practices
+
+- Give every `AccordionItem` a stable `value`, and control the open set with
+  `value` and `onValueChange` when the state matters beyond the component.
+- Open the item a reader most likely wants first, or none at all. Opening all of
+  them restores the wall of text the accordion was meant to break up.
+- Use one heading level for the triggers. Each header is a heading element, so
+  the accordion participates in the page outline.
+- Keep the trigger text a short question or label the reader can scan without
+  opening the panel.
+- Set `multiple` only when the sections are truly independent and comparing them
+  is a normal task.
+
+### Content guidelines
+
+- Phrase the trigger as the question or the topic, not as "Click to expand".
+- Use sentence case and a question mark on a question, no period on a label.
+- Keep the panel prose self-contained. A reader who opens one item should not
+  need another to make sense of it.
+
+**An accordion with one panel open and the rest available on demand.**
+
+```tsx
+'use client'
+
+import {
+  Accordion,
+  AccordionContent,
+  AccordionItem,
+  AccordionTrigger,
+} from '@nanisoft/prism-ui/components/accordion'
+
+/** An accordion with one panel open and the rest available on demand. */
+export default function AccordionDemo() {
+  return (
+    <Accordion defaultValue={['shipping']} className="max-w-measure-narrow">
+      <AccordionItem value="shipping">
+        <AccordionTrigger>How long does shipping take?</AccordionTrigger>
+        <AccordionContent>
+          Orders leave the warehouse within one working day and arrive in two to
+          five, depending on the region.
+        </AccordionContent>
+      </AccordionItem>
+      <AccordionItem value="returns">
+        <AccordionTrigger>What is the return window?</AccordionTrigger>
+        <AccordionContent>
+          Return anything unused within thirty days for a full refund.
+        </AccordionContent>
+      </AccordionItem>
+      <AccordionItem value="support">
+        <AccordionTrigger>How do I reach support?</AccordionTrigger>
+        <AccordionContent>
+          Reply to any order email, or write to support and include the order
+          number.
+        </AccordionContent>
+      </AccordionItem>
+    </Accordion>
+  )
+}
+```
+
+## Props
+
+**`value`** `string[]` · optional · default: — — The open item values, when the accordion is controlled.
+**`defaultValue`** `string[]` · optional · default: — — The item values open initially, for an uncontrolled accordion.
+**`onValueChange`** `(value: string[]) => void` · optional · default: — — Called when the open set changes.
+**`multiple`** `boolean` · optional · default: — — Whether more than one item may be open at once.
+**`disabled`** `boolean` · optional · default: — — Whether every item ignores user interaction.
+**`hiddenUntilFound`** `boolean` · optional · default: — — Whether the browser's page search may expand a panel.
+**`keepMounted`** `boolean` · optional · default: — — Whether a closed panel stays in the DOM.
+**`onOpenChange`** `(open: boolean) => void` · optional · default: — — Called when this item opens or closes.

package/dist/md/components/alert.md

@@ -1,14 +1,97 @@
 # Alert
 
-antd Alert, unchanged — a pass-through re-export. Import from '@nanisoft/prism-ui'.
+A static callout that carries an important message to the reader.
 
-```ts
-import { Alert } from '@nanisoft/prism-ui/components';
+```tsx
+import { Alert, AlertTitle, AlertDescription } from '@nanisoft/prism-ui/components/alert'
 ```
 
-`Alert` is antd's [Alert](https://ant.design/components/alert), re-exported unchanged.
+## Overview
 
-- Extends: antd **Alert** — for inherited props and demos, use the antd MCP (`antd_info Alert`).
-- Always import from '@nanisoft/prism-ui', never from `antd` directly.
+An Alert is a static callout that carries an important message in place. It
+ships as `Alert`, `AlertTitle` and `AlertDescription`, all from the same module.
 
-_No additional props beyond the antd base component._
+The root renders a `<div role="alert">`, so assistive technology announces it
+when it enters the document. `variant="destructive"` switches the border and
+text to the destructive token for an error; the default is the neutral surface.
+The icon, when one is passed as the first child, is placed beside the text and
+takes the variant's colour.
+
+## Guidelines
+
+### When to use
+
+Use an Alert for a message that must be read before the reader continues: a
+failed publish, a failed connection, a maintenance window, a consequence of the
+action they are about to take.
+
+### When not to use
+
+Do not use an Alert for a transient success. A message that confirms something
+happened should not occupy the page afterwards; a toast covers that case, and
+toasts are not in v1.
+
+Do not use an Alert for a field-level problem. A FieldError sits beside the
+control it belongs to.
+
+Do not use an Alert for a decision the reader must make before continuing. A
+dialog blocks the page and takes focus; an inline callout does neither.
+
+### Best practices
+
+- Lead with the condition in `AlertTitle` and put the next step in
+  `AlertDescription`. A reader scanning the page should get the point from the
+  title alone.
+- Keep the whole callout to two short sentences. Anything longer is documentation
+  and belongs in the page body.
+- Reserve `variant="destructive"` for a real failure. Using it for a warning
+  spends the one emphasis the system has.
+- Pair the colour with the word. The title carries the meaning; the variant
+  reinforces it.
+- Mark a decorative icon `aria-hidden` so it does not enter the announced text,
+  and never use the icon as the only signal of severity.
+- Place any action the message calls for just after the callout, not inside the
+  description, so the reading order stays simple.
+
+### Content guidelines
+
+- State the condition and the next step: "Publish failed. Fix the type error and
+  publish again."
+- Do not prefix the title with "Error" or "Warning". The variant and the words
+  already say it.
+- Use sentence case and no period in the title. The description takes full
+  sentences.
+
+**The neutral alert beside the destructive one.**
+
+```tsx
+import {
+  Alert,
+  AlertDescription,
+  AlertTitle,
+} from '@nanisoft/prism-ui/components/alert'
+
+/** The neutral alert beside the destructive one. */
+export default function AlertDemo() {
+  return (
+    <div className="flex flex-col gap-4">
+      <Alert>
+        <AlertTitle>Scheduled maintenance</AlertTitle>
+        <AlertDescription>
+          Reads stay available on 3 October between 02:00 and 04:00.
+        </AlertDescription>
+      </Alert>
+      <Alert variant="destructive">
+        <AlertTitle>Publish failed</AlertTitle>
+        <AlertDescription>
+          The build did not finish. Fix the type error and publish again.
+        </AlertDescription>
+      </Alert>
+    </div>
+  )
+}
+```
+
+## Props
+
+**`variant`** `"default" | "destructive" | null | undefined` · optional · default: —

package/dist/md/components/avatar.md

@@ -1,14 +1,96 @@
 # Avatar
 
-antd Avatar, unchanged — a pass-through re-export. Import from '@nanisoft/prism-ui'.
+The person or entity image with an initials fallback.
 
-```ts
-import { Avatar } from '@nanisoft/prism-ui/components';
+```tsx
+import { Avatar, AvatarImage, AvatarFallback } from '@nanisoft/prism-ui/components/avatar'
 ```
 
-`Avatar` is antd's [Avatar](https://ant.design/components/avatar), re-exported unchanged.
+## Overview
 
-- Extends: antd **Avatar** — for inherited props and demos, use the antd MCP (`antd_info Avatar`).
-- Always import from '@nanisoft/prism-ui', never from `antd` directly.
+An Avatar shows a person or entity's image, with an initials fallback when the
+image is missing or still loading. It ships as `Avatar`, `AvatarImage` and
+`AvatarFallback`, all from the same module. The fallback covers the moment
+before the image arrives and the case where it never does, so the control is
+never an empty circle.
 
-_No additional props beyond the antd base component._
+Size the root with `className`; the image and the fallback fill it. The image is
+a real `<img>`, so give it a meaningful `alt`, or leave `alt` empty when the
+adjacent name already identifies the person.
+
+## Guidelines
+
+### When to use
+
+Use an Avatar to represent a person or an entity in a list, a header, a comment
+or a member row, where a face or initials helps the reader identify the subject
+at a glance.
+
+### When not to use
+
+Do not use an Avatar as a control on its own. A clickable avatar is a Button or
+a link; wrap the Avatar rather than making the image interactive.
+
+Do not use one when the name alone is enough, such as a single signed-in user's
+own settings page. The name carries the meaning; the image adds noise.
+
+Do not use an Avatar for a decorative mark. A logo or an icon tile is a
+different job.
+
+### Best practices
+
+- Always render an `AvatarFallback`. Without it, a slow or missing image leaves
+  an empty circle.
+- Keep the fallback to one or two initials, derived from the name, and set
+  `text-xs` or smaller on a small avatar.
+- Give the image a name when it stands alone, and an empty `alt` when the name
+  sits beside it, so a screen reader does not read it twice.
+- Use one size per context. A list of avatars at mixed sizes makes the rows
+  harder to compare.
+- Do not encode status in the avatar alone. A presence dot needs a text
+  alternative nearby.
+
+### Content guidelines
+
+- Fall back to initials, not a generic icon, so the circle still identifies the
+  person.
+- Use the same name form in the fallback as in the adjacent label, so the two
+  read as one subject.
+- Keep the `alt` text to the person's name, without titles or roles.
+
+**Avatars with an image, initials fallbacks and a smaller size.**
+
+```tsx
+import { Avatar, AvatarFallback, AvatarImage } from '@nanisoft/prism-ui/components/avatar'
+
+const portrait =
+  "data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' width='80' height='80'><rect width='80' height='80' fill='%23111827'/><circle cx='40' cy='30' r='14' fill='%2394a3b8'/><rect x='16' y='50' width='48' height='40' rx='20' fill='%2394a3b8'/></svg>"
+
+/** Avatars with an image, initials fallbacks and a smaller size. */
+export default function AvatarDemo() {
+  return (
+    <div className="flex items-center gap-4">
+      <Avatar>
+        <AvatarImage src={portrait} alt="" />
+        <AvatarFallback>AL</AvatarFallback>
+      </Avatar>
+      <Avatar>
+        <AvatarFallback>PR</AvatarFallback>
+      </Avatar>
+      <Avatar className="size-8">
+        <AvatarFallback className="text-xs">SM</AvatarFallback>
+      </Avatar>
+      <Avatar className="size-12">
+        <AvatarImage src={portrait} alt="Ada Lovelace" />
+        <AvatarFallback>AL</AvatarFallback>
+      </Avatar>
+    </div>
+  )
+}
+```
+
+## Props
+
+**`onLoadingStatusChange`** `(status: 'idle' | 'loading' | 'loaded' | 'error') => void` · optional · default: — — Called when the image loading status changes.
+**`keepMounted`** `boolean` · optional · default: `false` — Whether the image stays mounted and loads in place.
+**`delay`** `number` · optional · default: `0` — How long to wait before showing the fallback, in milliseconds.

package/dist/md/components/badge.md

@@ -1,14 +1,81 @@
 # Badge
 
-antd Badge, unchanged — a pass-through re-export. Import from '@nanisoft/prism-ui'.
+A compact status or category label.
 
-```ts
-import { Badge } from '@nanisoft/prism-ui/components';
+```tsx
+import { Badge } from '@nanisoft/prism-ui/components/badge'
 ```
 
-`Badge` is antd's [Badge](https://ant.design/components/badge), re-exported unchanged.
+## Overview
 
-- Extends: antd **Badge** — for inherited props and demos, use the antd MCP (`antd_info Badge`).
-- Always import from '@nanisoft/prism-ui', never from `antd` directly.
+A Badge is a compact label for a short status or category. It renders a
+`<span>` with a filled or outlined surface, and it is not interactive: it
+carries meaning next to something else rather than being a control itself.
 
-_No additional props beyond the antd base component._
+`variant` selects the surface treatment. `default` is the neutral filled badge,
+`secondary` is a quieter fill, `outline` is a bordered badge for a surface that
+already has a fill, and `destructive`, `success` and `warning` carry the three
+status colours.
+
+## Guidelines
+
+### When to use
+
+Use a Badge to mark a row, a card or a heading with one short fact: a status, a
+plan name, a count or a category.
+
+### When not to use
+
+Do not use a Badge as a control. It does not take focus and it does not respond
+to a press; use a Button for an action and a link for navigation.
+
+Do not use a Badge for a sentence or a long phrase. A badge is a label, and a
+label that wraps stops reading as one.
+
+Do not use `destructive`, `success` or `warning` for decoration. Those three
+carry status meaning, and colour alone never carries it for a reader who cannot
+distinguish it.
+
+### Best practices
+
+- Pair the colour with the word. A status is communicated by the label first;
+  the variant reinforces it.
+- Use at most one status Badge per row. Two statuses on one row make the reader
+  decide which is current.
+- Keep the variant to a small, consistent set across a product, so `success`
+  always means the same thing.
+- Place a status Badge beside the name it qualifies, not at the far edge of the
+  row where it can be read as belonging to a neighbour.
+
+### Content guidelines
+
+- Keep a Badge to one or two words.
+- Use sentence case: "Past due", not "Past Due".
+- Prefer a noun or an adjective. "Active" and "Trial" read as states; "Started"
+  reads as an action that already happened.
+- Do not invent a status the product does not have. If the set is unclear, the
+  status vocabulary belongs above the component.
+
+**Badge at each variant, paired with the word that carries the status.**
+
+```tsx
+import { Badge } from '@nanisoft/prism-ui/components/badge'
+
+/** Badge at each variant, paired with the word that carries the status. */
+export default function BadgeDemo() {
+  return (
+    <div className="flex flex-wrap items-center gap-3">
+      <Badge>New</Badge>
+      <Badge variant="secondary">Draft</Badge>
+      <Badge variant="outline">Internal</Badge>
+      <Badge variant="success">Active</Badge>
+      <Badge variant="warning">Past due</Badge>
+      <Badge variant="destructive">Failed</Badge>
+    </div>
+  )
+}
+```
+
+## Props
+
+**`variant`** `"default" | "destructive" | "outline" | "secondary" | "success" | "warning" | null | undefined` · optional · default: —

package/dist/md/components/breadcrumb.md

@@ -1,14 +1,91 @@
 # Breadcrumb
 
-antd Breadcrumb, unchanged — a pass-through re-export. Import from '@nanisoft/prism-ui'.
+The trail of ancestor links that shows where the current page sits.
 
-```ts
-import { Breadcrumb } from '@nanisoft/prism-ui/components';
+```tsx
+import { Breadcrumb, BreadcrumbList, BreadcrumbItem, BreadcrumbLink, BreadcrumbPage, BreadcrumbSeparator } from '@nanisoft/prism-ui/components/breadcrumb'
 ```
 
-`Breadcrumb` is antd's [Breadcrumb](https://ant.design/components/breadcrumb), re-exported unchanged.
+## Overview
 
-- Extends: antd **Breadcrumb** — for inherited props and demos, use the antd MCP (`antd_info Breadcrumb`).
-- Always import from '@nanisoft/prism-ui', never from `antd` directly.
+A Breadcrumb shows the reader where the current page sits in a hierarchy and
+offers a way back up it. It ships as a parent and five parts: `Breadcrumb`,
+`BreadcrumbList`, `BreadcrumbItem`, `BreadcrumbLink`, `BreadcrumbPage` and
+`BreadcrumbSeparator`, all from the same module.
 
-_No additional props beyond the antd base component._
+The parts keep the native list semantics a screen reader expects. `Breadcrumb`
+is a labelled `<nav>`, `BreadcrumbList` is an `<ol>`, and each `BreadcrumbItem`
+is an `<li>`. The last item is a `BreadcrumbPage`, which renders text carrying
+`aria-current="page"` rather than a dead link. Separators are decorative and
+hidden from assistive technology, so the trail reads as a list of destinations
+instead of a list of glyphs.
+
+## Guidelines
+
+### When to use
+
+Use a Breadcrumb when the reader can be more than one step deep: a catalog item
+inside a category, a record inside a project, or a settings page inside an
+account. It answers two questions at once, which section this page belongs to
+and how to leave it.
+
+### When not to use
+
+Do not use a Breadcrumb on a top-level page. A trail with one step restates the
+page title and adds nothing.
+
+Do not use it as the page's primary navigation. A Breadcrumb is a secondary
+affordance; the header or side navigation still owns the main routes.
+
+Do not use it to model a linear flow. A checkout or a wizard moves forward and
+back in a fixed order, so previous and next controls express that better.
+
+### Best practices
+
+- Ship one Breadcrumb per page and place it above the page title.
+- Link every ancestor and render only the current page as plain text with
+  `aria-current="page"`. A link to the page you are already on wastes a stop.
+- Keep the labels the same as the destinations they point at, so the trail
+  matches the navigation the reader came from.
+- Let the trail wrap rather than truncate the middle. A label a reader cannot
+  finish reading is not a label.
+- Use `BreadcrumbSeparator`'s default chevron and leave it decorative. If a
+  separator carries meaning in the copy, it belongs in the link text instead.
+
+**A three-level trail with the current page marked.**
+
+```tsx
+import {
+  Breadcrumb,
+  BreadcrumbItem,
+  BreadcrumbLink,
+  BreadcrumbList,
+  BreadcrumbPage,
+  BreadcrumbSeparator,
+} from '@nanisoft/prism-ui/components/breadcrumb'
+
+/** A three-level trail with the current page marked. */
+export default function BreadcrumbDemo() {
+  return (
+    <Breadcrumb>
+      <BreadcrumbList>
+        <BreadcrumbItem>
+          <BreadcrumbLink href="/">Home</BreadcrumbLink>
+        </BreadcrumbItem>
+        <BreadcrumbSeparator />
+        <BreadcrumbItem>
+          <BreadcrumbLink href="/components">Components</BreadcrumbLink>
+        </BreadcrumbItem>
+        <BreadcrumbSeparator />
+        <BreadcrumbItem>
+          <BreadcrumbPage>Breadcrumb</BreadcrumbPage>
+        </BreadcrumbItem>
+      </BreadcrumbList>
+    </Breadcrumb>
+  )
+}
+```
+
+## Props
+
+> Extends: the native `<nav>` element. No additional Prism-specific props.

package/dist/md/components/button.md

@@ -1,14 +1,97 @@
 # Button
 
-antd Button, unchanged — a pass-through re-export. Import from '@nanisoft/prism-ui'.
+The action control for commands, links and loading states.
 
-```ts
-import { Button } from '@nanisoft/prism-ui/components';
+```tsx
+import { Button } from '@nanisoft/prism-ui/components/button'
 ```
 
-`Button` is antd's [Button](https://ant.design/components/button), re-exported unchanged.
+## Overview
 
-- Extends: antd **Button** — for inherited props and demos, use the antd MCP (`antd_info Button`).
-- Always import from '@nanisoft/prism-ui', never from `antd` directly.
+The Button is the control for an action the reader takes deliberately. It
+renders a native `<button>` and takes the standard React button props plus
+`variant` and `size`, so it behaves like the element it is: it submits, it is
+focusable, and it is reachable by keyboard without extra work.
 
-_No additional props beyond the antd base component._
+The `variant` prop carries the action hierarchy. `default` is the primary
+action, `secondary` and `outline` are supporting actions, `ghost` is for a quiet
+action inside a surface that already carries weight, `destructive` marks an
+action that cannot be undone, and `link` is an action styled as a link for the
+rare case where an action sits inside a sentence.
+
+## Guidelines
+
+### When to use
+
+Use a Button when the reader's intent is to make something happen: submit a
+form, save a change, delete a record, open a dialog, or start a process.
+
+Use one `default` Button per view for the action the view exists to perform.
+Supporting actions take `secondary` or `outline`.
+
+### When not to use
+
+Do not use a Button to navigate. A route change is a link, and a link is
+right-clickable, openable in a new tab, and announced as a link. Use an anchor
+with the link styling instead.
+
+Do not use a `ghost` Button as the only affordance on an empty surface. With no
+surface to sit against, a ghost control reads as text; use `outline`.
+
+Do not use a `destructive` Button for an action that can be undone. Reserve it
+for the action that cannot.
+
+### Best practices
+
+- Keep one `default` Button visible at a time. Two primaries make neither of
+  them primary.
+- Put the primary action last in reading order in a left-to-right layout, after
+  the supporting actions.
+- For a destructive action, put the consequence in the confirmation, not in the
+  button label. The label names the thing, not the warning.
+- A loading or disabled Button should explain why it is unavailable through
+  adjacent text or a tooltip. A disabled control with no reason in reach is a
+  dead end.
+- The coarse-pointer media query grows the target to 44px on touch input
+  automatically. Do not add a second size rule for touch.
+
+### Content guidelines
+
+- Start a label with a verb in the imperative: "Save", "Delete project", "Add member".
+- Use sentence case and no period.
+- Name the object when the action is ambiguous: "Delete project" is better than
+  "Delete".
+- Never use "Click here" or "Submit". The button's own label should state its
+  outcome.
+- Keep a label to three words where possible.
+
+**Buttons at each variant and size.**
+
+```tsx
+import { Button } from '@nanisoft/prism-ui/components/button'
+
+/**
+ * Buttons at each variant and size.
+ *
+ * Self-contained: the only import is from the package, and it has a default
+ * export. The file is the source for the live preview, the copy control and the
+ * corpus.
+ */
+export default function ButtonDemo() {
+  return (
+    <div className="flex flex-wrap items-center gap-3">
+      <Button>Save changes</Button>
+      <Button variant="secondary">Secondary</Button>
+      <Button variant="outline">Cancel</Button>
+      <Button variant="ghost">Ghost</Button>
+      <Button variant="destructive">Delete project</Button>
+      <Button variant="link">Read the guide</Button>
+    </div>
+  )
+}
+```
+
+## Props
+
+**`variant`** `"default" | "destructive" | "outline" | "secondary" | "ghost" | "link" | null | undefined` · optional · default: —
+**`size`** `"default" | "sm" | "lg" | "icon" | null | undefined` · optional · default: —