Menu
Interactive Syngrisi MCP test-engine wrapper for guided debugging, step execution, and debug-session attachment
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
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.
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.
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.
Analysis of unstaged changes for dangerous application logic modifications (Safety Gatekeeper)
| 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"] |
Use this skill when you want a Cape-style workflow over the Syngrisi MCP Test Engine without talking to raw JSON-RPC directly.
Run from packages/syngrisi/e2e:
yarn start:mcp
Raw bridge mode is still available when needed:
yarn start:mcp:bridge
start <sessionName> or attach.step for a single action or diagnostic step.batch only for 2 or more sequential steps.shutdown when finished.helpstart <sessionName> [--headed]attachtoolsstep <stepText> [--docstring <text>] [--docstring-json <json>]batch <step1> <step2> [step3 ...]clearshutdownexitstart or attach before executing steps.step for all single actions, diagnostics, and value-returning steps.batch only for multi-step reproduction.clear and start a fresh session.start demo-session
step "I test"
step "I get current URL"
shutdown
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