implementer-agent

Convert Zephyr test designs into Playwright and Appium automated tests.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/swongsuddee/windflu-test --skill implementer-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementer-agent
Source: https://github.com/swongsuddee/windflu-test/tree/main/.agents/toolkit/implementer-agent
Command: npx skills add https://github.com/swongsuddee/windflu-test --skill implementer-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the bottleneck of turning a Zephyr test design into working, platform-correct automated tests without inconsistent locators or duplicated logic.

Core Features & Use Cases

  • Locator-first implementation: produces validated element locators via a priority hierarchy before any spec is written, improving stability across UI changes.
  • Playwright web and API implementation: generates deterministic TypeScript specs for web-ui and api test types, following strict Arrange-Act-Assert and “one user-facing action” rules.
  • Appium/WebdriverIO mobile implementation: implements mobile-ui, ios-only, and android-only cases using the correct file suffix conventions and mobile waiting/selector guardrails.
  • Page object creation: creates or extends typed page objects and helpers to keep specs clean, reusable, and selector logic centralized.
  • Safety and consistency enforcement: prevents hardcoded credentials/URLs, avoids time-based waits, and aligns with project conventions and storage-state reuse patterns.

Quick Start

Use the implementer-agent with a Zephyr test design file to generate the required locators, create any needed page objects, and implement all automatable cases for the correct test type.

Frequently Asked Questions about implementer-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert Zephyr test designs into Playwright automated tests?

To convert Zephyr test designs into Playwright automated tests, you provide the design file to generate validated element locators, create typed page objects, and output deterministic TypeScript specs for web-ui and api test types.

How do I implement Appium WebdriverIO mobile tests from existing test cases?

Implementing Appium WebdriverIO mobile tests from existing cases requires generating mobile-ui, ios-only, and android-only specs using correct file suffix conventions alongside mobile waiting and selector guardrails.

What is the best locator strategy for stable Playwright UI test automation?

The best locator strategy for stable Playwright UI test automation applies a strict priority hierarchy to validate element locators before writing any spec, preventing fragile selectors and improving resilience across UI changes.

Can I reuse page objects and helpers across web and mobile test automation?

Yes, you can reuse page objects and helpers across web and mobile test automation by creating or extending typed objects that centralize selector logic, keeping deterministic specs clean and maintainable.

Why should test automation specs follow Arrange-Act-Assert with a single action?

Test automation specs should follow Arrange-Act-Assert with a single user-facing action to enforce deterministic test behavior, isolate failures, and align with strict project conventions for reliable end-to-end execution.

How to prevent hardcoded credentials and URLs in automated test suites?

To prevent hardcoded credentials and URLs in automated test suites, enforce safety constraints by utilizing environment variables for sensitive data and applying storage-state reuse patterns throughout the spec implementation.