Run any Skill in Manus with one click

junrei-browser-test

Stars8

Forks0

UpdatedJuly 12, 2026 at 22:26

Launch Junrei's isolated development environment and verify its web UI in a browser. Use when changing React UI, CSS/layout, navigation, interactive controls, or API-backed screen behavior in this repository, and whenever a dev server or port must be chosen for browser testing — with whatever browser tooling the current agent environment provides.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

yuya-takeyama

yuya-takeyama/junrei

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	junrei-browser-test
description	Launch Junrei's isolated development environment and verify its web UI in a browser. Use when changing React UI, CSS/layout, navigation, interactive controls, or API-backed screen behavior in this repository, and whenever a dev server or port must be chosen for browser testing — with whatever browser tooling the current agent environment provides.

Junrei Browser Test

Start the environment

Run pnpm dev from the repository root. Do not select ports manually and do not use pnpm start for isolated agent testing.

Read the launcher output and use its Web URL. pnpm dev assigns free API and Web ports independently, starting from 7868 and 5874, and configures Vite's proxy to the assigned API port.

Use pnpm start only for the normal fixed-port mode: API 7867 and Web 5873 by default, overridable with JUNREI_PORT and JUNREI_WEB_PORT. Do not hardcode ports anywhere else (including .claude/launch.json, whose entries fit only this fixed-port mode) — pnpm dev allocates isolated ports dynamically.

When to test

Run browser verification when a change affects visible UI, routes, selection, layout, responsiveness, or client/server integration. Skip it for isolated non-UI logic when unit tests cover the behavior.

Run the test

The workflow is the same whatever agent harness is running. Never skip verification because a familiar tool surface is missing — use whatever browser control the environment provides:

If a dedicated verifier agent is available (preview-verifier at .claude/agents/preview-verifier.md), delegate to it: it owns browser-tool usage, follows the port contract above, and returns a compact verdict. Pass it the Web URL or tab id when the environment is already running.
Otherwise drive the browser tools directly: reuse a running Junrei tab or server whatever its port, else start one per the contract above, and navigate to the printed Web URL. In-app browser surfaces bootstrapped through a REPL (e.g. browser:control-in-app-browser via mcp__node_repl__js) document their own API — follow that skill rather than duplicating it here.

Inspect the DOM for content and interaction state; take a screenshot only when layout or visual hierarchy is under test.

Keep the development process running while testing and stop it once the task is finished unless the user asks to keep it available. Never stop servers you did not start.

More from this repository

same repository

cost-efficient-delegation

yuya-takeyama/junrei

Cost-efficient model delegation playbook for Claude Code and Codex. Use BEFORE spawning subagents or workflows, when starting research/exploration/multi-step implementation, or when discussing cost or model selection. Routes Claude Fable/Opus/Sonnet/Haiku per call, and Codex GPT-5.6 Sol/Terra/Luna via predefined .codex/agents roles plus per-call overrides. Loading it for delegation work commits the main loop to plan/integrate/review only.

2026-07-268

junrei-session-analysis

yuya-takeyama/junrei

Evidence-grade methodology for analyzing, auditing, or retrospecting a Claude Code or Codex agent session over Junrei's MCP tools, and for closing the self-improvement loop (record a fix, check whether it helped). Use whenever asked to analyze/review/retrospect an agent session, investigate cost/behavior/looping/delegation, propose or record a learning, or produce an evaluation grounded in Junrei data. Encodes the six-tool loop order, the provenance-citation rule, the confidence-class trust order, and truncation handling. Load it before drafting any analysis or logging any learning.

2026-07-198

pr-ci-health

yuya-takeyama/junrei

Prevent and diagnose "PR created but GitHub Actions never start" situations. Use on EVERY commit/push/PR-creation flow in this repo (including commit-commands:commit-push-pr) — rebase onto origin/main before pushing — and whenever `gh pr checks` shows "no checks reported", checks stay absent after a push, or CI seems stuck without any runs.

2026-07-098

aqua-tooling

yuya-takeyama/junrei

How to manage dev tools with aqua (aquaproj) in this repo — adding tools, updating versions, and keeping aqua-checksums.json in sync. Use whenever aqua.yaml or aqua-checksums.json is touched, when the user asks to add/update/pin a CLI tool (node, gh, pnpm, etc.), when tool versions drift between local and CI, or when aqua install fails with a checksum/policy error. Version bumps are NOT complete until checksums are regenerated.

2026-07-088

name	junrei-browser-test
description	Launch Junrei's isolated development environment and verify its web UI in a browser. Use when changing React UI, CSS/layout, navigation, interactive controls, or API-backed screen behavior in this repository, and whenever a dev server or port must be chosen for browser testing — with whatever browser tooling the current agent environment provides.

Junrei Browser Test

Start the environment

Run pnpm dev from the repository root. Do not select ports manually and do not use pnpm start for isolated agent testing.

Read the launcher output and use its Web URL. pnpm dev assigns free API and Web ports independently, starting from 7868 and 5874, and configures Vite's proxy to the assigned API port.

When to test

Run the test

The workflow is the same whatever agent harness is running. Never skip verification because a familiar tool surface is missing — use whatever browser control the environment provides:

If a dedicated verifier agent is available (preview-verifier at .claude/agents/preview-verifier.md), delegate to it: it owns browser-tool usage, follows the port contract above, and returns a compact verdict. Pass it the Web URL or tab id when the environment is already running.
Otherwise drive the browser tools directly: reuse a running Junrei tab or server whatever its port, else start one per the contract above, and navigate to the printed Web URL. In-app browser surfaces bootstrapped through a REPL (e.g. browser:control-in-app-browser via mcp__node_repl__js) document their own API — follow that skill rather than duplicating it here.

Inspect the DOM for content and interaction state; take a screenshot only when layout or visual hierarchy is under test.

Keep the development process running while testing and stop it once the task is finished unless the user asks to keep it available. Never stop servers you did not start.