Tidewave MCP runtime tools — debugging, smoke testing, live state; Use when evaluating code in a running Phoenix app.
日本語の概要は準備中です。原文の説明を表示しています。
1,766 件 ・ 関連度順
概要と使いどころ
Tidewave MCP runtime tools — debugging, smoke testing, live state; Use when evaluating code in a running Phoenix app.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, scheduling, testing or debugging Oban jobs, even for a how-to question: workers, cron, retries…
日本語の概要は準備中です。原文の説明を表示しています。
Build LiveView: async data (assign_async), PubSub (check connected?); Use when handling interactions, debugging…
日本語の概要は準備中です。原文の説明を表示しています。
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task; Use when designing processes or debugging BEAM…
日本語の概要は準備中です。原文の説明を表示しています。
Use when debugging how a value or request reaches Elixir code, finding who calls a function, or planning a signature…
日本語の概要は準備中です。原文の説明を表示しています。
Use when debugging how a value or request reaches Elixir code, finding who calls a function, or planning a signature change. Builds the call tree with mix xref callers instead of reading files one by one.
日本語の概要は準備中です。原文の説明を表示しています。
Provide Phoenix, LiveView, Ecto, OTP, or Oban examples. Use when asked for sample code, a walkthrough, a proper implementation, or expected workflow output. Pair with domain skills. NOT for debugging, direct changes, best-practice advice, or audits.
日本語の概要は準備中です。原文の説明を表示しています。
Use when debugging how a value or request reaches Elixir code, finding who calls a function, or planning a signature change. Builds the call tree with mix xref callers instead of reading files one by one.
日本語の概要は準備中です。原文の説明を表示しています。
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
日本語の概要は準備中です。原文の説明を表示しています。
Provide Phoenix, LiveView, Ecto, OTP, or Oban examples. Use when asked for sample code, a walkthrough, a proper implementation, or expected workflow output. Pair with domain skills. NOT for debugging, direct changes, best-practice advice, or audits.
日本語の概要は準備中です。原文の説明を表示しています。
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
日本語の概要は準備中です。原文の説明を表示しています。
Scope or freeze which files Claude can edit during debugging, a refactor, or review. Use when edits should stay in specific dirs, or for a read-only investigate lock. Backed by a sentinel + PreToolUse hook.
日本語の概要は準備中です。原文の説明を表示しています。
Build LiveView: async data (assign_async), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, live_patch. Use when handling interactions, debugging events, or tracking Presence.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, scheduling, testing or debugging Oban jobs, even for a how-to question: workers, cron, retries, unique jobs, queues, Pro Workflow/Batch. Load it before touching job code; it holds the job rules.
日本語の概要は準備中です。原文の説明を表示しています。
Audit websites for SEO, technical, content, security, JS rendering, and AI readiness using SEOmator CLI. Returns LLM-optimized reports with health scores across 373 rules and 20 categories, and can diff two audits to show what a deploy changed. Use when analyzing websites, debugging SEO issues, checking site health, or comparing a site before and after a change.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive R package for command-line interface styling, semantic messaging, and user communication. Use this skill when working with R code that needs to: (1) Format console output with inline markup and colors, (2) Display errors, warnings, or messages with cli_abort/cli_warn/cli_inform, (3) Show progress indicators for long-running operations, (4) Create semantic CLI elements (headers, lists, alerts, code blocks), (5) Apply themes and customize output styling, (6) Handle pluralization in user-facing text, (7) Work with ANSI strings, hyperlinks, or custom containers. Also use when migrating from base R message/warning/stop, debugging cli code, or improving existing cli usage.
日本語の概要は準備中です。原文の説明を表示しています。
Run full 5-layer analysis (AST, call graph, CFG, DFG, slice) on a specific function for deep debugging or understanding.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic hook debugging workflow. Use when hooks aren't firing, producing wrong output, or behaving unexpectedly.
日本語の概要は準備中です。原文の説明を表示しています。
Terminal pet that lives in your statusline. 12 species, 5 stats (DEBUGGING, PATIENCE, CHAOS, WISDOM, SPEED). Reacts to your workflow - happy when tests pass, sad when builds fail, excited during swarm mode. Deterministic species from user ID.
日本語の概要は準備中です。原文の説明を表示しています。
Braintrust tracing for Claude Code - hook architecture, sub-agent correlation, debugging
日本語の概要は準備中です。原文の説明を表示しています。
Agentica server + Claude proxy setup - architecture, startup sequence, debugging
日本語の概要は準備中です。原文の説明を表示しています。
Optimize SQL query performance through EXPLAIN analysis, indexing strategies, and query rewriting for PostgreSQL, MySQL, and SQL Server. Use when debugging slow queries, analyzing execution plans, or improving database performance.
日本語の概要は準備中です。原文の説明を表示しています。
Configure TLS certificates and encryption for secure communications. Use when setting up HTTPS, securing service-to-service connections, implementing mutual TLS (mTLS), or debugging certificate issues.
日本語の概要は準備中です。原文の説明を表示しています。
Retrieves up-to-date documentation, API references, and code examples for any developer technology. Use this skill whenever the user asks about a specific library, framework, SDK, CLI tool, or cloud service — even for well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. Your training data may not reflect recent API changes or version updates. Always use for: API syntax questions, configuration options, version migration issues, "how do I" questions mentioning a library name, debugging that involves library-specific behavior, setup instructions, and CLI tool usage. Use even when you think you know the answer — do not rely on training data for API details, signatures, or configuration options as they are frequently outdated. Always verify against current docs. Prefer this over web search for library documentation and API details.
日本語の概要は準備中です。原文の説明を表示しています。