rn-self-feedback — chrome-remote-devtools rn-self-feedback, chrome-remote-devtools, community, ide skills, debugging, debugging-tool, devtools, remote, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

このスキルについて

React Nativeを専門とするモバイルアプリ開発エージェントに適しており、Maestro MCPとTauri MCPを使用してデバッグのワークフローを簡素化することを目指しています。 Use Maestro MCP and Tauri MCP to run React Native flows and capture Inspector state for self-validation. Use when working on RN/Inspector code and you need to verify changes (run app, run Maestro flows, capture screenshots, then evaluate results).

# Core Topics

chrome-remote-devtools debugging debugging-tool devtools remote
ohah ohah
[7]
[0]
Updated: 2/21/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
7/11
Quality Score
38
Canonical Locale
en
Detected Body Locale
en

React Nativeを専門とするモバイルアプリ開発エージェントに適しており、Maestro MCPとTauri MCPを使用してデバッグのワークフローを簡素化することを目指しています。 Use Maestro MCP and Tauri MCP to run React Native flows and capture Inspector state for self-validation. Use when working on RN/Inspector code and you need to verify changes (run app, run Maestro flows, capture screenshots, then evaluate results).

このスキルを使用する理由

エージェントにReact Nativeコードの変更を検証し、Maestro MCPとTauri MCPを使用して状態をキャプチャする能力を与え、Inspectorコードの変更の効率的なデバッグとテストを促進し、コードの動作についての自己フィードバックを提供します。

おすすめ

React Nativeを専門とするモバイルアプリ開発エージェントに適しており、Maestro MCPとTauri MCPを使用してデバッグのワークフローを簡素化することを目指しています。

↓ 実現可能なユースケース for rn-self-feedback

React NativeまたはInspectorコードの変更のデバッグ
パッケージ/ react-native-inspectorの変更後の動作の検証
状態のキャプチャとRNコードの変更の結果の評価

! セキュリティと制限

  • Maestro MCPとTauri MCPの設定が必要
  • React NativeとInspectorコードのデバッグに特化している

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is rn-self-feedback?

React Nativeを専門とするモバイルアプリ開発エージェントに適しており、Maestro MCPとTauri MCPを使用してデバッグのワークフローを簡素化することを目指しています。 Use Maestro MCP and Tauri MCP to run React Native flows and capture Inspector state for self-validation. Use when working on RN/Inspector code and you need to verify changes (run app, run Maestro flows, capture screenshots, then evaluate results).

How do I install rn-self-feedback?

Run the command: npx killer-skills add ohah/chrome-remote-devtools. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for rn-self-feedback?

Key use cases include: React NativeまたはInspectorコードの変更のデバッグ, パッケージ/ react-native-inspectorの変更後の動作の検証, 状態のキャプチャとRNコードの変更の結果の評価.

Which IDEs are compatible with rn-self-feedback?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for rn-self-feedback?

Maestro MCPとTauri MCPの設定が必要. React NativeとInspectorコードのデバッグに特化している.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add ohah/chrome-remote-devtools. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use rn-self-feedback immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Imported Repository Instructions

The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.

Supporting Evidence

rn-self-feedback

Install rn-self-feedback, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly
Imported Repository Instructions
The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.
Supporting Evidence

RN Self-Feedback (Maestro + Tauri MCP)

When you change React Native or Inspector code and need to verify behavior, use Maestro MCP and Tauri MCP to run the app, run flows, and capture state—then evaluate the results yourself.

When to use

  • After changing packages/react-native-inspector or related RN/Inspector code.
  • When the user or context implies "verify this" or "check if it works" for RN.
  • When you want to give yourself feedback on whether a change behaves correctly.

Prerequisites

  • MCP setup: MCP is configured so the tauri and maestro servers use the correct mise path. If this repo provides it, run bun run setup-mcp once per machine.
  • Tauri MCP: Inspector (Tauri) app running in debug (bun run dev:inspector:tauri) so Tauri MCP can connect.
  • Maestro MCP: Maestro available via mise (.mise.toml); Maestro MCP enabled in Cursor.

Workflow

  1. Run / drive the RN app

    • Use Maestro MCP to run flows or start the app as needed (e.g. maestro run ... or equivalent MCP tools). Check available Maestro MCP tools for run, tap, assert, etc.

  2. Capture Inspector / UI state

    • Use Tauri MCP to take a screenshot of the Inspector (e.g. "Take a screenshot of my app") or to interact (click, type) if needed.

  3. Evaluate

    • From the screenshot or flow result, decide: does the change work as intended? Note any failures or UI mismatches and suggest fixes.

Notes

  • MCP tools are provided by the configured maestro and tauri servers in your MCP configuration. Call them when you need to run or inspect the RN/Inspector stack.
  • If Tauri MCP cannot connect, confirm Inspector is running with bun run dev:inspector:tauri (debug build).
  • If Maestro MCP fails, ensure MCP is configured (e.g. run bun run setup-mcp if available) and Maestro is installed via mise.

関連スキル

Looking for an alternative to rn-self-feedback or another community skill for your workflow? Explore these related open-source skills.

すべて表示

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

カスタマイズ可能なウィジェットプラグインをprompts.chatのフィードシステム用に生成する

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

React フレームワーク

★ 138.4k
⑂ 0
ブラウザ

pr-review

Logo of pytorch
pytorch

Pythonにおけるテンソルと動的ニューラルネットワーク（強力なGPUアクセラレーション）

★ 98.6k
⑂ 0
開発者