frontend▌

Keyword: react-grab · grab · element context · copy component to ai

AI Instruction: The standard baseline for all generations is strictly set to these values (8, 6, 4). Do not ask the user to edit this file. Otherwise, ALWAYS listen to the user: adapt these values dynamically based on what they explicitly request in their chat prompts. Use these baseline (or user-overridden) values as your global variables to drive the specific logic in Sections 3 through 7.

Comprehensive guide for migrating to and building with Next.js App Router (13+). \n \n Covers migration from Pages Router including file structure mapping, layout creation, metadata handling, and cleanup steps \n Explains App Router file conventions (page.tsx, layout.tsx, loading.tsx, error.tsx, route.ts) and routing patterns (dynamic routes, catch-all, route groups) \n Details Server Components as the default with async/await support, Client Components with 'use client' directive, and data fetc

Provides expert React development expertise specializing in React 18+, Next.js ecosystem, and modern React patterns. Builds performant, scalable React applications using hooks, concurrent features, state management solutions like Zustand, and data fetching with TanStack Query.

Implement internationalization with next-intl, react-i18next, or similar libraries.

Mandatory reference guide for building production MCP servers with tools, resources, prompts, and widgets. \n \n Covers foundational concepts (Tool, Resource, Prompt, Widget primitives), server architecture, authentication patterns (OAuth, Supabase, custom), and deployment strategies \n Includes detailed guides for implementing tools, resources, prompts, response formatting, and widget-based UIs with state management and theming \n Documents common anti-patterns (missing validation, improper err

Role: Builder Module specialist

Use this skill when:

Build maintainable, performant React and Next.js frontends.

Use this skill to design and review Swift APIs that are clear at the point of use, fluent in call sites, and aligned with established Swift naming and labeling conventions. Prioritize readability, explicit intent, and consistency across declarations, call sites, and documentation comments.