frontend▌

Use XcodeBuildMCP tools via the xcodebuildmcp executable instead of raw xcodebuild, xcrun, or simctl.

Comprehensive guide for Medusa backend architecture, workflows, and critical implementation rules. \n \n Covers six rule categories (architecture, type safety, business logic placement, imports, data access, file organization) with specific anti-patterns and enforcement checks \n Enforces strict layer separation: Module → Workflow → API Route → Frontend, with workflows required for all mutations and only GET/POST/DELETE HTTP methods allowed \n Includes critical data handling rules: prices stored

Comprehensive Vue.js testing guidance covering unit, component, and end-to-end testing strategies. \n \n Addresses 11 common testing challenges including async handling, composable testing, Pinia store setup, Suspense components, and Teleport queries \n Recommends Vitest for unit and component testing infrastructure, with Playwright as the preferred E2E framework \n Covers black-box component testing patterns to reduce brittleness during refactoring, async/await synchronization, and snapshot tes

Comprehensive guide for building high-quality MCP servers that enable LLMs to interact with external services. \n \n Four-phase workflow covering research, implementation, review, and evaluation with detailed checklists and best practices for each stage \n Agent-centric design principles including workflow optimization, context efficiency, actionable error messages, and evaluation-driven development \n Language-specific implementation guides for Python (FastMCP) and Node/TypeScript with SDK docu

Rust naming, formatting, and best-practice guidelines covering 50 core rules. \n \n Covers naming conventions (no get_ prefix, iterator patterns, conversion methods), data types (newtypes, slice patterns, pre-allocation), and string handling (prefer bytes for ASCII, use Cow<str> when appropriate) \n Error handling guidance includes ? propagation over try!() , meaningful lifetime names, and lock ordering for concurrency safety \n Includes deprecation mappings (e.g., lazy_static! to OnceLock

Sentry error monitoring, session replay, and tracing for React applications. \n \n Install @sentry/react and initialize via instrument.js (imported first in your entry point) with DSN configuration \n Supports error capture via React 19+ error hooks or ErrorBoundary component for earlier versions \n Includes browser tracing, session replay, and Redux integration; router integrations available for React Router (v4–v7) and TanStack Router \n Source map upload via @sentry/wizard enables readable st

Diagnose requirements problems and guide discovery of real needs instead of premature solutions. \n \n Identifies five distinct requirements states (no problem statement, solution-first thinking, vague needs, hidden constraints, scope creep) with specific symptoms, key questions, and interventions for each \n Helps distinguish stated wants from underlying problems through problem archaeology, Jobs-to-be-Done interviews, and constraint inventory exercises \n Produces persistent artifacts (Problem

Create original visual designs by developing aesthetic philosophies, then expressing them through meticulously crafted .png or .pdf artwork. \n \n Two-step process: first generate a design philosophy manifesto (4–6 paragraphs articulating visual principles around form, space, color, and composition), then express it as a single-page or multi-page visual artifact \n Emphasizes sparse, essential-only text integrated as visual element; ideas communicate through spatial relationships, color zones, t

Translate Figma designs into production-ready code with pixel-perfect visual fidelity. \n \n Structured seven-step workflow: extract node IDs from Figma URLs, fetch design context and screenshots, download assets, translate to project conventions, and validate against Figma specs \n Integrates with Figma MCP server (remote or desktop) to access layout properties, typography, colors, design tokens, and component structure \n Emphasizes design system reuse, design token mapping, and 1:1 visual par

45 performance optimization rules for React and Next.js, organized by impact and category. \n \n Covers 8 rule categories from eliminating waterfalls and bundle optimization (critical) through JavaScript performance and advanced patterns (low priority) \n Each rule includes explanation, before/after code examples, and context to guide automated refactoring and code generation \n Prioritized by impact: waterfalls and bundle size are critical; server-side performance and re-render optimization are