ios-simulator-browser
Skill1 starsChanged 30 days agoNo licenceView on GitHub
Mirror an iOS Simulator into an in-app browser and hot-reload SwiftUI previews from importable Swift packages. Use when previewing SwiftUI in the simulator, mirroring a running simulator in the browser, or live-reloading package-backed previews.
6 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- mohammadchehab/isnadibottheir own version, first seen Nov 15, 2026
- openai/pluginsedited, first seen Oct 13, 2026
- NateBJones-Projects/unlock-ai-workbenchtheir own version, first seen Jul 30, 2026
- btsouth/toolport-studiotheir own version, first seen Jul 28, 2026
- tsouth89/toolport-studiotheir own version, first seen Jul 28, 2026
- robinebers/skillsedited, first seen Jun 25, 2026
Used with
Projects with it also use test-t3-app and test-t3-mobile.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
btsouthSkilltest-t3-app
Launch, retain, and test the T3 Code web app in isolated development environments, including first-try browser authentication with one-time pairing URLs, pairing-token recovery, worktree-safe state directories, cross-turn dev server lifecycle, and direct SQLite inspection or fixture seeding. Use when an agent needs to run T3 locally, iteratively test UI behavior with a human, recover from an expired or consumed pairing token, isolate dev state, or prepare test data in state.sqlite.
Also in 3 projects that use this
btsouthSkilltest-t3-mobile
Launch and test T3 Code Mobile on an iOS Simulator or Android Emulator against disposable local T3 environments, including Metro and dev-client reuse, native rebuild decisions, per-client pairing, seeded projects, semantic UI control, screenshots, and iOS serve-sim streaming. Use after mobile UI or native changes, when reproducing phone or tablet behavior, pairing an emulator to isolated state, or verifying mobile behavior on macOS, Linux, or Windows.
Also in 3 projects that use this
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- openai/plugins★ 7.8k89% same
- robinebers/skills★ 4888% same
Wrote their own version · 4
- btsouth/toolport-studio★ 4same name
- NateBJones-Projects/unlock-ai-workbench★ 4same name
- tsouth89/toolport-studio★ 4same name
- mohammadchehab/isnadibot★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository242 other files it gives its agents.
- vercel-react-best-practices/AGENTS.mdAGENTS.md
- caveman-learn/CLAUDE.mdCLAUDE.md
- Agent Cost ReportSkill
- agent-loop-autoreviewSkill
- agent-loop-browserSkill
- agent-loop-orchestratorSkill
- agent-loop-triageSkill
- animation-vocabularySkill
- anyrouterSkill
- api-and-interface-designSkill
- appkit-interopSkill
- apple-intelligenceSkill
- babysitSkill
- backend-api-patternsSkill
- browser-testing-with-devtoolsSkill
- build-run-debugSkill
- cavecrewSkill
- caveman-commitSkill
- caveman-compressSkill
- caveman-discoverSkill
- caveman-evidence-reviewSkill
- caveman-exploreSkill
- caveman-helpSkill
- caveman-learnSkill
- caveman-manageSkill
- caveman-optimizeSkill
- caveman-reviewSkill
- caveman-setupSkill
- cavemanSkill
- caveman-statsSkill
- ccs-alignSkill
- ce-babysit-prSkill
- ce-bakeoffSkill
- ce-brainstormSkill
- ce-code-reviewSkill
- ce-commit-push-prSkill
- ce-commitSkill
- ce-compound-refreshSkill
- ce-compoundSkill
- ce-debugSkill
- ce-doc-reviewSkill
- ce-dogfoodSkill
- ce-explainSkill
- ce-handoffSkill
- ce-ideateSkill
- ce-noslopSkill
- ce-optimizeSkill
- ce-planSkill
- ce-polishSkill
- ce-povSkill
- ce-product-pulseSkill
- ce-promoteSkill
- ce-proofSkill
- ce-prototypeSkill
- ce-resolve-pr-feedbackSkill
- ce-retuneSkill
- ce-riffrec-feedback-analysisSkill
- ce-setupSkill
- ce-simplify-codeSkill
- ce-skill-workSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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
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.

