A toolchain version in project instructions gives the agent a concrete compatibility target. It does not prevent the model from guessing, so require compilation against that target.

Recorded toolchain → API choice → Build → Availability review
  1. 1Recorded toolchain
  2. 2API choice
  3. 3Build
  4. 4Availability review

Work through the example

Prompt: Use the installed Xcode version recorded here. If an API needs a newer SDK, explain the fallback before editing.

One practical example

Use the prompt above on one small, named part of your app. Before accepting an edit, ask the agent to point to the source or configuration that supports its answer. If it cannot locate that context, resolve the missing input before expanding the task.

In the diagram, each arrow represents a handoff you can inspect. Keep the intermediate result rather than jumping directly to the final claim. For example, a reported finding should retain its location, and an executed check should retain its outcome. This gives the next attempt a concrete starting point and makes a misleading completion message easier to challenge.

Apply it to your project

Prompt: Use the installed Xcode version recorded here. If an API needs a newer SDK, explain the fallback before editing. Then compare the resulting diff with the original request. If it changed a neighboring concern, ask why that change was necessary. Save the result only after the relevant check has run, and record any part that remains unverified.

Evidence and limits

Do not label an API available solely because it appears in a newer guide.

This is an educational guide. Its presence in the series does not certify a completed client-specific lab. The series evidence record separates executed checks from exercises and blocked environments.

Inspect the source used in this lesson.

What to do next

Next: One deep link per screen makes every screenshot automatable