Skip to content
kindui
Esc

31 results

Theme

Delightful AI interfaces and charts,ready for .

Browse components

Copy prompt

Pick a library, then paste this prompt into your coding agent.

Library
Set up Kind UI's Agent UI in this project.

1. If the project has no components.json, run: npx shadcn@latest init
2. Add the @kind-ui registry to components.json:
   "registries": { "@kind-ui": "https://kindui.dev/r/{name}.json" }
3. Add a component with: npx shadcn@latest add @kind-ui/conversation
   For Web Components, add the -web version, for example @kind-ui/conversation-web.
4. The CLI writes an AGENTS.md next to the components. Follow it, and read https://kindui.dev/docs/agent-ui/llms.txt before using a component.

When you're done, ask me what I'd like to build.
Library
Installation option
npm install @kind-ui/agent-ui

01 · Agent UI

Agent-ready UI, built on .

Messages, the steps an agent took, the sources it cited and the code it ran, answers that stream in, and a composer to reply. Your agent can read every component and use its controls, without screenshots. Works in React, Vue, Svelte, Solid and Web Components.

npx shadcn@latest add @kind-ui/
Read the Agent UI docs

Live components

  • export-log.txt18 kB
The nightly billing export keeps failing. Can you fix it?

    Conversation

    The nightly export failed again. Can you take a look?

    Sure. Which job is it, and when did it last succeed?

    billing-export. It last succeeded on Tuesday.

    Since Wednesday, every run has stopped after 30 seconds waiting on the reports service. The service was slow, not down: its median response time went from 4 to 41 seconds.

    So we just raise the timeout?

    Raising it would get tonight's run through, but the job would still fail on the next slow night. I'd retry each page with backoff, cap the attempts at five, and alert when a run takes longer than an hour.

    Do that, and open a pull request.

    Done. The pull request adds the retry and the alert, with a test that replays Wednesday's responses.

    Plan

    1 of 4 steps
    1. Find every session read and write
    2. Add a Redis session storeBehind a flag, so both stores run side by side.
    3. Copy the live sessions
    4. Remove the old store

    Message

    How should the client handle a flaky upstream?
    Retry with exponential backoff, and cap the number of attempts.
    1 of 2

    Reasoning

    Two of the flights leave before 7 a.m., so rank the third one first.

    Checkpoint

    CheckpointBefore editing auth.ts

    Markdown

    Retry with backoff

    Wait a little longer after each failure, and give up after a few tries. Retry only idempotent requests.

    ts
    await sleep(2 ** attempt * 250);
    AttemptDelay
    1250 ms
    2500 ms
    31 s

    Read the Retry-After header first when the server sends one.

    Code Block

    ts
    async function retry<T>(run: () => Promise<T>, tries = 4): Promise<T> {  for (let attempt = 0; ; attempt++) {    try {      return await run();    } catch (error) {      if (attempt + 1 >= tries) throw error;      await sleep(2 ** attempt * 250);    }  }}

    Attachments

    • retry-spec.pdf482 kB
    • notes.md812 byte
    • heap.zipFile is too large

    Tool

    InputPartial
    {  "filter": "client"}
    InputPartial
    {  "branch": "old-retry"}
    Waiting for approval

    Question

    Where should it deploy? Required
    Which checks should run first?
    Anything the reviewers should know?

    Terminal

    npm test
    > app@1.0.0 test
    ✓ format.test.ts (12 tests)
    ✓ parse.test.ts (9 tests)
    ✗ cache.test.ts (1 failed)
    Expected "hit", received "miss"
    Tests: 1 failed, 21 passed, 22 total

    Inline Citation

    The API allows 5,000 requests an hour for a signed-in user . When you hit the limit, wait as long as the Retry-After header says before trying again .

    File Tree

    src
    lib
    format.ts
    parse.ts
    index.ts
    package.json
    README.md

    Test Results

    auth.test.ts
    logs in with a password
    locks the account after five attempts
    1. Context.<anonymous>test/auth.test.ts:58:31
    signs in with SSO
    ReasoningToolPlanTaskSubagentConfirmationQuestionModel SelectorSourcesInline CitationTerminalFile Treeand more

    02 · Charts

    Interactive charts, built on Recharts and Motion.

    Hover a bar to read it, or tab in and use the arrow keys. Tap a legend to focus one series. Bar, line, pie, radar, sankey and more.

    npx shadcn@latest add @kind-ui/
    Read the Charts docs

    Orders this week

    665

    Daily activity

    Stand
    9 hours
    Exercise
    38 min
    Move
    410 kcal

    Leads by channel

    351

    Trials and paid plans

    Paid in June

    260

    Focus the chart and use the arrow keys to inspect values. Press Escape to dismiss the tooltip.

    AreaComboRadarRadialScatterHeatmapWaterfallSankeyHistogramBox plotand more

    Use them together.

    Ask a question, get a chart back. Both libraries share the same colors and type, so they match with no extra styling.

    How did orders do this week?
    Thinking

    What every library includes.

    Accessible

    Use a keyboard or a screen reader. Every component has labels and a visible focus ring.

    Composable

    Each component is made of small parts you can rearrange, restyle or leave out.

    Yours to own

    Install the package from npm, or copy a component's source into your project with shadcn.

    Calm motion

    Animations stay short, and they stop when someone turns on reduced motion.

    Light and dark

    Colors come from CSS variables, so each theme works without extra setup.

    Ready for agents

    Agent skills and an llms.txt file show your coding agent how to use each library.

    FAQ