meow:testing

Enforce red-green-refactor TDD workflows with validation scripts for unit and integration tests.

14|2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-testing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meow:testing
Source: https://github.com/ngocsangyem/MeowKit/tree/main/.claude/skills/meow%3Atesting
Command: npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Writes and enforces a disciplined testing workflow by guiding teams through RED-GREEN-REFACTOR, validation steps, and visual QA.

Core Features & Use Cases

  • Enforces failing-first test development with clear, repeatable steps.
  • Provides references to canonical TDD guidance and validation scripts for quality gates.
  • Supports integration with unit/integration tests and light-weight validation before shipping.

Quick Start

Invoke the testing toolkit to guide a feature through RED, GREEN, and REFACTOR with clear practices.

Frequently Asked Questions about meow:testing

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

FAQPage Schema
How does the red-green-refactor TDD workflow actually work?▼

Yes, you can enforce disciplined TDD across both unit and integration testing. The workflow guides teams through failing-first test development, applying minimal code implementation and refactoring practices to both test scopes.

How do I automate TDD validation steps before shipping code?▼

Automate TDD validation by applying optional validation scripts that act as quality gates. These scripts validate tests and code quality, ensuring light-weight validation passes before shipping your feature through the red-green-refactor cycle.

Do I need clear frontmatter metadata to use this TDD workflow?▼

Yes, clear frontmatter metadata is required to guide the TDD workflow. The testing toolkit uses this metadata alongside references to canonical TDD guidance to enforce red-green-refactor patterns and integration testing practices.

What is the best way to structure test development for new features?▼

The best way to structure test development is through red-green-refactor. Invoke the testing toolkit to guide a feature through writing failing tests first, implementing minimal code, and refactoring, with clear repeatable steps for quality assurance.

Are there limitations to using automated TDD patterns for validation?▼

Automated TDD patterns focus specifically on unit and integration tests with light-weight validation. The workflow requires strict adherence to the red-green-refactor sequence and clear frontmatter metadata, which may constrain rapid prototyping without test coverage.