behavior-to-e2e

Converts user behavior descriptions into executable test cases for Weibo's Android app.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/botterYosuke/The-Trader-Was-Replaced --skill behavior-to-e2e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: behavior-to-e2e
Source: https://github.com/botterYosuke/The-Trader-Was-Replaced/tree/main/.claude/skills/behavior-to-e2e
Command: npx skills add https://github.com/botterYosuke/The-Trader-Was-Replaced --skill behavior-to-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill converts user's verbal descriptions of desired behaviors into E2E test cases for The-Trader-Was-Replaced, ensuring comprehensive coverage and automated testing.

Core Features & Use Cases

  • Behavior Conversion: Translate user descriptions into E2E test scenarios.
  • Test Case Generation: Automatically create test cases and flows for tests/e2e/FLOWS.md.
  • Wiki and FLOWS.md Update: Ensure consistency between the test documentation and the actual test flows.
  • Use Case: For instance, if a user suggests "When the user clicks 'Run', the system should update the portfolio state", this skill would create a corresponding test case in tests/e2e/FLOWS.md.

Quick Start

Use the behavior-to-e2e skill to generate a test case for the behavior: "User clicks 'Run' and the system updates the portfolio state."

Frequently Asked Questions about behavior-to-e2e

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

FAQPage Schema
How do I convert user behavior descriptions into E2E test cases?

This skill converts user behavior descriptions into E2E test cases by translating verbal scenarios into structured test flows, automatically generating entries for the test documentation file while ensuring consistent coverage.

When should I generate E2E test cases during the development workflow?

E2E test case generation should occur during behavior refinement, code reviews, and before implementation. Invoking the skill at these stages ensures generated tests accurately reflect desired behaviors and maintain documentation consistency.

Does this E2E test generation skill work with Bevy and Python gRPC?

Yes, this skill generates E2E test cases specifically for The-Trader-Was-Replaced, an environment built with Bevy and Python gRPC. It aligns generated test flows directly with this specific technology stack.

How do I keep test documentation consistent with actual E2E test flows?

To keep test documentation consistent with actual E2E test flows, the skill automatically updates the wiki and the FLOWS.md file, ensuring documented test scenarios match the implemented automated testing behaviors exactly.

What is the best way to ensure comprehensive E2E test coverage for new features?

The best way to ensure comprehensive E2E test coverage is to convert user behavior descriptions into structured test scenarios. This skill translates verbal feature requests into automated test cases, maintaining consistency between documentation and execution.