elixir-tdd

Enforce test-first development in Elixir and Phoenix projects.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/hwatkins/my-skills --skill elixir-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elixir-tdd
Source: https://github.com/hwatkins/my-skills/tree/main/skills/elixir-tdd
Command: npx skills add https://github.com/hwatkins/my-skills --skill elixir-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Elixir TDD Enforcement skill closes the gap between writing tests and implementing code by mandating failing tests precede changes, promoting robust, well-tested features and bug fixes.

Core Features & Use Cases

  • Red/Green/Refactor workflow: write a failing spec first, then implement just enough code to pass, and refine.
  • Testing discipline across the stack: unit tests, integration tests, and LiveView/test patterns; support for Mox mocks and StreamData property tests.
  • Real-world adoption: teams that want consistent test coverage, maintainable code, and faster safe releases.

Quick Start

Begin by writing a failing test that describes the desired behavior, then implement the minimal code to pass the test and refactor.

Frequently Asked Questions about elixir-tdd

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

FAQPage Schema
How do I enforce test-first development in Elixir and Phoenix projects?

Test-first development in Elixir and Phoenix is enforced by mandating a failing test before any implementation code is written. This red/green/refactor workflow ensures robust design and maintainable features.

Can I use Mox for mocking and StreamData for property-based testing with TDD in Phoenix?

Yes, TDD in Phoenix supports Mox for mocks and StreamData for property-based testing. These patterns integrate directly into the test-first workflow to ensure thorough testing across the stack.

What is the best way to structure LiveView testing workflows in Elixir?

LiveView testing workflows in Elixir benefit from a disciplined TDD approach where you write a failing test describing the desired behavior first, then implement minimal code to pass and refactor.

Does TDD discipline work for both unit and integration tests in Elixir applications?

Yes, TDD discipline applies across the full testing stack in Elixir, covering unit tests, integration tests, and LiveView patterns to deliver consistent test coverage and maintainable code.

Why should my team adopt strict test-first TDD for Elixir releases?

Strict test-first TDD for Elixir promotes robust, well-tested features and bug fixes, leading to consistent test coverage, maintainable code, and faster safe releases for teams.

How do I start a red green refactor cycle for an Elixir feature?

To start a red/green/refactor cycle in Elixir, begin by writing a failing test that describes the desired behavior, implement just enough code to pass it, and then refine the implementation.