Junior Garcia
ebb2517bf6
* docs: add 12 copy-edited blog posts for SEO and AI discoverability De-templated repetitive boilerplate across all posts, rewrote tutorial openings with pain-point hooks, and made "Why HeroUI" closing sections contextually unique per article. Removed 4 duplicate/unpolished posts (two dashboard duplicates, e-commerce, landing page, SaaS app tutorials) to keep the initial launch set focused and high-quality. Made-with: Cursor * feat(docs): add SEO, blog, JSON-LD, and AI discoverability improvements Adds blog pages, JSON-LD structured data, enhanced metadata, sitemap normalization, component/example counts, why-heroui page, AI prompts, and SEO-optimized README. Made-with: Cursor * feat(docs): blog content rebalancing, SEO improvements, and blog UI polish - Rebalance all 7 comparison/listicle blog posts: remove self-undermining trade-offs, star count comparisons, and competitor endorsements; replace with HeroUI-forward conclusions and brief "when X might work" sections - Optimize blog post descriptions using Ahrefs keyword data - Add BreadcrumbList JSON-LD to blog post pages - Add OG images to Chakra and Mantine comparison posts - Extract PostCard into shared component with image support and onError fallback - Redesign blog post header: Linear-inspired layout with title, hero image, author name + date below image, avatar on hover - Add DocsImage support to blog posts with light/dark mode switching - Add darkImage frontmatter field to blog data layer - Fix mobile overflow on blog post pages - Add hero images to "Why Choose HeroUI" and "12 Best" posts - Enhance "Why Choose HeroUI" post: add YC backing, community metrics, "Ready in Two Steps" section, AGENTS.md docs, theme builder link - Remove "Updated April 2026" from all posts - Sort related posts by newest first - Truncate card titles to 2 lines - Fix Draft badge visibility on light backgrounds Co-authored-by: Cursor <cursoragent@cursor.com> * fix(docs): wrap BlogContent in Suspense boundary for useSearchParams Next.js requires useSearchParams (used by nuqs) to be wrapped in a Suspense boundary during static generation. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(blog): publish 12 best react UI component libraries post Remove draft state so the post is publicly visible. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
2.0 KiB
HeroUI v3 — AI Integration Prompt Packs
System prompts that teach AI code-generation tools to produce correct, idiomatic HeroUI v3 code.
What's in this directory
| File | Purpose |
|---|---|
heroui-system-prompt.md |
Universal prompt — works with any LLM or AI coding tool (Claude, ChatGPT, Cursor, Copilot, etc.) |
v0-heroui.md |
Tailored for v0.dev — emphasizes Next.js App Router, RSC patterns, and Tailwind v4 |
bolt-heroui.md |
Tailored for bolt.new / StackBlitz — includes full Vite setup and runnable single-file examples |
These prompts also work well with Lovable, Replit Agent, Windsurf, and similar AI-powered code generation platforms.
How to use
v0.dev
Paste the contents of v0-heroui.md into v0's system instructions or prepend it to your prompt.
bolt.new / StackBlitz
Paste the contents of bolt-heroui.md at the start of your prompt when creating a new project. It includes the full Vite + Tailwind v4 setup so bolt can scaffold the project correctly.
Cursor / Claude / ChatGPT / Copilot
Use heroui-system-prompt.md as a custom instruction, system prompt, or .cursorrules file. It gives the AI a complete reference of HeroUI v3 components and patterns.
Any other tool
The universal heroui-system-prompt.md works with any tool that accepts system-level instructions.
Richer integrations
For deeper integration beyond system prompts:
- MCP Server — The HeroUI MCP server provides real-time component docs, source code, and theme tokens to AI agents. See the
@heroui/mcppackage. - llms.txt — Full-context documentation following the llms.txt standard, available at heroui.com/llms.txt.
Contributing
When updating these prompts, verify that the component names, APIs, and import patterns match the actual v3 source code in this repo. Run a quick check against the component docs in apps/docs/content/docs/react/components/ to catch any drift.