frontend▌

SDK-first frontend integration for Medusa storefronts with React Query patterns and critical API calling rules. \n \n Always use the Medusa JS SDK for all API requests—never use regular fetch(), as it lacks required headers (publishable API key for store routes, auth for admin routes) \n Pass plain JavaScript objects to SDK methods; never use JSON.stringify() on body parameters, as the SDK handles serialization automatically \n Use useQuery for GET requests and useMutation for POST/DELETE reques

Query Hyperliquid market data, order books, metadata, and execute withdrawals via Grimoire CLI. \n \n Supports six command categories: mid prices, L2 order books, open orders, perpetual metadata, spot metadata, and USDC withdrawals \n Output formats include JSON, table, and spell (for snapshot-based agent inputs); withdrawals require explicit user confirmation and keystore credentials \n Read-only commands (mids, l2-book, open-orders, meta, spot-meta) return market snapshots; stateful withdraw a

Refactor SwiftUI views toward small, explicit, stable types with MV-first defaults. \n \n Enforces view ordering (environment, state, computed vars, init, body, helpers) and strongly prefers dedicated subview types over computed some View helpers for non-trivial sections \n Defaults to Model-View architecture: local state in views, shared dependencies in environment, business logic in services/models, view models only when explicitly required or already present \n Extracts actions and side effec

Full-stack React framework with file-system routing, Server Components, and built-in performance optimization. \n \n File-system based routing with layouts, dynamic segments, and catch-all routes; supports both static generation (SSG) and server-side rendering (SSR) \n Server Components for data fetching directly in components; Client Components with the use hook for interactive features \n Server Actions for handling data mutations and form submissions without separate API endpoints \n Built-in

Build Next.js 16 apps with async route params, Server Components, Cache Components, and Partial Prerendering. \n \n Covers 25+ documented errors and solutions, including async params migration, parallel routes with required default.js , and \"use cache\" directive patterns \n Supports Cache Components with revalidateTag() , updateTag() , and refresh() APIs for opt-in caching and stale-while-revalidate strategies \n Includes proxy.ts migration (replaces deprecated middleware.ts), Turbopack produc

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

Automate App Store Connect app creation by driving the web UI form with browser automation. \n \n Requires a pre-registered bundle ID in the Apple Developer portal and user sign-in to App Store Connect; handles multi-platform selection (iOS, macOS, tvOS, visionOS) and all required fields including the tricky User Access radio buttons \n Includes detailed workarounds for known UI quirks: dropdown menu navigation for \"New App\", asynchronous Bundle ID dropdown loading, and span-overlay intercepti

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

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

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