vocello-macos-ui
Skill388 starsChanged 21 days agoMITView on GitHub
Validate macOS native UI changes through repository XCUITest lanes, including smoke, localization and relevant performance acceptance.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- website/CLAUDE.mdCLAUDE.md
- vocello-benchmarkSkill
- vocello-debugSkill
- vocello-device-diagnosticsSkill
- vocello-ios-validationSkill
- vocello-release-readinessSkill
- vocello-ui-autonomySkill
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
- Very specific: line 11
Read docs/reference/native-engineering.md, docs/reference/testing-runbook.md and relevant Axiom macOS/testing guidance.
- Very specific: line 20
Keep the run ID, raw log, result bundle, ledgers and failed evidence.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
macOS UI validation
Arguments: $ARGUMENTS
Read docs/reference/native-engineering.md, docs/reference/testing-runbook.md and relevant Axiom
macOS/testing guidance. Choose the smallest lane from scripts/ui_test.sh help; compile-only work
uses scripts/build_ui_test_bundles.sh macos.
Join/stop workers and commit source before source-bound UI/performance evidence. Use the host lock,
load/memory checks and installed assets; if tracking is unavailable explicitly declare lead-only
after joining all workers. Run scripts/ui_test.sh macos <lane> <options> from the repository root.
Repository XCUITest is the only automated native UI evidence; use genuine controls and stable
identifiers. Computer use covers what XCUITest cannot, between lanes and never while one runs
(/vocello-ui-autonomy). After the lane, review <run>/screenshots/index.json.
Keep the run ID, raw log, result bundle, ledgers and failed evidence. Triage the finished directory
with scripts/dev.sh triage <run-directory> --json or the read-only vocello-xcresult-triage agent;
report limits. Reruns require a reason and new ID.
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.

