test-helpers

Generate engine-specific test helper libraries from existing test patterns.

Updated May 13, 2026
One-click install
npx skills add https://github.com/FrancisVarga/the-dream-machine --skill test-helpers-francisvarga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-helpers
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/test-helpers
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill test-helpers-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing repetitive test setup, assertions, factories, and mocks slows down development and leads to inconsistent test style across the project.

Core Features & Use Cases

  • Engine-aware helper generation: Detects the configured engine, language, and testing framework, then creates helpers that match the project’s test ecosystem.
  • Pattern-aligned scaffolding: Scans existing tests to mirror the repository’s current setup/teardown, assertion, object creation, and mocking conventions.
  • System-specific factories: Optionally generates per-system helper factories based on in-scope GDD/system definitions so new tests start with correct domain structure.
  • Run-mode options: Supports generating for a specific system, all systems, or scaffolding only the base helper library.
  • Safety-oriented behavior: Never overwrites existing helper files; it reports and skips any files that already exist.

Quick Start

Run /test-helpers scaffold to create the base tests/helpers library if it does not exist yet.

Frequently Asked Questions about test-helpers

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

FAQPage Schema
How do I generate test helpers that match my existing test framework and repository conventions?▼

Test helper generation detects your project's engine, language, and testing framework, then scans existing tests to mirror current setup, teardown, assertion, and mocking patterns. It produces a tailored tests/helpers/ directory that aligns with your repository's test conventions.

What is the best way to reduce repetitive test setup boilerplate across my project?▼

Generating engine-specific test helpers reduces repetitive setup boilerplate by creating consistent factory functions and mocks tailored to your test suite. Scaffolding mode builds a base helper library that standardizes object creation and assertions across the project.

Can I generate factories and mocks for a specific system instead of all systems at once?▼

Yes, test helper generation supports run-mode options for generating a specific system, all systems, or scaffolding only the base helper library. System-specific factories use in-scope system definitions so new tests start with correct domain structure.

Does generating test scaffolding overwrite my existing helper files?▼

No, test helper generation never overwrites existing helper files. It applies safety-oriented behavior by reporting and skipping any files that already exist in the tests/helpers/ directory, preserving your current repository conventions.

How do I bootstrap a test helpers directory if it does not exist yet?▼

Run the scaffold mode to create the base tests/helpers library if it does not exist yet. This bootstraps the test framework by generating the foundational helper directory structure without overwriting existing files.