frontend▌

You are a frontend developer documenting what data you need from backend. You describe the what, not the how. Backend owns implementation details.

Modern React component patterns for building scalable, maintainable UI libraries. \n \n Covers five core patterns: props API design with TypeScript, composition, render props, custom hooks for logic separation, and performance optimization with React.memo and useMemo \n Includes compound components, polymorphic components, and context-based state sharing for flexible, reusable architectures \n Enforces single responsibility, accessibility standards (aria-*, role, tabindex), and prohibits prop dr

Battle-tested utilities for Convex backends covering relationships, authentication, filtering, sessions, and data migrations. \n \n Relationship helpers ( getOneFrom , getManyFrom , getManyVia ) simplify loading related data across tables with type safety \n Custom functions provide TypeScript-based data protection and access control as an alternative to row-level security, with automatic auth injection and role-based access patterns \n Additional utilities include filtering for complex logic, s

Best practices for writing effective AI video generation prompts via inference.sh.

$23

React useEffect best practices guide covering when to use Effects and superior alternatives. \n \n Teaches the escape-hatch nature of Effects: use only for synchronizing with external systems, not for derived state, expensive calculations, or user event responses \n Provides a decision tree and quick-reference table mapping common situations (data fetching, state derivation, prop changes) to the correct React pattern \n Covers when NOT to use Effects: transforming data for render, handling user

Essential Vue Composition utilities for state, sensors, browser APIs, and common patterns. \n \n 200+ composables across 12 categories including state persistence, mouse tracking, keyboard input, network requests, animations, and array operations \n Auto-imports in Nuxt via @vueuse/nuxt module; manual imports required for Vue 3 standalone \n SSR-safe composables return sensible defaults on server; use isClient guard or onMounted wrapper for browser-only APIs \n Common patterns include useLocalSt

Provides complete frontend development expertise for building production-ready web applications with modern frameworks (React, Vue, Next.js), comprehensive tooling setup, state management patterns, testing infrastructure, and performance optimization strategies.

A 3-phase workflow for extracting, structuring, and applying design identity across three dimensions:

Automated UI code review against Vercel's Web Interface Guidelines. \n \n Fetches the latest guidelines from the official Vercel repository before each review to ensure current rule compliance \n Analyzes React, Vue, Svelte, HTML, CSS, and JavaScript/TypeScript files against all fetched rules \n Reports violations in file:line format with actionable feedback on how to fix each issue \n Supports file paths and glob patterns for flexible scope selection across projects \n