This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
viberdy.dev
React + Tailwind kits, one design style at a time
A React + Tailwind library organised by design style. Each style is one real site cut into standalone pieces, with source, an AI prompt and a one-line shadcn install. 174 pieces are free, no account. Every piece previews live, Pro included.
I'm the maker of viberdy.dev, so everything below is my own work.
Why styles instead of components: a button, a card and a hero from three libraries don't belong together. Here each style starts as one real site and is cut into standalone pieces, so they fit because they came from the same page. 17 styles, 436 entries.
Free: 174 entries with full source and the AI prompt, one shadcn command, no account. The licence covers client work.
Pro: the other 262, complete-kit installs and future drops. Every Pro entry previews live before you pay.
Launch prices end 31 Oct 23:59 UTC: Pro $19/mo or $93/yr (kept while you stay subscribed), Lifetime $161. New: Agency Lifetime, $499 once for 5 seats.
The hand-written parts: WebGL2 shaders without three.js (raymarched forms, liquid chrome, live dither), soft-body physics for letters, a variable-font fitting solver.
Two questions for you: which style should get more pieces next, and what stops you using a library like this on client work?
About viberdy.dev on Product Hunt
“React + Tailwind kits, one design style at a time”
viberdy.dev was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #557 on the daily leaderboard. A React + Tailwind library organised by design style. Each style is one real site cut into standalone pieces, with source, an AI prompt and a one-line shadcn install. 174 pieces are free, no account. Every piece previews live, Pro included.
On the analytics side, viberdy.dev competes within Design Tools and Web Design — topics that collectively have 273.4k followers on Product Hunt. The dashboard above tracks how viberdy.dev performed against the three products that launched closest to it on the same day.
Who hunted viberdy.dev?
viberdy.dev was hunted by viberdy-dev. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of viberdy.dev including community comment highlights and product details, visit the product overview.
viberdy-dev
I'm the maker of viberdy.dev, so everything below is my own work.
Why styles instead of components: a button, a card and a hero from three libraries don't belong together. Here each style starts as one real site and is cut into standalone pieces, so they fit because they came from the same page. 17 styles, 436 entries.
Free: 174 entries with full source and the AI prompt, one shadcn command, no account. The licence covers client work.
Pro: the other 262, complete-kit installs and future drops. Every Pro entry previews live before you pay.
Launch prices end 31 Oct 23:59 UTC: Pro $19/mo or $93/yr (kept while you stay subscribed), Lifetime $161. New: Agency Lifetime, $499 once for 5 seats.
The hand-written parts: WebGL2 shaders without three.js (raymarched forms, liquid chrome, live dither), soft-body physics for letters, a variable-font fitting solver.
Two questions for you: which style should get more pieces next, and what stops you using a library like this on client work?