Platform Integration Workflow

Add platform support by defining platform metadata (id, hostname, displayName, selectors), implementing a platform strategy class, registering it in centralized configuration, then testing detection and prompt injection. This Skill guides you through a 10-step workflow using the Strategy Pattern for seamless integration with new AI chat platforms.

Use centralized configuration and the Strategy Pattern to manage multiple platforms. Define each platform's metadata once, implement individual strategy classes for their unique input types, and register them in one config file. This approach scales easily as you add Gemini, Mistral, Claude, or other platforms without duplicating logic.

Inspect the platform's DOM to locate the input field where prompts are inserted, then extract its CSS selector. This selector becomes part of the platform metadata definition. The Skill includes manual verification steps to confirm the selector works correctly before testing automated injection.

The Skill covers both unit testing and manual verification. Unit tests validate strategy logic and platform detection, while manual testing confirms the prompt library icon renders and prompts inject correctly. Both steps are necessary to prevent regressions across different platform interfaces.

Test platform detection, verify the UI badge renders correctly, and confirm prompts inject into the target input field. The Skill provides comprehensive testing guidance including unit tests for strategy classes and manual steps to validate end-to-end functionality on the actual platform.

Yes. The Strategy Pattern adapts to diverse AI interfaces by letting each platform strategy implement its own injection logic. This handles variations in input field types, authentication flows, and UI layouts across different platforms like Gemini, Mistral, and Meta AI.