How Claude builds in Taskade Genesis

Opened its own app and checked the assistant's answers — the only model to verify its work this way.

Most carefully finished result, with eight minor items left.

Built a contacts database instead of the requested sign-up form after two stalls.

Four attempts stalled before the sign-up form was completed.

Stopped after asking its questions on the client sign-up form, and wrote the plan instead of the app.

Typed an 81-row scoring rubric and a 36-field sign-up table, then stopped at an approval prompt before writing the app.

Built a three-page match tracker whose dashboard reported zero matches over the eight matches it had entered itself.

Set the design high-water mark with a polished, consistent interface.

Created the fullest workspace, with an assistant that understood its contents.

The most complete client sign-up build of the test: a five-page form, every answer saved, and the scoring automation graded the submission on its own.

Best-executed match tracker of the test, without a single failed build action, at by far the highest cost.

Finished the client sign-up form with all 32 questions in the customer's wording, 31 word for word, five pages, and a scoring automation that saved its result.

Decided two open points in the brief and named both decisions in its closing summary.

Found the problem while building, repaired it, and then finished — the only model in the test to recover on its own.

Fastest build of the test, but it left out the weekly recap automation the brief asked for.