Menu
SkillsMP has collected 13 skills from cybersemics/em. Open a skill to review its source and details.
Showing 13 of 13 collected skills.
ALWAYS USE THIS SKILL before ending a session, yielding your turn, or escalating to the user. A step-by-step exit checklist: documentation still true, nothing uncommitted, nothing unpushed, no test left skipped, CI green, and a report the user can act on.
ALWAYS USE THIS SKILL before writing implementation code for any non-trivial change. Produces a written architectural plan grounded in the existing codebase, then critiques it — both stages, one agent, one atomic unit.
ALWAYS USE THIS SKILL when a change makes something in `docs/` no longer true. Routes the files you changed to the docs that describe them, and brings those docs back in line with reality before the change is committed.
ALWAYS USE THIS SKILL when creating or editing a GitHub issue in this repo — filing a new bug, splitting one out of a comment thread, or adding reproduction steps to an issue that lacks them.
Use this skill after pushing commits or when asked about CI status or to fix failing tests. It monitors GitHub Actions workflow runs for the current branch, waits for completion, returns which checks passed or failed with error details, and provides a…
ALWAYS USE THIS SKILL to run a single e2e test in the real test harness for a given target platform — web/android (Vitest + puppeteer) or iOS (WDIO + Appium + simulator) — and report pass/fail with the failing assertion. Invoked by tdd-write-failing-test and…
iOS environment bring-up for driving the em Capacitor app on BrowserStack App Automate — native (XCUITest) AND web (WKWebView) in one session. The session is created out of band of the wdio MCP (a Bash bring-up script), then driven by either wdio-MCP through…
Use this skill when a test run has failed — a CI check, or a suite run locally. It analyzes the failure output, identifies the specific failing test or build step, categorizes the failure type, and provides guidance on how to fix it. In CI, use in combination…
ALWAYS USE THIS SKILL immediately after reproducing a bug that has documented Steps to Reproduce, and before fixing it. Turns the reproduction into a permanent automated regression test and proves it fails for the right reason. Invoked by issue-repro after…
ALWAYS USE THIS SKILL when working on an issue that has "Steps to Reproduce".
Web (desktop) and Android (mobile Chrome) environment bring-up for driving the em app via the chrome-devtools MCP. Invoked by browser-control when the target is `web` or `android`; not normally called directly.
ALWAYS USE THIS SKILL to bring up a browser/app environment for a given target platform (web, android, or ios) before driving the em app. The caller (e.g. issue-repro) decides the platform and passes it in; this skill is a routing hub that delegates to the…
Regenerate Puppeteer image snapshots using Docker. Use this skill when Puppeteer tests fail due to missing or outdated snapshots. Only use if the UI change was intentional, matches the user’s request or if you otherwise deem it to be necessary. NEVER use this…