agentsclimarketplace

Simulator screenshot reviewer

Skill 7vibex/swiftui-developer-kit/.agents/skills/simulator-screenshot-reviewer

Codex skill pack for SwiftUI, SwiftData, Xcode debugging, app audits, screenshots, accessibility, Liquid Glass, and App Store release workflows.

Install
npx -y skills add 7vibex/swiftui-developer-kit --skill simulator-screenshot-reviewer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Review user-approved iOS/iPadOS Simulator screenshots for SwiftUI layout, clipping, spacing, readability, visual hierarchy, and screenshot-based UI feedback.

SKILL.md

2.1 KB, as published. Nobody here has run it

Simulator Screenshot Reviewer

Capture and review Simulator screenshots only after user approval.

Required Questions Before Capture

Ask:

  • Is Simulator open?
  • Which screen should be captured?
  • Is anything sensitive/private visible?

Do not capture until the user confirms the target screen and privacy state.

References

  • Use references/privacy-checklist.md before capture.
  • Use references/screenshot-workflow.md for capture and inventory flow.
  • Use references/ui-review-checklist.md for review.
  • Use references/output-contract.md for the report.

Supported Capture Modes

  • Appshots, if available and approved.
  • Shell fallback with scripts/capture-simulator-screenshot.sh.
  • Manual screenshots attached by the user.

Workflow

  1. Confirm Simulator is open and the intended screen is visible.
  2. Confirm no sensitive/private information is visible.
  3. Ask for the screen name.
  4. Capture with the approved method.
  5. Create or update screenshot inventory.
  6. Review visual hierarchy, layout, readability, clipping, spacing, and accessibility risks.
  7. Ask for follow-up screenshots only when they materially affect the review.

Do Not Use When

  • The user has not approved capture or supplied screenshots.
  • The task can be answered from code, build logs, or release metadata without visual evidence.

Done When

  • Capture consent, screen names, and privacy state are recorded or screenshots are user-supplied.
  • Layout, clipping, readability, hierarchy, spacing, and accessibility risks are reviewed per screen.
  • Output distinguishes screenshot-backed confidence from missing code or runtime evidence.

Output

Use references/output-contract.md.

Follow ../../../docs/skill-quality-standard.md and compare ../../../examples/skill-outputs/simulator-screenshot-reviewer-bad-output.md with ../../../examples/skill-outputs/simulator-screenshot-reviewer-good-output.md.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.