UI, design system, web framework practitioners · 12 rooms · ranked by yield
Frontend and product-builder rooms. Ranked by deal-flow yield.
Next.js Discord, Reactiflux, Tailwind, shadcn/ui, the surface where frontend-org repos surface first.
Frontend-framework and design-system rooms. Half our dataset's frontend-org repos surface here before they hit GitHub trending. This is the highest first-mention density among non-AI builder rooms.
Yield story
Primary surfaces are Next.js Discord, Reactiflux, Tailwind Discord, and shadcn/ui Discussions, four rooms with the highest first-mention density for frontend-org repos.
Cadence
Weekly read on the four primary surfaces.
Caveat
Frontend rooms are heavily moderated against link-drops. Engagement is reactive (technical Q&A) only.
Yield breakdown · 12 rooms
5
Primary
Direct deal-flow surface. Multiple repos we surface first showed up here.
5
Secondary
Adjacent. Signals overlap, but rarely the first-mention surface.
2
Ambient
Culture / reading list. Useful for framing, not for sourcing.
Engagement status
0
Engage
9
Watch
0
Hold
3
Read
0
Blocked
The ranked roster
12 rooms, sorted by yield tier, numbered, linked.
Primary first, then secondary, then ambient. Hand-authored order within each tier, top of tier = highest attention density.
- 1.
Next.js community. Vercel-orbit orgs surface here first.
- 2.
React-community Discord. Broad frontend-org signal.
- 3.
Tailwind-ecosystem community. Component-lib-to-startup pipeline.
- 4.
shadcn/ui Discussions. UI-primitive adoption signal.
- 5.
Next.js community. Vercel-orbit orgs surface here first.
- 6.
Svelte / SvelteKit community.
- 7.
Vue / Nuxt community. Adjacent frontend org signal.
- 8.
Mantine UI-kit community. Niche component-lib signal.
- 9.
React community, half of our dataset's frontend orgs land here.
- 10.
Frontend-leaning practitioner audience.
- 11.
Figma-power-user / community Slack. Designer crossover.
- 12.
Design-practitioner Slack. Ambient design-side signal.
Frequently asked
Four questions about this list.
- What is the "deal-flow yield" of a community?
- Yield is a three-tier rating, primary, secondary, ambient, describing how often a community has been the first public surface where a repo or founder we now surface inside the product appeared. Primary means multiple deals trace back to the room; ambient means the room is read for framing, not sourcing.
- Why is frontend and product-builder rooms indexed by type instead of by platform?
- The platform map at /voices already covers per-platform rosters (Reddit-100, HN-100, X-100). Indexing by type cuts the same audience differently, a Cursor user in a Cursor Discord is a different deal-flow signal than the same user in a CNCF channel, even though both are on Discord.
- Do we engage in every community on this page?
- No. Each community is tagged with an engagement status (engage / watch / hold / read / blocked). The default for most rooms is "watch" or "read", we listen but do not post. The "engage" tag is reserved for a small number of rooms where comment-only engagement on technical Q&A is allowed by both the room rules and our anonymity rule.
- Are the individuals inside these communities listed anywhere?
- No. The anonymity rule that governs the entire site applies here: we name communities, not individuals. The specific founders, maintainers, and contributors we surface live inside the paid product, that is the buyer's edge.
Where the deal-flow signal actually lives
Rooms tell us where to look. Telemetry tells us what to fund.
Reading frontend and product-builder roomsdoesn’t produce a deal. It sharpens the question we ask the GitHub-side telemetry. The actual deal-flow signal lives at /predicted, /firstlook, and the rest of the signal stack below.
Frontend and product-builder rooms roster regenerated quarterly. Status flags update weekly. Companion platform map at /voices. Master mixed list at /target-list.