ShieldCheckVerified against your real project types

Type-check the code in your Markdown

Kiira runs the TypeScript and JavaScript code fences in your docs through the compiler against your real project API, reporting errors on the exact Markdown line — in your editor, on the CLI, and in CI.

terminal
$ pnpm add -D kiira
$ pnpm kiira init
$ pnpm kiira check
✓ Kiira found no errors in 12 files.

Watch Kiira catch a bug

A broken snippet goes in, runs through the real TypeScript compiler, and comes back with the errors flagged on the exact line — the same check you get in your editor, on the CLI, and in CI.

FileTextREADME.mdunchecked

Usage

Call the hook and send a message:

import { useChat } from "@tanstack/ai/react"
 
const chat = useChat({ onMessge: reset })
chat.sendMessages("hi")

It returns the chat instance.

Kiira
Kiira
FileTextREADME.mdTriangleAlert 2 errors

Usage

Call the hook and send a message:

import { useChat } from "@tanstack/ai/react"
 
const chat = useChat({ onMessge: reset })
chat.sendMessages("hi")

It returns the chat instance.

TriangleAlertTS2353 · line 3 — no known property onMessge; did you mean onMessage?
TriangleAlertTS2551 · line 4 — sendMessages does not exist; did you mean sendMessage?

Everything that breaks a copy-pasted example

Docs rot quietly — and agents hallucinate APIs with total confidence. Kiira fails the check the moment an example stops matching your real types.

Xinvalid imports
Xmissing exports
Xwrong package subpaths
Xwrong prop / option names
Xhallucinated APIs
Xnon-copy-pasteable examples

One engine, every surface

The same check powers your editor, the command line, and CI — so "it passes locally" means "it passes in the PR."

Zap

kiira-core

the check engine

ChevronRight
Kiira
ChevronRight
Code

CLI

kiira check

VS Code

live diagnostics

Github

GitHub Action

PR annotations