skills.rest
vchelaru
vchelaruCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

engine-tdd

Enforce test-first discipline for FlatRedBall2 engine changes under src/.

11|3|Updated Feb 28, 2026
Search Tags:#testing#regression#quality-assurance#test-first#engine#flatredball2
One-click install
npx skills add https://github.com/vchelaru/FlatRedBall2 --skill engine-tdd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engine-tdd
Source: https://github.com/vchelaru/FlatRedBall2/tree/main/.claude/skills/engine-tdd
Command: npx skills add https://github.com/vchelaru/FlatRedBall2 --skill engine-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a test-first discipline for FlatRedBall2 engine changes, ensuring a failing test exists before modifying src/ to prevent silent regressions.

Core Features & Use Cases

  • Enforces that a failing test exists before any engine-related change.
  • Applies to edits under src/ for bug fixes or new features, across engine base classes and APIs.
  • Useful for maintaining stability when refactoring or iterating on engine behavior.

Quick Start

Create a failing test in tests/FlatRedBall2.Tests for the intended src/ change, run it to observe failure, then implement the fix.

Frequently Asked Questions about engine-tdd

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

FAQPage Schema
How do I enforce test-first discipline for FlatRedBall2 engine changes?▼

To enforce test-first discipline for FlatRedBall2 engine changes, you must create a failing test in the tests/FlatRedBall2.Tests directory before modifying any source files under src/.

Why do I need a failing test before fixing a bug in the engine source?▼

You need a failing test before fixing a bug in the engine source to prevent silent regressions. It validates the issue exists and ensures your source code edit actually resolves the failing behavior.

What is the best way to add a new feature to FlatRedBall2 without causing regressions?▼

The best way to add a new feature without causing regressions is to write a failing test in tests/FlatRedBall2.Tests first, run the test suite to observe the failure, then implement the source edit under src/.

Does test-first development apply to all file edits under the src/ directory?▼

Yes, test-first development applies to all edits under src/ for either bug fixes or new features, ensuring a failing test exists in tests/FlatRedBall2.Tests before you implement any source code changes.

Can I refactor FlatRedBall2 engine base classes without writing tests first?▼

No, you should not refactor FlatRedBall2 engine base classes without writing tests first. Maintaining a failing test before implementing source edits is required to maintain stability and validate changes via the test suite.

Related Skills

Explore More Software Engineering Skills→
morodomimorodomi
8

tdd-red

Generate failing tests and coordinate parallel workers for TDD RED phases.

Community
Intermediate
kaynetikkaynetik
1

tdd-red-green-refactor

Write failing tests before production code to drive minimal fixes.

Community
Intermediate
mysticfallmysticfall
1

godot-asset-ops

Modify Godot scenes and resources through engine APIs while preserving node ownership.

Community
Advanced
jyang234jyang234

coding

Enforce coding standards and best practices across software development tasks.

Community
Intermediate