Simulating dice rolls as a component for your game

At a glance

Project structure

Source bundle/
├── TabletopKit-Dice/
│   ├── TabletopKitDiceExample/
│   │   ├── DiceSampleApp.swift
│   │   ├── Views/
│   │   │   └── ContentView.swift
│   │   ├── Support/
│   │   │   ├── FaceMappingHelpers.swift
│   │   │   ├── Game.swift
│   │   │   └── Utils.swift
│   │   ├── Equipment/
│   │   │   ├── Die.swift
│   │   │   ├── PlayerSeat.swift
│   │   │   └── RoundTabletop.swift
│   │   └── Interaction/
│   │       └── DiceInteraction.swift
│   └── Packages/
│       └── RealityKitContent/
│           ├── Sources/
│           │   └── RealityKitContent/
│           │       └── RealityKitContent.swift
│           └── Package.swift
└── Configuration/
    └── SampleCode.xcconfig

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 9 source declaration(s).

Overall architecture

flowchart LR
    N1["DiceSampleApp"]
    N2["ContentView"]
    N3["TabletopKit APIs"]
    N1 --> N2
    N2 --> N3

Reference code

TabletopKit-Dice/TabletopKitDiceExample/DiceSampleApp.swift:10 — architecture anchor

@MainActor
@main
struct DiceSampleApp: App {
    // ...
}

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 TabletopKit.

Ownership and state

classDiagram
    DiceSampleApp *-- Game : game
    ContentView *-- Bool : predeterminedOutcome
    ContentView *-- Bool : tossAllDice
    FaceMap *-- Dictionary : faceToValue

Ownership evidence

TabletopKit-Dice/TabletopKitDiceExample/DiceSampleApp.swift:12 — stored dependency or nearest verified ownership anchor

    @State var game = Game()

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.

Class and protocol design

TabletopKit-Dice/TabletopKitDiceExample/Support/FaceMappingHelpers.swift:44 — representative type boundary

protocol TossableFaceMap {
    func value(for face: any TossableRepresentation.TossableFace) -> Int?
    func face(for value: Int) -> (any TossableRepresentation.TossableFace)?
    var values: Set<Int> { get }
}

No local protocol conformance is claimed as protocol-oriented design; external framework conformances are listed only as dependencies.

Access control

Reference code

TabletopKit-Dice/Packages/RealityKitContent/Sources/RealityKitContent/RealityKitContent.swift:11 — representative boundary

public let realityKitContentBundle = Bundle.module

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: DiceSampleApp; View: ContentView.
• Protocols: TossableFaceMap.
• Methods: value, face, handID, diceID, restingOrientation, calculateScore, faceWithHighestScore, tetrahedronDie.
• Files: TabletopKit-Dice/TabletopKitDiceExample/DiceSampleApp.swift, TabletopKit-Dice/TabletopKitDiceExample/Views/ContentView.swift, TabletopKit-Dice/TabletopKitDiceExample/Equipment/Die.swift, TabletopKit-Dice/TabletopKitDiceExample/Equipment/PlayerSeat.swift, TabletopKit-Dice/TabletopKitDiceExample/Equipment/RoundTabletop.swift, TabletopKit-Dice/TabletopKitDiceExample/Interaction/DiceInteraction.swift.

Architecture takeaways

• DiceSampleApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches RealityKit, TabletopKit, SwiftUI, RealityKitContent 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.
• The source does not justify labeling the design protocol-oriented.

Source map

• Official Apple documentation