Use when testing or debugging a JLCEDA Pro extension (.eext) against a live JLCEDA project page. Covers the full workflow: (1) restarting Edge via mcpextension-dev-mcp-toolsdevplugin to reimport the .eext, (2) connecting to the user's already-logged-in Edge/Chrome via CDP, (3) navigating to a project tab and waiting for the sch canvas to render, (4) handling V3.2-specific dialogs ("另有一个标签页" / "导入扩展"), (5) mouse-drag selecting components on the schematic canvas, (6) clicking the extension's toolbar menu and verifying the resulting IFrame, (7) capturing screenshots + dialog text for comparison, (8) verifying settings-page toggles (e.g. saveToDisk) end-to-end, (9) running a 3-case saveToDisk regression (true / false / new-install), (10) polling the AI chat IFrame through reasoning-model timeouts (deepseek-v4-pro etc.). MUST use mcp devplugin (NOT importplugin — that one fails on V3.2 UI). Use this skill whenever the user says "test the extension in Edge", "verify the menu triggers", "run the workflow end-to-end", "重开浏览器验证", "截图对比", "check the AI chat reply", "verify saveToDisk", or "打开 settings 测试开关". Do NOT use this skill for unit-testing the extension's source code with mocks — use the project's existing mock-test.js / ai-e2e-test.js for that.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryEngineeringStars0
About this skill
Use when testing or debugging a JLCEDA Pro extension (.eext) against a live JLCEDA project page. Covers the full workflow: (1) restarting Edge via mcpextension-dev-mcp-toolsdevplugin to reimport the .eext, (2) connecting to the user's already-logged-in Edge/Chrome via CDP, (3) navigating to a project tab and waiting for the sch canvas to render, (4) handling V3.2-specific dialogs ("另有一个标签页" / "导入扩展"), (5) mouse-drag selecting components on the schematic canvas, (6) clicking the extension's toolbar menu and verifying the resulting IFrame, (7) capturing screenshots + dialog text for comparison, (8) verifying settings-page toggles (e.g. saveToDisk) end-to-end, (9) running a 3-case saveToDisk regression (true / false / new-install), (10) polling the AI chat IFrame through reasoning-model timeouts (deepseek-v4-pro etc.). MUST use mcp devplugin (NOT importplugin — that one fails on V3.2 UI). Use this skill whenever the user says "test the extension in Edge", "verify the menu triggers", "run the workflow end-to-end", "重开浏览器验证", "截图对比", "check the AI chat reply", "verify saveToDisk", or "打开 settings 测试开关". Do NOT use this skill for unit-testing the extension's source code with mocks — use the project's existing mock-test.js / ai-e2e-test.js for that.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
This skill should be used when testing or debugging a JLCEDA Pro extension (.eext) against a live JLCEDA project page. Covers the full workflow: (1) restarting Edge via mcp__extension-dev-mcp-tools__dev_plugin to reimport the .eext, (2) connecting to the user's already-logged-in Edge/Chrome via CDP, (3) navigating to a project tab and waiting for the sch canvas to render, (4) handling V3.2-specific dialogs ("另有一个标签页" / "导入扩展"), (5) mouse-drag selecting components on the schematic canvas, (6) clicking the extension's toolbar menu and verifying the resulting IFrame, (7) capturing screenshots + dialog text for comparison, (8) verifying settings-page toggles (e.g. saveToDisk) end-to-end, (9) running a 3-case saveToDisk regression (true / false / new-install), (10) polling the AI chat IFrame through reasoning-model timeouts (deepseek-v4-pro etc.). **MUST use mcp `dev_plugin` (NOT `import_plugin` — that one fails on V3.2 UI).** Use this skill whenever the user says "test the extension in Edge", "verify the menu triggers", "run the workflow end-to-end", "重开浏览器验证", "截图对比", "check the AI chat reply", "verify saveToDisk", or "打开 settings 测试开关". Do NOT use this skill for unit-testing the extension's source code with mocks — use the project's existing mock-test.js / ai-e2e-test.js for that.
About this listing
Category
Engineering
Reported license
Not specified
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.