Local references provide project-specific context and reproducible examples. When they lack an answer, disclose the gap and distinguish external research from repository guidance.

Focused local search → Read source section → Identify gap → Check primary source
  1. 1Focused local search
  2. 2Read source section
  3. 3Identify gap
  4. 4Check primary source

Work through the example

Prompt: Search the local library for this API first; cite the relevant file and say if the answer needs current Apple documentation.

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: Search the local library for this API first; cite the relevant file and say if the answer needs current Apple documentation. 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

A local catalog is dated and is not Apple's proprietary framework implementation.

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: What to put in .gitignore for agent-built Xcode projects