build-zoom-ui-toolkit-app — Codex command: what it does
This command adds a ready-made Zoom Video SDK session UI to a web app. Use it when a toolkit surface fits better than a fully custom video interface.
~/.codex/prompts/build-zoom-ui-toolkit-app.mdWhat build-zoom-ui-toolkit-app does
The command reviews the repository before editing it. It looks for existing Video SDK code, the web framework, server-side token generation, a session UI shell, and the place where the toolkit should mount. It also asks for the target UX, files to change, auth route, mount plan, and verification steps.
It then wires the UI Toolkit into the web layer, adds the server-side signature or auth path needed to join, and configures permissions, join and leave behavior, plus media settings. Afterward it rechecks the mount code, auth flow, and session lifecycle, then runs available local builds or tests. A server-side signature or auth path is required for the session to join. The command keeps Meeting SDK assumptions out of a Video SDK integration.
What it helps with
- add a ready-made Zoom Video SDK web UI
- wire server-side session authentication
- mount the UI Toolkit in an existing frontend
- check session join, leave, and lifecycle handling
- keep Meeting SDK logic out of a Video SDK flow
Example prompts for the agent
- Add a ready-made Zoom Video SDK session UI to this web app with the UI Toolkit.
- Inspect the auth route and mount location, then connect the session join and leave flow and run the available checks.
- Run
/build-zoom-ui-toolkit-app, plan the file changes first, then implement and verify the integration.
How to install build-zoom-ui-toolkit-app
Manually: put the files in place
~/.codex/prompts/build-zoom-ui-toolkit-app.mdCall it with /prompts:build-zoom-ui-toolkit-app. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.claude/commands/build-zoom-ui-toolkit-app.mdCall it with /build-zoom-ui-toolkit-app. For all projects use ~/.claude/commands/
Manually: put the files in place
.github/prompts/build-zoom-ui-toolkit-app.prompt.mdManually: put the files in place
.gemini/commands/build-zoom-ui-toolkit-app.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about build-zoom-ui-toolkit-app
How do I install build-zoom-ui-toolkit-app in Codex?
Save the command file at ~/.codex/prompts/build-zoom-ui-toolkit-app.md.
What does build-zoom-ui-toolkit-app do?
It connects the Zoom Video SDK UI Toolkit to a web app, sets up session authentication and mounting, and checks the core session lifecycle. It can also run available local builds or tests.
Does this command build a Zoom Meeting SDK integration?
No. It targets a prebuilt Video SDK session UI and keeps Meeting SDK assumptions out of the implementation.
Source text
build-zoom-ui-toolkit-app.md · MIT
--- description: Implement a Zoom Video SDK UI Toolkit integration for a prebuilt web session UI with the right auth, mount strategy, and session lifecycle. --- # Build Zoom UI Toolkit App Use this command when the repo needs a prebuilt web UI for a Zoom Video SDK session instead of a fully custom video interface. ## Preflight 1. Inspect the codebase for existing Video SDK usage, web frontend structure, server-side token generation, and session UI shells. 2. Confirm the requirement is a prebuilt Video SDK UI and not a real Zoom meeting flow. 3. Identify the host framework and where the UI Toolkit should mount. 4. Check whether the required Video SDK session auth path exists without printing secrets. ## Plan Before making changes: - state the target web framework and session UX goal - list the files that will be changed - state the auth path, mount strategy, and session lifecycle responsibilities - state how the UI Toolkit flow will be verified ## Commands 1. Add or correct the UI Toolkit integration in the appropriate web UI layer. 2. Wire the minimum server-side signature or auth path required for a working session join. 3. Keep custom UI work limited unless the user explicitly needs it beyond the toolkit surface. 4. Configure permissions, session join and leave behavior, and any required media settings. 5. Avoid mixing Meeting SDK assumptions into a Video SDK UI Toolkit integration. ## Verification 1. Re-read the UI mount code, Video SDK auth path, and session join flow after changes. 2. Run the relevant local build or tests where available. 3. Verify the toolkit mount path, auth flow, and base session lifecycle. 4. State any remaining blocker such as browser restrictions, token generation gaps, or unsupported environment requirements. ## Summary ```text ## Result - Action: implemented or updated a Zoom UI Toolkit integration - Status: success | partial | failed - Details: files changed, auth path, mount strategy, verification run ``` ## Next Steps - Test the session in the target browser environment. - If deeper layout control is required, switch to `/build-zoom-video-sdk-app`. - If auth is incomplete, fix the token path before expanding UI work.
© Zoom · MIT · openai/plugins
