305건 · 관련도순
Collective research memory for AI coding agents — search prior research before hitting the web, save findings back to the shared cache, view karma stats. Use when the user asks a library/API/framework question, before running WebSearch/WebFetch, or after deep web research so the next agent doesn't repay the cost. Talks directly to the hosted MCP endpoint via JSON-RPC — no local MCP server required.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Complete operational guide for the NV oOS (Open Operator System) WordPress plugin in Docker/WSL2 — setup, assistant creation, credential tokens, MCP tool calling, API key auto-detection, env var bridging, common fixes, and IGCSE study configuration. Use when setting up the plugin for the first time, creating assistants programmatically, generating MCP bridge tokens, troubleshooting Docker path issues, bridging API keys, or calling tools via JSON-RPC over HTTP.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Alchemy — alchemy Web3 development platform management including app configuration, RPC endpoint health, webhook notifications, NFT API usage, Enhanced APIs, gas optimization, and usage analytics. Covers request volume monitoring, error rates, compute unit consumption, and multi-chain endpoint health.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and write Cloudflare Durable Objects. SQLite storage, RPC methods, WebSocket hibernation, alarms, class lifecycle (exports or migrations), and testing. Use for stateful coordination, rooms, per-user state, counters, rate limiters.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Activate for any ticket that touches a Supabase RPC, edge function, or TypeScript client function in src/lib/. Ensures both caller and callee are verified before state:ready-for-qa.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Uses Falco YAML rules for runtime threat Tespit in containers and Kubernetes, monitoring syscalls for shell spawns, file tampering, network anomalies, and privilege escalation. Manages Falco rules via the Falco gRPC API and parses Falco alert output. Use building yaparken container runtime security or investigating k8s cluster compromises.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Model Context Protocol (MCP 仕様 2026-07-28, modelcontextprotocol.io) リファレンス。 JSON-RPC, server/discover, tools/call, subscriptions/listen, MRTR (InputRequiredResult), CacheableResult, Streamable HTTP, CIMD, MCP Apps (ui://), MCP Registry (server.json, MCPB), tasks 拡張。ホスト設定・SDK は別スキル。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Conducts security testing of REST, GraphQL, and gRPC APIs to identify vulnerabilities in authentication, authorization, rate limiting, input validation, and business logic. The tester uses the OWASP API Security Top 10 as the testing framework, combining Burp Suite interception with Postman collections and custom scripts to test endpoint security at every privilege level. Activates for requests involving API security testing, REST API pentest, GraphQL security assessment, or API vulnerability testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Starts a CARLA UE 5.8 server from a ue58-dev tree — the editor binary in -game mode (the working headless server), the packaged shipping build, or the full editor — with offscreen/nullrhi rendering, custom RPC and streaming ports, and native ROS 2 via the single-dash -ros2 flag. Probes a running server, and stops one cleanly despite the 15-character process-name truncation. Use when the user asks to "run/start CARLA UE5", "launch a ue58 server", "run headless", "publish ROS 2 topics from UE5", or a client cannot reach the simulator.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Launches a CARLA RPC server a carla.Client can connect to, working out for itself what you pointed it at — a downloaded/extracted release, a package cooked inside a checkout, or a source checkout run through the UE4 editor — headless or windowed, and shuts it down cleanly. ROS2=1 starts it with the native ROS 2 interface active (--ros2, --rmw=fastdds/cyclonedds/zenoh, --ros-domain-id). Use when the user asks to "run/start the CARLA server", "boot CARLA headless", "launch CARLA with a window", "run the CARLA I downloaded", "start CARLA with ROS2 enabled", or "serve a packaged CARLA build".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Hono (軽量・マルチランタイム対応 Web フレームワーク) リファレンス。 Hono App, Context (c.req / c.json / c.text / c.html), HonoRequest, Routing, HTTPException、 Built-in Middleware (JWT, CORS, CSRF, Cache, Logger, Compress, Basic / Bearer Auth, Mount)、 Helpers (Cookie, Streaming, WebSocket, Factory, RPC)、 Cloudflare Workers / Deno / Bun / Node.js / AWS Lambda 対応、@hono/* アダプターパッケージ。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
OpenAI Codex (CLI / IDE / cloud / ChatGPT desktop app) リファレンス。 GPT-6 系, Fast / Ultrafast mode, codex exec, スラッシュコマンド, prompting, AGENTS.md, rules, subagents, approvals, auto-review, sandbox, permission profiles, profiles, config.toml, 環境変数, roles, MCP 設定, GitHub Action, Codex SDK, App Server (JSON-RPC), Agents SDK 連携, Codex skills (.agents/skills), plugins, scheduled tasks, Browser, Computer Use, cloud / local / worktree 環境, git worktrees, Record & Replay, cloud 委譲, GitHub / GitLab / Linear / Slack 連携, administration, provisioning, analytics API, compliance API, LLM gateway, Codex Security 脆弱性スキャン (SARIF), deep scan, triage, findings, threat model, security hardening。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate Skills from HTTP MCP servers with async job patterns (submit/status/result). Use when converting MCP specifications (.mcp.json) into reusable Skills using mcp_tool_catalog.yaml. Supports --lazy mode for context-saving generation. Also use for calling async MCP tools via JSON-RPC 2.0 with session-based polling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Query the Lyrion Music Server over its JSON-RPC API from the Flask app. Use this whenever a task needs live data from Lyrion — the now-playing track, player list, transport state, album art, or any `slim.request` command — or when adding a feature that reads from the music server. Covers the request format, the tag system, the shared cache, and the self-signed-TLS rules, so new calls match how `services/lyrion.py` already talks to the server.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Query Solana blockchain data with USD pricing — wallet balances, token portfolios with values, transaction details, NFTs, whale detection, and live network stats. Uses Solana RPC + CoinGecko. No API key required.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Query Base (Ethereum L2) blockchain data with USD pricing — wallet balances, token info, transaction details, gas analysis, contract inspection, whale detection, and live network stats. Uses Base RPC + CoinGecko. No API key required.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
End-to-end Solana development playbook (Jan 2026). Prefer Solana Foundation framework-kit (@solana/client + @solana/react-hooks) for React/Next.js UI. Prefer @solana/kit for all new client/RPC/transaction code. When legacy dependencies require web3.js, isolate it behind @solana/web3-compat (or @solana/web3.js as a true legacy fallback). Covers wallet-standard-first connection (incl. ConnectorKit), Anchor/Pinocchio programs, Codama-based client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.