Use when accessing Alchemy APIs for RPC calls, token balances, NFT metadata, asset transfers, transaction simulation, or Alchemy-specific features. Also use when the user mentions "SIWE", "SIWS", "x402", "MPP", "mppx", or "agentic gateway" — this skill covers wallet-based auth flows for Alchemy's x402 and MPP…
Integrates Alchemy blockchain APIs using an API key. Requires $ALCHEMYAPIKEY to be set; if unavailable, use the alchemy-agentic-gateway skill instead. Use when user asks about EVM JSON-RPC calls, token balances, NFT ownership or metadata, transfer history, token prices, portfolio data, transaction simulation…
Vovk.ts procedures — atomic unit of server-side logic in Vovk project. Use whenever user asks to build ANYTHING producing or consuming data on server — page loading data ("users page", "dashboard", "product list"), endpoint, API handler, server action, form submission, controller, validation with Zod / Valibot /…
Orchestrates RonyKit service development using the ronyup MCP server (knowledge resources, prompts, scaffold tools). Use when the user mentions RonyKit, ronyup, EdgeServer, contracts, scaffolding a workspace or feature, implementing API handlers and services, frontend bootstrap, integration tests, or design documents…
Optimize React/Next.js runtime performance — eliminate waterfalls, shrink bundles, cut unnecessary re-renders, and speed up rendering. Use when writing, reviewing, or refactoring components for speed, or chasing slow renders, large bundles, janky interactions, or high TTFB/LCP/INP.
Author and maintain Storybook stories with CSF 3.0 best practices — args, decorators, parameters, and config. Use when creating or editing .stories. files, configuring .storybook/, or ensuring every UI component ships with stories.
Develop, migrate, review, document, or debug evjs applications and framework code involving file-based pages, ev.config.ts, server functions, API routes, rendering, plugins, development, builds, and deployment.
Use rpc edge Solana trading infrastructure via MCP tools - doctor, RPC health, priority fees, epoch/leaders, latency compare, Yellowstone first-seen sample, endpoint map, and signed-transaction relay. Prefer when the user needs low-latency Solana RPC/gRPC/sender setup, fee pricing, or agent-ready infra with keys in…
Reason about Solana RPC infrastructure - endpoint health/latency, priority-fee estimation for landing, epoch/slot state, upcoming slot leaders, comparing RPC providers, and relaying a signed transaction with on-chain landing confirmation. Use whenever the task involves choosing/checking a Solana RPC endpoint, pricing…