DOMAIN:FRONTEND:THOUGHT_LEADERS¶
OWNER: floris (Team Alpha), floor (Team Beta)
UPDATED: 2026-03-24
PURPOSE: key people, resources, and references for frontend agents
USAGE: consult when seeking authoritative patterns or staying current
PEOPLE¶
LEE_ROBINSON¶
ROLE: VP of Developer Experience at Vercel
AUTHORITY_ON: Next.js, App Router, Server Components, deployment, caching
WHY_MATTERS: defines Next.js direction. His content reflects official Vercel thinking.
KEY_CONTENT:
- YouTube channel — Next.js deep dives, live coding, architecture decisions
- leerob.com — blog posts on Next.js patterns, performance, developer experience
- X/Twitter: @leeerob
FOLLOW_FOR: Next.js release announcements, caching strategy changes, App Router best practices
NOTABLE: championed "React Server Components by default" philosophy
DAN_ABRAMOV¶
ROLE: formerly React core team (Meta), now independent
AUTHORITY_ON: React mental models, component composition, hooks philosophy, Server Components theory
WHY_MATTERS: shaped React's core API design philosophy. His writings define how to think about React.
KEY_CONTENT:
- overreacted.io — deep essays on React internals, composition, rendering
- "A Complete Guide to useEffect" — canonical reference for effect cleanup
- "Before You memo()" — canonical reference for when memoization is unnecessary
- "The Two Reacts" — influential essay on Server vs Client component mental model
FOLLOW_FOR: fundamental React thinking. NOT for framework-specific tutorials.
NOTE: no longer at Meta. Insights remain foundational but may not reflect latest React team decisions.
KENT_C_DODDS¶
ROLE: independent educator, creator of Testing Library, Remix co-founder
AUTHORITY_ON: React testing, component patterns, forms, accessibility in React
WHY_MATTERS: Testing Library (React Testing Library) is the standard. His testing philosophy shaped the ecosystem.
KEY_CONTENT:
- kentcdodds.com/blog — testing strategies, React patterns, component design
- Epic React (epicreact.dev) — comprehensive React course
- Testing Library docs — user-centric testing approach
- "Write tests. Not too many. Mostly integration." — canonical testing philosophy
FOLLOW_FOR: testing strategy, component design patterns, React best practices
KEY_PRINCIPLE: "The more your tests resemble the way your software is used, the more confidence they can give you."
ADAM_WATHAN¶
ROLE: creator of Tailwind CSS, founder of Tailwind Labs
AUTHORITY_ON: utility-first CSS, Tailwind architecture, Headless UI
WHY_MATTERS: defines Tailwind direction, responsive patterns, design token strategy
KEY_CONTENT:
- tailwindcss.com/blog — Tailwind releases, design philosophy
- "CSS Utility Classes and 'Separation of Concerns'" — canonical utility-first argument
- YouTube — Tailwind live streams, UI builds, design process
FOLLOW_FOR: Tailwind CSS new features, migration guides, design system patterns
NOTABLE: Tailwind v4 was a ground-up rewrite. His blog posts explain every decision.
SHADCN (SHADCN)¶
ROLE: creator of shadcn/ui, works at Vercel
REAL_NAME: shadcn (publicly known by this handle)
AUTHORITY_ON: component library architecture, Radix + Tailwind integration, theming
WHY_MATTERS: shadcn/ui is GE's component library foundation. Understanding his decisions helps customize correctly.
KEY_CONTENT:
- ui.shadcn.com — component library, docs, examples, blocks
- X/Twitter: @shadcn
- GitHub: shadcn-ui/ui — source code, discussions
FOLLOW_FOR: new component releases, Tailwind v4 migration, theming approaches
KEY_PRINCIPLE: "copy and paste, not dependency" — own your components
NOTABLE: data-slot attribute pattern (v4) for targeted styling without brittle selectors
RYAN_FLORENCE¶
ROLE: co-creator of React Router, co-founder of Remix (acquired by Shopify)
AUTHORITY_ON: routing, data loading, progressive enhancement, form handling
WHY_MATTERS: React Router v7 merged with Remix. His ideas influence Next.js through competition.
KEY_CONTENT:
- remix.run/blog — routing philosophy, progressive enhancement, data mutations
- Conference talks on "The Web's Next Transition"
FOLLOW_FOR: alternative perspectives on data loading, streaming, progressive enhancement
NOTE: Remix and Next.js compete but cross-pollinate ideas. Understanding both helps write better Next.js code.
ADDITIONAL_EXPERTS¶
THEO_BROWNE (theo.gg / t3.gg)¶
AUTHORITY_ON: TypeScript full-stack patterns, T3 stack (Next.js + tRPC + Prisma), developer experience
FOLLOW_FOR: practical opinions on Next.js architecture, library selection
CAVEAT: strong opinions. Evaluate claims against your project context.
JOSH_COMEAU (joshwcomeau.com)¶
AUTHORITY_ON: CSS deep dives, animations, visual explanations, React mental models
FOLLOW_FOR: CSS layout/animation understanding, interactive visual tutorials
NOTABLE: "CSS for JavaScript Developers" course — essential for frontend developers
WES_BOS (wesbos.com)¶
AUTHORITY_ON: JavaScript/React/Node practical tutorials, full-stack patterns
FOLLOW_FOR: hands-on tutorials, real-world project patterns
MARK_ERIKSON¶
AUTHORITY_ON: Redux, state management history, React ecosystem analysis
FOLLOW_FOR: state management comparisons, when to use what, Redux Toolkit patterns
NOTABLE: "State of React State Management" talks — excellent overview of all options
STEVE_SEWELL (Builder.io)¶
AUTHORITY_ON: performance optimization, framework benchmarks, visual builders
FOLLOW_FOR: framework comparison data, performance best practices
KEY_BLOGS_AND_SITES¶
| Resource | URL | Focus |
|---|---|---|
| Next.js Docs | nextjs.org/docs | Official framework documentation |
| React Docs | react.dev | Official React documentation |
| Tailwind CSS Docs | tailwindcss.com/docs | Official Tailwind documentation |
| shadcn/ui Docs | ui.shadcn.com | Component library documentation |
| Vercel Blog | vercel.com/blog | Framework updates, deployment |
| Patterns.dev | patterns.dev | React/JS design patterns with visuals |
| web.dev | web.dev | Google's web performance/accessibility guides |
| Smashing Magazine | smashingmagazine.com | In-depth frontend articles |
| CSS Tricks | css-tricks.com | CSS patterns, guides, techniques |
KEY_REPOSITORIES¶
| Repository | Purpose | Why Follow |
|---|---|---|
| vercel/next.js | Next.js framework | Issues reveal common problems. Discussions have official answers. |
| facebook/react | React core | RFCs reveal future direction. |
| shadcn-ui/ui | shadcn/ui | New components, Tailwind v4 migration. |
| tailwindlabs/tailwindcss | Tailwind CSS | Releases, breaking changes. |
| radix-ui/primitives | Radix UI | Accessibility patterns, new primitives. |
| testing-library/react | React Testing Library | Testing patterns, query priorities. |
| TanStack/query | TanStack Query | Server state management. |
| 47ng/nuqs | nuqs | URL state management. |
| pmndrs/zustand | Zustand | Simple global state. |
| pmndrs/jotai | Jotai | Atomic state. |
CONFERENCES¶
| Conference | Focus | Location | Timing |
|---|---|---|---|
| React Summit | React ecosystem | Amsterdam + remote | June |
| Next.js Conf | Next.js specific | Online (Vercel) | October |
| React Advanced | Deep React topics | London | October |
| Tailwind Connect | Tailwind ecosystem | Online | Varies |
| React Day Berlin | React in Europe | Berlin | December |
| JSNation | JavaScript broad | Amsterdam | June |
| Frontend Unite | Frontend broad | Utrecht, NL | Spring |
NOTE: prefer European conferences for timezone and travel convenience.
NEWSLETTERS¶
| Newsletter | Frequency | Focus |
|---|---|---|
| This Week in React | Weekly | React ecosystem news, releases, articles |
| Bytes.dev | Twice weekly | JavaScript/frontend humor + news |
| Frontend Focus | Weekly | Broad frontend (CSS, perf, browser APIs) |
| Tailwind Weekly | Weekly | Tailwind CSS tips, components, tools |
| Smashing Newsletter | Weekly | Design + frontend development |
DECISION_FRAMEWORK¶
WHEN_CONFLICTING_ADVICE:
1. Official docs (Next.js, React, Tailwind) take precedence over blog posts
2. Lee Robinson/Vercel blog = quasi-official Next.js guidance
3. Dan Abramov's principles = quasi-official React thinking
4. Kent C. Dodds' testing philosophy = standard approach
5. Adam Wathan's Tailwind patterns = official Tailwind guidance
6. Blog posts from 2023 or earlier may be outdated — check against current docs
7. If still conflicting, prefer the simpler approach (less abstraction, less magic)
WHEN_EVALUATING_NEW_PATTERNS:
- is it in the official docs?
- is it endorsed by a core maintainer?
- does it have production usage at scale?
- does it simplify or complicate our codebase?
- does it have good TypeScript support?
- does it add a dependency we cannot afford?