Socket.IO lifecycle conventions for PortOS client views — event-driven state swaps, single-subscriber resources (PTY shells, agent runs), pending-request tracking, stale-response filtering, and deferred-work guards. Invoke before wiring or debugging a socket-driven UI.
$npx -y skills add atomantic/portos --skill portos-socket-uiInstalls into the current project.
Run `npx skills use "https://github.com/atomantic/portos" --skill "atomantic/portos/portos-socket-ui"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/atomantic/portos" that are relevant to the current task. Run `npx skills add "https://github.com/atomantic/portos"` and select the relevant skills, then follow their instructions.