OpenParable
Skip to content
← Back to skills

Polling Parity

Development
polling-parity

Polling Parity is an Agent Skill for development published in the fossasia/visdom repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Keep feature behavior identical across WebSocket and polling transport modes. Use when adding socket commands, event flows, or transport-sensitive UI updates.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/fossasia/visdom/blob/HEAD/.agents/skills/polling-parity/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/polling-parity, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Skill: Polling and WebSocket Parity

When to Use

Use this skill for any real-time feature that touches transport behavior.

Core Workflow

  1. Implement feature changes in the primary socket path.
  2. Mirror equivalent behavior in polling wrappers/fallback logic.
  3. Confirm command names and payload shapes are transport-neutral.
  4. Validate environment switch, pane update, and callback routing in both modes.
  5. Ensure no mode-specific regressions in reconnect/reload behavior.

Guardrails

  • Do not ship socket-only features.
  • Keep command contracts stable across both modes.
  • Avoid mode-specific payload forks unless explicitly versioned.

Documentation

  • Skill reference
  • py/visdom/server/handlers/socket_handlers.py
  • js/api/ApiProvider.js
  • js/api/Legacy.js
  • AGENTS.md
  • CONTRIBUTING.md

Assets

  • See assets/README.md and store templates/resources in assets/.

Tests

  • Follow the default flow in references/TESTS.md.