HITL Kit

What this is

HITL Kit is three artifacts shipped as one project: a perspective paper arguing that 95% of enterprise AI pilots fail because we evaluate systems for autonomous completion when deployment demands human-AI collaboration; a component library of eleven HITL primitives that installs into any shadcn/ui project via one CLI command; and a shadcn-compatible registry I built and host at hitlkit.dev. The argument, the implementation, and the distribution, in one place.

What I actually built

• An AI Measurement Problem (paper). A perspective piece synthesizing benchmark saturation, cognitive neuroscience, uncertainty quantification, and enterprise deployment data into the Assist-Not-Complete paradigm. Rendered live on the site from a single markdown source, with a sticky table of contents and editorial typography.
• Eleven HITL primitives. Interrupt Card, Subagent Status, MiniTrace, AI Generation Scale, Context Chips, QA Flow, Writing Agent, Research Agent, Batch Queue, Search Result Card, Approve/Reject Row. Each one is the physical embodiment of a specific claim from the paper.
• Shadcn registry with fifteen endpoints. registry.json, a build pipeline (pnpm registry:build), and fifteen JSON manifests served at hitlkit.dev/r/*.json. Transitive dependencies resolve correctly. End-to-end tested: anyone on the open internet can run npx shadcn@latest add https://www.hitlkit.dev/r/hitl-card.json and get a working install.
• The site itself. Next.js 16, Tailwind CSS v4, TypeScript, React 19. Dark-mode-first with Geist and JetBrains Mono. Four routes: a landing that frames the thesis, a live component showcase, a markdown paper renderer, and a registry-install reference page with copy-button commands for every primitive.
• A taxonomy, not a grab-bag. Every primitive traces to a named research claim: MiniTrace instantiates the supporting-facts requirement from HotpotQA (Yang 2018), the AI Generation Scale operationalises the scaffolding principle from Dhillon 2024, the Interrupt Card is the agency-preservation boundary from §3.1. The library is the paper, made clickable.

Why it's unusual

Most open-source AI UI kits are commodities: chat bubbles, tool-call cards, maybe a markdown renderer. HITL Kit couples a research argument with an installable implementation. I wrote the paper that says enterprise AI fails because it measures the wrong thing, then built the component library that makes the alternative buildable, then set up the shadcn registry so other teams can drop those components into their own agentic products. Positioning, authorship, engineering, and distribution are all one piece of work. The measurement critique is not separate from the UI library. The UI library is the critique made useful.

How I describe the skill set

Technical writing and research synthesis, design systems, component library engineering, shadcn CLI and registry authoring, Next.js App Router, Tailwind CSS v4, TypeScript, React 19, open-source product positioning, agentic UI pattern design, human-AI collaboration research, and the ability to connect all of those into one shippable artifact.