agentleFS
Sign inStart free
simiancraftsimiancraft/simiancraft-skills/skills/ios-simulator-flow-evidence/SKILL.md

ios-simulator-flow-evidence

Skill8 starsChanged 5 months agoMITView on GitHub

Capture proof of a driven iOS-simulator flow: vision-verifiable screenshots, video (mp4), and a manifest tying steps to artifacts, plus an honest list of what a simulator cannot do (deliver a push, use a real camera, place a call, fully observe the network). Produces artifacts to a contract that a separate GitHub-presentation skill consumes; this skill owns extraction, not publishing. Sits beside ios-simulator; project-agnostic. Use for "capture evidence of an iOS flow" or "record the simulator".

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All capture comes from the device framebuffer, so the Simulator window's size and position never matter (see ios-simulator …

    line 35
  2. Very specific:

    If a flow's proof depends on any of these, list it under the manifest's deviceOnly (see references/flow-manifest.md).

    line 58

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

iOS Simulator Flow Evidence (extraction, not publishing)

Owns getting artifacts OUT of the simulator. The separate prove-work-on-github skill consumes them; the seam is references/artifact-contract.md. This skill produces the bundle; it does not publish it.

The three artifact kinds

A driven flow (see ios-simulator references/driving.md) leaves three kinds of proof:

  1. A sequence of screenshots (references/screenshots.md): one PNG per meaningful step, each vision-verified to show the state it claims. The default, most reviewable evidence.
  2. A video (references/video.md): the whole flow as one MP4 or MOV. An animated GIF is not a native output; it is a post-process that needs a separate tool (see that file).
  3. A manifest (references/flow-manifest.md): a machine-readable index tying each step to its artifact and the state it proves, so a reviewer (or the presentation skill) can read the bundle without re-running the flow.

All capture comes from the device framebuffer, so the Simulator window's size and position never matter (see ios-simulator references/capture.md); never resize or full-screen it.

The contract

Everything this skill emits conforms to references/artifact-contract.md: stable names, known formats (PNG, MP4 or MOV), and the manifest shape. The consumer prove-work-on-github relies on that contract; do not break it without updating the presentation side.

Honest can't-do list (simulator limits)

Evidence from a simulator proves UI, navigation, wiring, and state, not device fidelity. A simulator cannot:

  • vend a native APNs device token (getDevicePushTokenAsync), so real remote-push registration is a device pass; a simulator can still display a payload via xcrun simctl push and receive a remote push on Xcode 14+ (see expo-ios-simulator references/known-prompts.md for the push-token alert this raises);
  • produce real camera or microphone frames (no physical sensors);
  • place a phone call or send a carrier SMS;
  • fully reproduce on-device network conditions (no cellular radio; bandwidth and latency are the host's, not a real handset's).

If a flow's proof depends on any of these, list it under the manifest's deviceOnly (see references/flow-manifest.md); it is a device pass, not something the simulator evidence covers.

Where to go

  • references/screenshots.md: the per-step PNG sequence and vision-verification.
  • references/video.md: recording MP4 / MOV, and the GIF post-process and its dependency.
  • references/artifact-contract.md: the bundle shape the external skill consumes.
  • references/flow-manifest.md: the step-to-artifact manifest.

Out of scope

Publishing or presenting artifacts -> the separate prove-work-on-github skill. Driving the flow itself -> ios-simulator and expo-ios-simulator.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free