collection-generator

Create curated Playwright collections by tagging existing specs and generating JSON reports.

Updated Aug 27, 2026

Search Tags:#automation #testing #reporting #playwright #collection #tagging #cross-module

Ready to run

npx skills add https://github.com/midas44/ttt-expert-v2 --skill collection-generator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: collection-generator
Source: https://github.com/midas44/ttt-expert-v2/tree/main/.claude/skills/collection-generator
Command: npx skills add https://github.com/midas44/ttt-expert-v2 --skill collection-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidating test efforts across multiple modules into a single, maintainable Playwright test suite without duplicating specs.

Core Features & Use Cases

Consolidates test cases from multiple modules into a single curated Playwright collection.
Adds a shared tag to existing specs to enable cross-module execution and reporting.
Generates a report JSON to track tag application, scope, and missing specs.
Enables end-to-end cross-domain validation by grouping tests across domains while keeping originals intact.

Quick Start

Create a new collection with a descriptive name and let the skill aggregate relevant tests into a single tagged Playwright suite.

Frequently Asked Questions about collection-generator

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

FAQPage Schema

How do I run cross-module Playwright tests without duplicating specs?▼

You can group cross-module Playwright tests by injecting a shared collection tag into existing specs. This allows combined validations across modules while keeping original test files intact and avoiding duplication.

Can I consolidate test cases from multiple domains into a single Playwright suite?▼

Yes, multi-domain test consolidation is supported by reading existing manifests and curating a single Playwright collection. A shared tag is applied to relevant specs to enable unified cross-domain execution.

Does the collection generator modify existing test specs when applying tags?▼

Tagging injects collection tags into existing specs to enable cross-module execution, but original test logic remains intact. The skill reads manifests and adds shared tags without duplicating the underlying test cases.

How do I track which Playwright specs are included in a cross-module test collection?▼

A JSON report is generated to track tag application, scope, and missing specs. This report maps which test cases belong to the curated collection and identifies any gaps in coverage.

What is the best way to execute a curated cross-domain test suite autonomously?▼

Autonomous collection execution is supported once shared tags are injected into the relevant specs. You run the curated Playwright suite directly using the applied tags to trigger grouped cross-module validations.

How do I create a new Playwright collection from existing test manifests?▼

Create a new collection with a descriptive name and the skill aggregates relevant tests into a single tagged suite. It reads existing manifests, applies shared tags, and produces a JSON report tracking the collection scope.