frontend▌

Apply these rules when writing or reviewing Next.js code.

Framework-based guidance for hiring and scaling sales teams from zero to repeatable revenue. \n \n Emphasizes proving founder-led repeatability (50-100 at-bats at 15-25% win rate) before hiring any salespeople \n Recommends always hiring sales reps in pairs to validate process and create performance baselines, not single hires \n Matches sales archetypes (hunters for outbound, growers for inbound/PLG) to your specific motion and buyer profile \n Delays VP of Sales hires until you have two reps c

$22

Provide comprehensive guidance for choosing between Server Components and Client Components in Next.js App Router, including cookie/header access, searchParams handling, pathname routing, and React's 'use' API for promise unwrapping.

Exhaustive React API research from authoritative sources, not training knowledge. \n \n Spawns six parallel research agents to systematically search React's test files, source code, git history, PRs, issues, and type definitions \n Enforces skepticism mandate: treats source material as sole authority and flags discrepancies between findings and common understanding \n Generates documented research with exact file paths, line numbers, and source links for every claim, code example, and warning \n

Build a compelling promotion case by diagnosing blockers and framing advancement as solving company problems. \n \n Diagnose the situation by understanding current role, target role, manager relationship, and identifying whether blockers are visibility, advocacy, role availability, or skill gaps \n Core principle: perform at the next level before requesting the title; promotions recognize readiness, they don't develop it \n Frame promotion conversations around business impact and company needs,

Data-driven persona generation, journey mapping, and usability testing frameworks for user research and design validation. \n \n Generates research-backed personas from user data and interviews, with behavior pattern analysis, psychographic extraction, and confidence scoring \n Supports customer journey mapping, usability testing frameworks, and research synthesis to inform design decisions \n Includes design validation methods and scenario generation tied directly to persona insights \n

Styling guidelines for the Mastra Playground UI, containing 5 rules across 3 categories. Rules are prioritized by impact to guide automated refactoring and code generation. These rules ensure design system consistency, prevent token drift, and maintain component library integrity.

Convert JSON specs into React component trees with type-safe props and state management. \n \n Define catalogs with Zod schemas for component props, then implement components with automatic type safety and validation \n Built-in state management via StateProvider with two-way binding ( $bindState ), conditional rendering, and external store integration (Redux, Zustand, XState) \n Event system with action dispatching, state watchers, and four built-in actions (setState, pushState, removeState, va

Framework for running design reviews using feedback hierarchy and structured critique. \n \n Prioritize feedback by value first (does it solve the problem?), then usability, then delight; defer aesthetic concerns until core value is validated \n Assign senior leaders as project sponsors to oversee quality through live demos and review 100% of shipped screens before launch \n Structure reviews around specific feedback requests; ask presenters exactly what type of input they need rather than openi