Use when delivering Nabatable full-stack changes across Next.js UI, hooks, routes, server logic, and tests, especially when deciding between RED-first feature work, verification-first regression work, and test-only changes.
This skill turns the repo's repeated review feedback into a clearer delivery workflow.
Ship Nabatable changes through the canonical implementation path with the right level of test and verification rigor for the kind of change being made.
verification.md.$nabatable-ui-proof for UI changes that need browser evidence.