Results for “test-driven-development”

Use before feature, bugfix, or refactor implementation when behavior can be tested; enforces Red-Green-Refactor discipline.

The English summary is being prepared. Showing the original description.

TDD: enforce RED-GREEN-REFACTOR, tests before code.

The English summary is being prepared. Showing the original description.

Teststrategie-Berater für Softwareprojekte — wählt die richtigen Teststufen (Unit/Integration/System/Abnahme), Testarten (funktional, nicht-funktional, änderungsbezogen) und Testentwurfsverfahren (Äquivalenzklassen, Grenzwerte, Entscheidungstabellen, explorativ) für die jeweilige Situation und SDLC-/CI-Phase, inkl. Testpyramide, CI/CD-Gates, Shift-Left und Best Practices. Nutze diesen Skill IMMER, wenn Tests geschrieben, geplant, priorisiert oder bewertet werden sollen — bei "schreibe Tests", "Teststrategie", "Testplan", "Testkonzept", "was/wie soll ich testen", "welche Tests fehlen", "Testabdeckung verbessern", "QA aufsetzen", Fragen zu Regression/Smoke/Sanity/Last/Stress/Security-Tests oder beim Einrichten einer Test-Pipeline — auch wenn "Test" nur beiläufig fällt. Abgrenzung — für die TDD-Schleife selbst superpowers:test-driven-development, für Bug-Diagnose bugfix-protocol, für systematische Bug-Suche bugsweep nutzen.

The English summary is being prepared. Showing the original description.

Write the test first, watch it fail, write minimal code to pass

The English summary is being prepared. Showing the original description.

Use when implementing any feature or bugfix, before writing implementation code

The English summary is being prepared. Showing the original description.

Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

The English summary is being prepared. Showing the original description.

Use when implementing any feature or bugfix, before writing implementation code

The English summary is being prepared. Showing the original description.

TDD: enforce RED-GREEN-REFACTOR, tests before code.

The English summary is being prepared. Showing the original description.

Use when implementing any feature or bugfix, before writing implementation code

The English summary is being prepared. Showing the original description.

Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.

The English summary is being prepared. Showing the original description.

Implement test-driven development (TDD) workflow using the red-green-refactor cycle. Use when writing new features, fixing bugs, or refactoring existing code. Always write the failing test first, then implement minimal code to pass, then refactor. Essential for ensuring code reliability, preventing regressions, improving design through testability requirements, documenting expected behavior through tests, enabling confident refactoring, and maintaining high code quality standards throughout the development process.

The English summary is being prepared. Showing the original description.

Ground framework-specific implementation in official documentation — detect stack versions, fetch authoritative docs, implement cited patterns, cite sources. Load when building with a library or framework where API correctness matters, when the user wants verified or documented code, or before writing framework code from memory. Also triggers on "source driven development", "cite the docs", "check official documentation", "verify against docs", "don't hallucinate APIs". Not for pure logic or renames. Pairs with feature-spec and test-driven-development.

The English summary is being prepared. Showing the original description.

Apply the Red-Green-Refactor cycle to software development. Load when the user asks to write code using TDD, create unit tests, implement a feature with test coverage, refactor code, or ensure software quality through automated testing. Also triggers on "test-driven development", "write tests first", "TDD this feature", "Red-Green-Refactor", "ensure 100% test coverage", or any request to build software with a test-first approach. Supports unit, integration, and end-to-end testing strategies.

The English summary is being prepared. Showing the original description.

Deliver multi-file changes in thin vertical slices — implement, test, verify, commit, repeat. Load when implementing a feature from a plan, building across more than one file, refactoring, or when tempted to land a large change in one pass. Also triggers on "incremental implementation", "vertical slice", "thin slice", "one slice at a time", "don't do it all at once". Routes single-file fixes to direct execution. Pairs with test-driven-development and git-workflow-and-versioning.

The English summary is being prepared. Showing the original description.

Write acceptance tests before unit tests to ensure you're building the right thing

The English summary is being prepared. Showing the original description.

Use when implementing any feature or bugfix, before writing implementation code

The English summary is being prepared. Showing the original description.

TDD: enforce RED-GREEN-REFACTOR, tests before code.

The English summary is being prepared. Showing the original description.

Run a bounded red-green-refactor feedback loop only when the user explicitly requests TDD, accepts reproduction-first proof for a bug, or an accepted high-risk behavior specifically requires red/green evidence; do not trigger for every logic, bug, behavior, or implementation change.

The English summary is being prepared. Showing the original description.