What problem does it solve? Production code changes to live apps ship without tests that actually verify behavior, so regressions reach real users and green test suites give false confidence through tautological or no-op assertions. ## Core Features & Use Cases - Red-green TDD loop: Write one failing behavior test at a confirmed public seam, then only enough code to pass it, working in vertical slices with Vitest, Jest, or Playwright. - Mode switching: Full TDD for logic, state, and data changes; a screenshot-based visual path via verify-ui-quality for pure CSS, layout, and motion work. - Test quality gates: Detect tautological tests that recompute expected values with the code's own logic and no-op tests that cannot fail against a broken implementation. - Use Case: When adding slot-availability logic to a live booking app, confirm the public seam, write a failing boundary test with hand-verified expected values, then implement only enough code to turn it green. ## Quick Start Use test-shipped-code to TDD the booking availability function in my Next.js app, starting with a failing boundary test.
