Getting Started with AI-Augmented Coding in iOS

Hello, welcome to the first demo in lesson two. In this lesson, we’ll go through the starter project with the help of AI to understand the structure, architecture, and have an idea on how it works.

In the previous lesson, when you set up Claude in Xcode, you asked it to give you a brief on the project. Let’s pick up from there. Feel free to ask the AI in any wording you want, as it shouldn’t matter.

Before we get into it, it’s very important to understand that the responses from the AI agent in this demo most likely won’t match what you get if you run the same prompt. You shouldn’t worry about it. What’s important is to understand how to drive a conversation or a task with an AI agent to get the output you need. Also, it doesn’t matter which model you’re using, thus the demos in this lesson will not specify an AI model to use to accomplish the task.

From the last conversation, the AI gave a brief on the project as requested, but for me, this is not enough. I want to understand a little more on the application architecture and the views. So let’s ask it for that information. Use this as a prompt:

Give me more details on the architecture and the views, use code snippets from the project to help explain it.

As you can see, it’s going through the project files and starting to give information on the architecture, some information on how the game phases work, the enum of the game phases, the views, each of them one by one as found from the game phases. And it’s even specifying some views consist of other sub-views. And at the end, it’s providing a summary and some shared information about some styling.

How about if we ask for a little bit more information on how the views work? Like maybe try this prompt:

Give me a graph on how the views navigate to each other.

So with that, you’d have a better understanding of how the navigation works. Let’s put this prompt.

Again, remember, it’s very likely that the responses you get from your prompts will look a little differently. So from here, it’s not a perfect job, but it gives an idea. Here’s the graph. If I click it, it expands a bit more from Xcode, and it’s showing, as requested, a diagram of how the views navigate to each other based on the phases, the choices for next clue or submit a guess, and at the end, it reaches the summary view.

Click outside, we go back. Here’s more information about the transitions and a bit more info about the footer view. For now, this is enough. Feel free to ask whatever comes to your mind about a specific view, something in the project itself. But for now, this is enough, and in the next demo, you’ll start implementing one of the missing features, the streak mode.

The current application only has classic mode implemented. There’s a little bit more information in the code about streak and blitz, but both are not implemented yet. So the next demo will show you how to use Agentic AI to implement the streak feature, and the one after that, you’ll implement the blitz feature, but not through Xcode, but through Cursor IDE. See you in the next demo.