How Claude builds in Taskade Genesis

Asked where the weekly recap should go and who would use the tracker before it built, then built three pages and a coaching automation that wrote a note into a logged match, at a far higher cost than the economical models.

Built the family intake form so it saved every answer and both photos, and it turned away a 12 MB photo before the upload started.

The only build of its test that opened in the light cream look the request asked for.

Added the new teacher question and put the change live. Its class assistant answered questions about the class but could not count the families.

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.

Built the family intake form so it saved every answer and both photos, then added the new teacher question and put the change live.

Built the family intake form twice. Both builds saved every answer and both photos and took the new teacher question, and both showed sample families on the teacher page with no label.

Built the Dota 2 match tracker twice, each with a win-rate trend on the dashboard, and both saved a logged match. One ran wider than a phone screen. In the other the change added a second heroes page beside the one it had already built.

Built the family intake form so it saved every answer and both photos, in a plain look with little of the warm pastel the request asked for. Its open teacher page listed parent phone numbers.

Built a Dota 2 match tracker that rejected every logged match and showed every sample match as a loss, so the dashboard read a 0% win rate.

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.

Built the family intake form so it saved every answer and both photos, and its email automation ran three times. It cost far more than Claude Opus 5.5 on the same request for a lower result.

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.

Built the family intake form in under 4 minutes and took the new teacher question, but the family photo replaced the child photo on every submission.

Built a Dota 2 match tracker that saved logged matches and added a heroes page when asked, but its top-heroes chart showed empty axes.