What problem does it solve? Working on PingOne DaVinci authentication flows involves subtle multi-screen collector handling, callback URI registration, PKCE, and token custody rules that are easy to get wrong, leading to broken flows or security mistakes. ## Core Features & Use Cases - Flow correctness guidance: Enforces proper multi-screen progression by reading collectors after every SDK call, routing ActionCollector and FlowCollector controls correctly, and re-rendering on node changes. - Callback and tenant configuration safety: Requires read-only checks before mutating PingOne application redirect URIs and protects secrets like nonce, state, code verifier, and tokens from being printed. - Embedded and pop-out runners: Ensures both presentation modes share one flow implementation with correct pop-up handling, independent state, and consistent theming. - Use Case: When a DaVinci SDK login page shows only one screen or fails before any collector renders, use this Skill to diagnose whether the cause is a callback allowlist, client, flow policy, or CORS issue rather than a React rendering bug. ## Quick Start Ask the assistant to fix or extend the DaVinci widget or Orchestration SDK login page while following the pingone-davinci-orchestration skill rules.
