Agents may resolve workspace, scheme, and simulator values differently by project. That is expected.
The requirement is to use FlowDeck commands for the same workflow and report the exact commands executed.
--simulator is optional in many workflows. Use it only when you need explicit targeting (for example, multiple simulators are booted).Build the app
Tell the agent: “Build my app with the current FlowDeck project settings.” Agent should run:Run and watch logs
Tell the agent: “Run my app and stream logs.” Agent should run:Launch a simulator first
Tell the agent: “Boot the first available simulator and open the Simulator app.” Agent should run:UI login smoke test
Tell the agent: “Start UI automation on the booted simulator, fill login, tap Login, wait for Home, and save a screenshot.” Agent should run:Open a deep link
Tell the agent: “Open this deep link in the simulator: myapp://settings/profile” Agent should run:Run tests
Tell the agent: “Run tests with current FlowDeck project settings.” Agent should run:Get machine-readable output
Tell the agent: “Run build and run commands and return JSON output only.” Agent should run:Build a SwiftUI view from a mockup image (tangible)
Tell the agent: “I attached a mockup image. Implement a SwiftUI view to match it, run the app, and give me a current screenshot so I can compare.” Agent should run:run + screen until the visual match is acceptable.
Build a SwiftUI login screen from an image and verify IDs
Tell the agent: “Use this login mockup image, implement the SwiftUI screen, and verifyemailField, passwordField, and loginButton accessibility IDs exist.”
Agent should run:
