When you're making something with Claude's help, you often stumble less on the making itself than on everything around it. Publishing steps, signing up for outside services: you hit a settings screen you've never seen before, can't tell where to press, and get stuck.
Anthropic's official blog features the case of someone who had never written a line of code, all the way to publishing an app built with Claude Code on Apple's App Store. What this person used to get past unfamiliar screens was showing a picture of the screen and asking.
Let's look at what was made, how the screen pictures were used to ask, and how readers can do the same.
Contents
What was made: an app that works "right when you're feeling stressed"
The person featured is Kostiantyn Vlasenko, who has worked for ten years as a project manager at a game company in Ukraine. Until he joined a Claude Code hackathon (a contest where you build something in a short time) in February 2026, he had never written and shipped code.
What he made is Respiro, a stress management app for iPhone. Existing apps only reminded him at set times, like "do some deep breathing at 10 PM," and didn't understand that he was stressed right now. So he came up with an app that picks up signs of stress from devices like his phone and guides him to a breathing exercise at that moment.
From the idea to a version ready for the App Store took just under six weeks. The starting point for what he wanted to make was a problem he himself had.
How it went: when lost on a screen, take a picture and ask "what should I press?"
Making the app was one thing; publishing it was another. Vlasenko had never gone through Apple's developer process for getting an app onto the App Store.
What he did was take a screenshot of the screen where he got stuck and ask Claude, "what should I press here?" He used the same approach to set up outside services for logging and analytics, and says that when he got lost in the settings screens on Meta's site, Claude looked at the screen and guided him where to go. He considers Claude's ability to understand images its most under-appreciated feature.
You don't need to put together a description of the screen in words. When you can't put a screen into words, show it as a picture and ask.
To do the same: show the screen where you got stuck, as is
When you're building from zero, getting stuck on publishing or sign-up screens is unavoidable. If you then try to describe the screen in words, you often can't convey what it says, and the conversation doesn't line up.
In those moments, it's a good idea to take a picture of the screen as is and add one line about what you want to do. For example, the exchange might go like this.
You: (pastes a screenshot of the screen) I want to publish the page I made, and I got to this screen. What should I press here? Claude: Press "Create new" at the top right. On the next screen you'll be asked for a name, so enter the page's name and continue. You: I pressed it, and now I'm on this screen. (pastes a screenshot)
Don't stop at one picture; show the next screen each time you move forward, and you can go step by step even through a process you've never done. When you're lost, take a screenshot before trying to think up an explanation.
Summary
Once you can ask by showing a picture of the screen where you're lost, you can keep going even through unfamiliar steps around the making, like publishing and signing up. Behind someone with no coding experience getting their own app all the way to publication was this approach.
Asking with a picture of the screen isn't limited to publishing. The idea of showing what you see, as is is something you can use again and again, when an error appears or when you want to fix how something looks.
Next time you're stuck in front of a screen, take a screenshot and ask "what should I press here?"