Building a working tool without writing code

Building without code does not mean building without rigour. If anything it raises the bar on the parts that were always hard: saying exactly what the tool must do, and checking honestly whether it does it.

Start from the mapped step you want to change, not from the tool. Write the smallest useful version of the answer, wire it up with the AI stack available to you, and put a real input through it. Then break it on purpose to see where it fails.

The skill that carries is specification and judgement. The person who can describe a step precisely and test it without fooling themselves will out-build the person who simply prompts faster.