Loading...
Loading...
Found 17 Skills
Debugging and acceptance of MaaFramework (MaaFW) applications (in development state, with devices online) — addressing node recognition failures, missed click targets (recognition success ≠ effective clicks), ROI calibration and threshold tuning, single-node run verification, stuck flows and controller connection troubleshooting, end-to-end acceptance, and pipeline_override effect validation; triage is conducted across five layers: configuration, recognition, action, flow, and acceptance, producing root cause conclusions and evidence, with fixes handed over to maafw-pipeline / maafw-interface / maafw-custom. Use when debugging or acceptance-testing a MaaFW application with a device attached — node recognition failures, clicks that miss, ROI calibration and threshold tuning, single-node run verification, stuck flows and controller connection issues, end-to-end acceptance, or pipeline_override effect checks; triage by layer (config / recognition / action / flow / acceptance), then hand the fix back to maafw-pipeline / maafw-interface / maafw-custom.
Review Go implementations against spec acceptance tests. References go-conventions and agent-conduct.
Run all quality checks (tests, lint, typecheck), fix failures, update the changelog, commit, push, and create/update the pull request or merge request.
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.
Write tests that start with acceptance criteria, then add implementation tests for robustness. Use when writing unit tests (Vitest), end-to-end tests (Playwright), visual regression tests, or accessibility tests. Emphasizes user-centric testing, semantic locators, accessibility validation, and the balance between acceptance and implementation testing.
Implement Terraform Provider resources and data sources using the Plugin Framework. Use when developing CRUD operations, schema design, state management, and acceptance testing for provider resources.
Comprehensive BDD testing with Cucumber and Gherkin syntax. Use when writing feature files (.feature), step definitions, hooks, or implementing Behaviour-Driven Development. Covers Gherkin keywords (Feature, Scenario, Given/When/Then, Background, Scenario Outline, Rule), step definition patterns for Ruby/JavaScript/Java/Python, hooks (Before/After/BeforeAll/AfterAll), tags, data tables, doc strings, and best practices. Triggers on cucumber, gherkin, BDD, feature files, step definitions, acceptance testing, executable specifications.
This skill should be used when the user asks to "break down tasks", "create a task list", "plan implementation", "decompose architecture", "create agent tasks", "plan MVP build", "break down feature", "create execution plan", or mentions task breakdown, agent development workflow, or implementation planning. Two-phase workflow for AI agent development with granular, testable tasks.
Supervise and manage an inner Claude Code instance running in tmux. Use this skill when you need to delegate implementation work to an inner Claude while focusing on task planning, progress monitoring, and end-to-end acceptance testing. Ideal for long-running tasks that would otherwise exhaust a single Claude's context window.
Copilot agent that assists with comprehensive QA strategy and test planning to ensure product quality through systematic testing and quality metrics Trigger terms: QA, quality assurance, test strategy, QA plan, quality metrics, test planning, quality gates, acceptance testing, regression testing Use when: User requests involve quality assurance tasks.
BDD-style behavior specification engine for the skill system. Use when: (1) defining a new skill's behavior before implementation, (2) validating a spec against the schema, (3) generating a behavior contract (Mermaid DAG) from a spec, (4) running structural acceptance tests against a built skill. Workflow: Spec → Test → Develop → Contract.
Transform user stories and specifications into precise, verifiable Gherkin acceptance criteria using Given/When/Then syntax with Happy Path, Sad Path, and edge case scenarios. Use when asking for acceptance criteria, Gherkin scenarios, BDD criteria, test scenarios, or AC generation.