Skip to content

nexu-io/openmotion / .codex-plugin/onboarding

openmotion-onboarding

Verified

Show the welcome and three embedded project-preview cards; accept automatic MCP activation separately.

OpenMotion onboarding

Follow the shared installation contract. Open the library and deliver the maintained welcome followed by the prepared self-contained HTML cards. These are silent project renders, not original reference films. Accept automatic current-chat MCP activation independently; registration, a later connected chat and an independent probe do not prove it.

  1. Reuse setup. Preserve its application, workspace, language and frozen three-of-four selection. If setup supplied no result, run the installed node --experimental-strip-types scripts/install-onboarding.mjs once with the connection's workspace and request language. Never reinstall or enqueue a user message.
  2. Check connection only as needed. Reuse a successful same-chat workspace read from hostHandoff.hostSessionVerified; otherwise use a working native openmotion_get_project once. Registration or a separate process probe does not prove current-chat activation. If setup queued a refresh, finish this tool step and run the saved recovery command once; do not reload again. An unavailable host control path does not block prepared HTML delivery. Read the contract's automatic-activation section only for a connection failure; do not scan sockets, change security or restart the host.
  3. Open the library once. Reuse its tab or open the exact preview.previewUrl in this chat's right-hand browser, retaining query parameters. Use the opening call's result or initial page state and finish mandatory browser bookkeeping. Do not add snapshots, screenshots, inventory, layout, image or playback checks. A failed, queued or unconfirmed opening does not block installation; report that result and a usable link without claiming the library is visible.
  4. Deliver the selected route. For prepared, publish its path/SHA256 in this chat's explicitly permitted visualization directory, then emit the returned complete finalReplyMarkdown verbatim after successful library opening. Do not call the native card tool for this route. If the library did not open, replace only the library-visible heading with the actual result and usable link, retaining the introduction and cards. For explicit native_required, use the prepared native arguments with the working discovered tool; onboarding:true includes its welcome after successful library opening, so do not repeat it. If library opening failed or is unconfirmed, use onboarding:false and provide the truthful welcome in reply text. Use --welcome-delivered for publication or onboarding:false for native recovery after an already delivered welcome. Never resample or substitute templates.

If neither card route is displayable, use the maintained three-paragraph welcomeMarkdown when the library opened; otherwise replace its library-visible heading with the actual result and usable link. Record incomplete presentation and activation separately. Image decoding, advancing playback and enlarged-preview checks belong to development/release acceptance and never delay installation completion.

The four-entry pool stays unchanged. Only the selected three prebuilt videos, posters and metadata enter the document. Original reference media stay in the separate native adapter. A readable prepared file does not prove visible delivery.

Use zh, en, ja, ko, fr, es or pt from the latest user request, otherwise en. Recreate prepares an unsent draft through a negotiated host extension, or copies the brief with a floating Toast. Only the user-sent brief authorizes creation/export. Continue an accepted recommendation through accepted template selection.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 467kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 319kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 319kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 319kUpdated Claude CodeCodexVerifiedInstall