research-and-implement

You can research API integrations by using browser automation to gather official documentation, tutorials, and common pitfalls, then translating those findings into a structured implementation plan to code with confidence.

The best way to evaluate a new library is to establish best practices through a structured research workflow, gathering evidence from sources to produce actionable implementation patterns and examples before you start coding.

Browser automation works for technical documentation by systematically navigating official docs and tutorials to compile a findings document, satisfying a defined workflow from goal definition to evidence-based verification.

Yes, you can use this approach to validate the best implementation method for complex features by researching sources with browser automation, which reduces guesswork and rework during coding.

A limitation of using browser automation for research is that it primarily focuses on gathering external documentation and patterns, meaning you must still manually verify findings against your specific project environment.

No external dependencies are required to run the research and implementation workflow, as the skill operates independently to define goals, gather sources, and output a structured plan with notes.