ibelick/prompt-kit

Core building blocks for AI apps. High-quality, accessible, and customizable components for AI interfaces.

View on GitHub ↗Jump to charts ↓

ibelick/prompt-kit has 3k+ stars and 150+ forks on GitHub, is written in TypeScript, and was last pushed on Sep 28, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 23 minutes ago
Added to GitGenius on September 22nd, 2026
Created on February 10th, 2025
Open Issues & Pull Requests: 10 (+0)
GitHub issues: Enabled
Number of forks: 168
Total Stargazers: 3,125 (+0)
Total Subscribers: 15 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.4 days
Mean response time: 17.4 days
90th percentile: 38.9 days
Tracked items: 30

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 286 days
Stale 30+ days: 8
Stale 90+ days: 8

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • help wanted (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Prompt Kit is a React component library that provides building blocks for constructing AI application interfaces.

The tool addresses the need for pre-built, accessible UI components tailored to AI workflows. Rather than assembling generic interface elements, developers can use components designed specifically for common AI interaction patterns. The library is built on React and integrates with Tailwind CSS and shadcn/ui, allowing components to be customized through standard styling approaches.

Prompt Kit suits teams building AI-powered applications who want to accelerate interface development without sacrificing accessibility or visual customization. It works well for projects using Next.js and the React ecosystem where Tailwind CSS is already part of the stack. The component-based architecture means developers can adopt individual pieces rather than committing to a complete design system, making it flexible for projects at different stages of maturity.

Development activity shows consistent engagement with the codebase. The project maintains an active commit history with regular updates to components and documentation. Pull requests are reviewed and merged at a steady pace, indicating ongoing maintenance and responsiveness to contributions. The repository demonstrates attention to code quality through its use of TypeScript and adherence to accessibility standards in component design.