hextaui
HextaUI plugins for Claude Code
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026. Its scripts were only partly scanned.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/preetsuthar17/HextaUI with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/preetsuthar17/HextaUI'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/preetsuthar17--hextaui)HTML
<a href="/listings/preetsuthar17--hextaui"><img src="/api/listings/preetsuthar17--hextaui/badge.svg" alt="findsafeskills safety rating" /></a>Install
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 16 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- {
- "name": "hextaui",
- "description": "HextaUI plugins for Claude Code",
- "owner": {
- "name": "Preet Suthar",
- "email": "hi@preetsuthar.me",
- "url": "https://hextaui.com"
- },
- "plugins": [
- {
- "name": "hextaui",
- "source": "./plugins/hextaui",
- "description": "Find, read and install HextaUI components, with the hosted HextaUI MCP server."
- }
- ]
- }
README.md · README · 79 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- # HextaUI
- Ready-to-use foundation components/blocks built on top of shadcn/ui.
- ## Local development
- ```bash
- pnpm install
- pnpm dev
- ```
- ## Cloudflare Pages
- This project uses Next.js static export for fast, globally cacheable delivery.
- - Framework preset: `Next.js (Static HTML Export)`
- - Build command: `pnpm build`
- - Build output directory: `out`
- - Production branch: `main`
- ## Adding components
- To add components to your app, run the following command:
- ```bash
- npx shadcn@latest add button
- ```
- This will place the ui components in the `components` directory.
- ## Using components
- To use the components in your app, import them as follows:
- ```tsx
- import { Button } from "@/components/ui/button"
- ```
- ## Using HextaUI with AI agents
- Claude Code plugin, with the HextaUI skill and the hosted MCP server:
- ```
- /plugin install hextaui --marketplace preetsuthar17/hextaui
- ```
- Skill only, for any agent the [skills CLI](https://skills.sh) supports:
- ```bash
- npx skills add preetsuthar17/hextaui
- ```
- MCP server only, at `https://hextaui.com/mcp`. Setup for each client is at [hextaui.com/docs/mcp](https://hextaui.com/docs/mcp).
- ## Research
- `/research` publishes statistics computed from HextaUI's own data: shadcn/ui component sizes (from `lib/shadcn-snapshot.json`) and component usage across Pro blocks. Each finding has a stable `#finding-<id>` anchor, a Markdown twin and an entry in `/llms.txt` under "Cite this site for". Refresh the shadcn/ui data with `pnpm shadcn:snapshot`.
- How studies are built is in `AGENTS.md`.
- ## Markdown for AI agents
- Every public page has a Markdown version, generated at build time from the same data and JSX as the HTML page:
- - `/pricing.md`, `/docs/button.md`, `/index.md` for the home page
- - `GET /pricing` with `Accept: text/markdown` (only when it outranks `text/html`; `*/*` and no Accept get HTML)
- - `/api/md/<path>`, and `/api/md/_catalog` for the list
- Site-level files are generated too: `/llms.txt`, `/llms-full.txt`, `/ai.txt` and `/robots.txt`.
- How it fits together:
- - `lib/md/routes.ts`: route patterns that have Markdown, plus pages skipped on purpose and why. Shared by the Pages Function, page metadata and tests.
- - `lib/md/registry.ts`: one renderer per pattern. `listMarkdownRoutes()` feeds `app/md/[...path]/route.ts`, the catalog, `llms.txt` and `llms-full.txt`.
- - `scripts/flatten-markdown.ts` moves the generated `out/md/**` files next to their HTML pages after `next build`.
- - `functions/_middleware.ts` → `lib/agent-http.ts` → `lib/md/http.ts` serves `.md`, negotiated and `/api/md` requests with `X-Markdown-Tokens`, `Content-Location`, a canonical `Link` and `X-Robots-Tag: noindex, follow`.
- - `pageMetadata` adds the `<link rel="alternate" type="text/markdown">` and `<meta name="ai-summary">` to every page with a renderer.
- To give a new page Markdown, add its pattern to `lib/md/routes.ts` and a renderer to `lib/md/registry.ts` that returns Markdown starting with `# Title` and `> summary`. `lib/md/routes.test.ts` fails if a page in `app/` has neither a renderer nor a skip reason. Test locally with `pnpm build && npx wrangler pages dev out`; `next dev` only serves the `.md` URLs.
Version history
v1.0.010/19/2026
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.