원클릭으로 Manus에서 모든 스킬 실행

tidewave-integration

스타0

포크0

업데이트2026년 4월 1일 07:32

Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

forest

forest/claude-elixir-phoenix

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Tidewave MCP Integration

Runtime intelligence for Phoenix apps via MCP. Prefer Tidewave tools over Bash when available.

Iron Laws — Never Violate These

DEV ONLY — Never use Tidewave tools in production contexts. Avoid on shared dev servers with production data copies
PREFER TIDEWAVE OVER BASH — mcp__tidewave__get_docs > web_fetch, execute_sql_query > psql
CHECK AVAILABILITY FIRST — Use /mcp command or detect mcp__tidewave__ tools
SQL IS READ-HEAVY — Use execute_sql_query for SELECT, be careful with mutations
EXACT VERSIONS — get_docs returns docs for YOUR mix.lock versions, not latest

Quick Reference

Task	Tidewave Tool	Fallback
Get docs	`mcp__tidewave__get_docs Module.func/3`	`web_fetch hexdocs.pm/...`
Run code	`mcp__tidewave__project_eval`	`mix run -e "code"`
SQL query	`mcp__tidewave__execute_sql_query`	`psql $DATABASE_URL`
Find source	`mcp__tidewave__get_source_location`	`grep -rn "defmodule"`
Inspect DOM	`mcp__Tidewave-Web__browser_eval`	Manual browser inspection
List schemas	`mcp__tidewave__get_ecto_schemas`	Read `lib/*/schemas/`
Read logs	`mcp__tidewave__get_logs level: :error`	`tail -f log/dev.log`

Detection

# Check endpoint
curl -s http://localhost:4000/tidewave/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"ping"}'

Or use /mcp in Claude Code to see connected servers.

Essential Patterns

Test Function Immediately

# mcp__tidewave__project_eval
MyApp.Accounts.create_user(%{email: "test@example.com"})

Verify Migration

-- mcp__tidewave__execute_sql_query
SELECT column_name, data_type FROM information_schema.columns
WHERE table_name = 'users';

Debug LiveView (with PID from browser)

# mcp__tidewave__project_eval
pid = pid("0.1234.0")
:sys.get_state(pid) |> Map.get(:socket) |> Map.get(:assigns) |> Map.keys()

Setup Requirements

# mix.exs
{:tidewave, "~> 0.1", only: :dev}

# endpoint.ex (in dev block)
plug Tidewave

# config/dev.exs (for LiveView source mapping)
config :phoenix_live_view,
  debug_heex_annotations: true,
  debug_attributes: true

Proactive Runtime Checks

Don't just use Tidewave reactively. Query runtime state at workflow checkpoints automatically:

After code edits: get_logs level: :error (catch runtime crashes)
After features complete: project_eval smoke test (behavioral check)
Before planning: get_ecto_schemas + routes eval (concrete context)
When investigating: Auto-capture errors before asking user
LiveView UI bugs: browser_eval to inspect DOM state before editing components

See ${CLAUDE_SKILL_DIR}/references/proactive-patterns.md for full integration points.

References

For detailed patterns, see:

${CLAUDE_SKILL_DIR}/references/proactive-patterns.md - Push-like runtime patterns at workflow checkpoints
${CLAUDE_SKILL_DIR}/references/tool-examples.md - Complete tool usage examples
${CLAUDE_SKILL_DIR}/references/validation-checklist.md - Runtime validation patterns

이 저장소의 다른 Skills

같은 저장소

release

forest/claude-elixir-phoenix

CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.

2026-06-040

elixir-idioms

forest/claude-elixir-phoenix

OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.

2026-06-040

phx-verify

forest/claude-elixir-phoenix

Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.

2026-06-040

phx-audit

forest/claude-elixir-phoenix

Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.

2026-05-250

phx-permissions

forest/claude-elixir-phoenix

Recommend safe Bash permissions for Elixir mix commands in settings.json. Use when permission prompts slow workflow, "fix permissions", "reduce prompts", "auto-allow mix".

2026-05-200

phx-perf

forest/claude-elixir-phoenix

Analyze Elixir/Phoenix performance — N+1 queries, assign bloat, ecto optimization, genserver bottlenecks. Use when slowness, timeouts, or high memory reported.

2026-05-200

name	tidewave-integration
description	Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
effort	low
user-invocable	false

Tidewave MCP Integration

Runtime intelligence for Phoenix apps via MCP. Prefer Tidewave tools over Bash when available.

Iron Laws — Never Violate These

DEV ONLY — Never use Tidewave tools in production contexts. Avoid on shared dev servers with production data copies
PREFER TIDEWAVE OVER BASH — mcp__tidewave__get_docs > web_fetch, execute_sql_query > psql
CHECK AVAILABILITY FIRST — Use /mcp command or detect mcp__tidewave__ tools
SQL IS READ-HEAVY — Use execute_sql_query for SELECT, be careful with mutations
EXACT VERSIONS — get_docs returns docs for YOUR mix.lock versions, not latest

Quick Reference

Task	Tidewave Tool	Fallback
Get docs	`mcp__tidewave__get_docs Module.func/3`	`web_fetch hexdocs.pm/...`
Run code	`mcp__tidewave__project_eval`	`mix run -e "code"`
SQL query	`mcp__tidewave__execute_sql_query`	`psql $DATABASE_URL`
Find source	`mcp__tidewave__get_source_location`	`grep -rn "defmodule"`
Inspect DOM	`mcp__Tidewave-Web__browser_eval`	Manual browser inspection
List schemas	`mcp__tidewave__get_ecto_schemas`	Read `lib/*/schemas/`
Read logs	`mcp__tidewave__get_logs level: :error`	`tail -f log/dev.log`

Detection

# Check endpoint
curl -s http://localhost:4000/tidewave/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"ping"}'

Or use /mcp in Claude Code to see connected servers.

Essential Patterns

Test Function Immediately

# mcp__tidewave__project_eval
MyApp.Accounts.create_user(%{email: "test@example.com"})

Verify Migration

-- mcp__tidewave__execute_sql_query
SELECT column_name, data_type FROM information_schema.columns
WHERE table_name = 'users';

Debug LiveView (with PID from browser)

# mcp__tidewave__project_eval
pid = pid("0.1234.0")
:sys.get_state(pid) |> Map.get(:socket) |> Map.get(:assigns) |> Map.keys()

Setup Requirements

# mix.exs
{:tidewave, "~> 0.1", only: :dev}

# endpoint.ex (in dev block)
plug Tidewave

# config/dev.exs (for LiveView source mapping)
config :phoenix_live_view,
  debug_heex_annotations: true,
  debug_attributes: true

Proactive Runtime Checks

Don't just use Tidewave reactively. Query runtime state at workflow checkpoints automatically:

After code edits: get_logs level: :error (catch runtime crashes)
After features complete: project_eval smoke test (behavioral check)
Before planning: get_ecto_schemas + routes eval (concrete context)
When investigating: Auto-capture errors before asking user
LiveView UI bugs: browser_eval to inspect DOM state before editing components

See ${CLAUDE_SKILL_DIR}/references/proactive-patterns.md for full integration points.

References

For detailed patterns, see:

${CLAUDE_SKILL_DIR}/references/proactive-patterns.md - Push-like runtime patterns at workflow checkpoints
${CLAUDE_SKILL_DIR}/references/tool-examples.md - Complete tool usage examples
${CLAUDE_SKILL_DIR}/references/validation-checklist.md - Runtime validation patterns