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

시작하기

cape

스타31

포크0

업데이트2026년 3월 26일 20:31

Interactive Syngrisi MCP test-engine wrapper for guided debugging, step execution, and debug-session attachment

설치

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

Manus에서 실행

출처

syngrisi

syngrisi/syngrisi

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

다운로드

Manus에서 실행

Cape Skill

Use this skill when you want a Cape-style workflow over the Syngrisi MCP Test Engine without talking to raw JSON-RPC directly.

When to use

Quick manual debugging through the MCP test engine
Reproducing a UI flow step by step
Attaching to an already running debug MCP session
Exploring available MCP tools before running steps

Start commands

Run from packages/syngrisi/e2e:

yarn start:mcp

Raw bridge mode is still available when needed:

yarn start:mcp:bridge

Core workflow

Start the wrapper.
Run start <sessionName> or attach.
Use step for a single action or diagnostic step.
Use batch only for 2 or more sequential steps.
Run shutdown when finished.

Commands

help
start <sessionName> [--headed]
attach
tools
step <stepText> [--docstring <text>] [--docstring-json <json>]
batch <step1> <step2> [step3 ...]
clear
shutdown
exit

Rules of thumb

Always start or attach before executing steps.
Prefer step for all single actions, diagnostics, and value-returning steps.
Use batch only for multi-step reproduction.
Prefer the existing step catalog over raw browser mechanics.
If a session becomes inconsistent, run clear and start a fresh session.

Example session

start demo-session
step "I test"
step "I get current URL"
shutdown

Debug attach flow

If a scenario already started the debug MCP server and wrote a port file into support/mcp/logs/ports/, use:

attach
tools
start attached-session

이 저장소의 다른 Skills

같은 저장소

demo-seed

syngrisi/syngrisi

Spin up an isolated, fully-featured Syngrisi demo instance and seed it with a feature tour built from REAL test-app fixtures. Use when the user wants a runnable demo/sandbox to look at the UI, show off features (visual diffs, match types, ignore regions, AI Triage & auto-accept, RCA DOM diff, cross-browser, branches), or reproduce a flow with realistic data. Features are grouped by run name so the runs list reads as a tour.

2026-07-0331

react-performance-optimization

syngrisi/syngrisi

React performance optimization patterns using memoization, code splitting, and efficient rendering strategies. Use when optimizing slow React applications, reducing bundle size, or improving user experience with large datasets.

2026-04-0231

browser

syngrisi/syngrisi

Browser automation, manual UI debugging, and feature reproduction for Syngrisi via the test-engine CLI. Use this whenever the user wants to walk a browser flow step by step, run a headed UI check, reproduce an E2E scenario from feature files, debug MCP/Test Engine behavior, inspect available BDD steps, or execute a Syngrisi browser workflow without talking to raw JSON-RPC.

2026-03-2831

review-changes

syngrisi/syngrisi

Analysis of unstaged changes for dangerous application logic modifications (Safety Gatekeeper)

2026-01-3031

name	cape
description	Interactive Syngrisi MCP test-engine wrapper for guided debugging, step execution, and debug-session attachment
invocation	/cape
version	1.0.0
allowed-tools	["Bash","Read"]

Cape Skill

Use this skill when you want a Cape-style workflow over the Syngrisi MCP Test Engine without talking to raw JSON-RPC directly.

When to use

Quick manual debugging through the MCP test engine
Reproducing a UI flow step by step
Attaching to an already running debug MCP session
Exploring available MCP tools before running steps

Start commands

Run from packages/syngrisi/e2e:

yarn start:mcp

Raw bridge mode is still available when needed:

yarn start:mcp:bridge

Core workflow

Start the wrapper.
Run start <sessionName> or attach.
Use step for a single action or diagnostic step.
Use batch only for 2 or more sequential steps.
Run shutdown when finished.

Commands

help
start <sessionName> [--headed]
attach
tools
step <stepText> [--docstring <text>] [--docstring-json <json>]
batch <step1> <step2> [step3 ...]
clear
shutdown
exit

Rules of thumb

Always start or attach before executing steps.
Prefer step for all single actions, diagnostics, and value-returning steps.
Use batch only for multi-step reproduction.
Prefer the existing step catalog over raw browser mechanics.
If a session becomes inconsistent, run clear and start a fresh session.

Example session

start demo-session
step "I test"
step "I get current URL"
shutdown

Debug attach flow

If a scenario already started the debug MCP server and wrote a port file into support/mcp/logs/ports/, use:

attach
tools
start attached-session