Generate dynamic game content with guided generation and tools

At a glance

Project structure

Source bundle/
└── FoundationModelsCoffeeGame/
    └── FoundationModelsCoffeeGame/
        ├── FoundationModelsCoffeeGameApp.swift
        ├── GenerateDialog/
        │   ├── Characters.swift
        │   ├── DialogBoxView.swift
        │   └── DialogEngine.swift
        ├── GameView.swift
        ├── GenerateEncounters/
        │   ├── EncounterEngine.swift
        │   ├── CustomerProfileView.swift
        │   └── EncounterView.swift
        ├── MainMenu/
        │   ├── CloudsBackgroundView.swift
        │   └── MainMenuView.swift
        └── OrderCoffee/
            ├── CoffeeDrink.swift
            └── CoffeeOrderView.swift

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Swift.
• The verified tree contains 4 project/configuration file(s) and 40 source declaration(s).

Overall architecture

flowchart LR
    N1["FoundationModelsCoffeeGameApp"]
    N2["MainMenuView"]
    N3["DialogEngine"]
    N4["FoundationModels APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

FoundationModelsCoffeeGame/FoundationModelsCoffeeGame/FoundationModelsCoffeeGameApp.swift:10 — architecture anchor

@main
struct FoundationModelsCoffeeGameApp: App {
    var body: some Scene {
        WindowGroup {
            MainMenuView()
                #if os(iOS)
                    .statusBar(hidden: true)
                #endif
        }
    }
}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into Foundation Models.

Ownership and state

classDiagram
    Barista *-- UUID : id
    CustomerLisa *-- UUID : id
    GeneratedCustomer *-- UUID : id
    GeneratedCustomer *-- String : displayName

Ownership evidence

FoundationModelsCoffeeGame/FoundationModelsCoffeeGame/GenerateDialog/Characters.swift:29 — stored dependency or nearest verified ownership anchor

struct Barista: Character {
    let id = UUID()
    // ...
}

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Concurrency, scheduling, and thread safety

Evidence limit: actor isolation, async/await, or Task creation does not by itself prove background-thread execution; Sendable conformance alone does not prove thread-safe mutation.

@MainActor/MainActor.run, DispatchQueue.main, and RunLoop.main are reported as distinct isolation, queue, and event-loop mechanisms. A plain Task is kept separate from Task.detached; neither is labeled as a background thread.

Reference code

FoundationModelsCoffeeGame/FoundationModelsCoffeeGame/GameView.swift:60 — representative execution boundary

        Task {
            // ...
                    let npc = try await encounterEngine.generateNPC()
            // ...
        }

State propagation, frameworks, and dependencies

Evidence limit: an import proves a source-level compilation dependency at the cited line; it does not prove runtime use, architectural adoption, or whether a Swift package is a direct application dependency.

receive(on:) describes downstream delivery scheduling, while subscribe(on:) describes upstream subscription/request/cancel scheduling. An import Combine alone establishes neither behavior nor a Store, reducer, Redux, or other application architecture.

Class and protocol design

FoundationModelsCoffeeGame/FoundationModelsCoffeeGame/GenerateDialog/Characters.swift:11 — representative type boundary

protocol Character: Identifiable {
    var id: UUID { get }
    // ...
}

The source explicitly defines local protocol relationships: Barista → Character, CustomerLisa → Character, GeneratedCustomer → Character.

Access control

Reference code

FoundationModelsCoffeeGame/FoundationModelsCoffeeGame/GenerateDialog/DialogBoxView.swift:25 — representative boundary

struct DialogBoxView: View {
    // ...
    @FocusState private var isFocused: Bool
    // ...
}

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Naming conventions

• Types: App: FoundationModelsCoffeeGameApp; Engine: DialogEngine, EncounterEngine; Generator: RandomCustomerGenerator; Scene: CoffeeShopScene; View: CloudsBackgroundView, CoffeeOrderView, CustomerProfileView, DialogBoxView, EncounterView.
• Protocols: Character.
• Methods: showDialog, generateDreamCustomer, triggerEncounter, body, generateNPC, judgeDrink, createClouds, startCloudAnimation.
• Files: FoundationModelsCoffeeGame/FoundationModelsCoffeeGame/FoundationModelsCoffeeGameApp.swift, FoundationModelsCoffeeGame/FoundationModelsCoffeeGame/GameView.swift, FoundationModelsCoffeeGame/FoundationModelsCoffeeGame/GenerateEncounters/EncounterEngine.swift, FoundationModelsCoffeeGame/FoundationModelsCoffeeGame/MainMenu/CloudsBackgroundView.swift, FoundationModelsCoffeeGame/FoundationModelsCoffeeGame/MainMenu/MainMenuView.swift, FoundationModelsCoffeeGame/FoundationModelsCoffeeGame/OrderCoffee/CoffeeDrink.swift.

Architecture takeaways

• FoundationModelsCoffeeGameApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches SwiftUI, FoundationModels, SpriteKit, Contacts through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• Local protocol relationships provide an explicit substitution boundary.

Source map

• Official Apple documentation