linkedin-voyager-sdui-methodology
Installation
SKILL.md
Voyager and SDUI methodology
Treat Voyager and SDUI as observed private web protocols, not stable APIs.
- Capture the exact current UI flow.
- Group calls by causal order and identify the smallest request that performs or verifies the operation.
- Preserve opaque IDs exactly as captured for that session; never promote them into tool names or source constants.
- Replay reads before writes when possible.
- For SDUI, preserve prerequisite state/component calls if the final submit depends on them.
- Verify writes with a fresh independent read or UI state.
Read references/protocol-notes.md before interpreting opaque IDs or nested form state.