Fetches axiom-xctest-automation from charleswiltgen/axiom and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/axiom-xctest-automation
Restart Cursor to activate axiom-xctest-automation. Access via /axiom-xctest-automation in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Localized strings change → Use accessibilityIdentifier instead
Deeply nested views → Use shortest possible query
Dynamic content → Use generic query or identifier
// BAD - Fragile queriesapp.buttons["Login"]// Breaks with localizationapp.tables.cells.element(boundBy:0).buttons.firstMatch // Too specific// GOOD - Stable queriesapp.buttons["loginButton"]// Uses identifierapp.tables.cells.containing(.staticText, identifier:"itemTitle").firstMatch
Waiting Strategies
Never Use sleep()
// BAD - Hardcoded waitsleep(5)XCTAssertTrue(app.buttons["submit"].exists)// GOOD - Condition-based waitlet submitButton = app.buttons["submit"]XCTAssertTrue(submitButton.waitForExistence(timeout:5))
Wait Patterns
// Wait for element to appearfuncwaitForElement(_ element:XCUIElement, timeout:TimeInterval=10)->Bool{ element.waitForExistence(timeout: timeout)}// Wait for element to disappearfuncwaitForElementToDisappear(_ element:XCUIElement, timeout:TimeInterval=10)->Bool{let predicate =NSPredicate(format:"exists == false")let expectation =XCTNSPredicateExpectation(predicate: predicate, object: element)let result =XCTWaiter.wait(for:[expectation], timeout: timeout)return result ==.completed
}// Wait for element to be hittable (visible AND enabled)funcwaitForElementHittable(_ element:XCUIElement, timeout:TimeInterval=10)->Bool{let predicate =NSPredicate(format:"isHittable == true")let expectation =XCTNSPredicateExpectation(predicate: predicate, object: element)let result =XCTWaiter.wait(for:[expectation], timeout: timeout)return result ==.completed
}// Wait for text to appear anywherefuncwaitForText(_ text:String, timeout:TimeInterval=10)->Bool{ app.staticTexts[text].waitForExistence(timeout: timeout)}
Async Operations
// Wait for network responsefuncwaitForNetworkResponse(){let loadingIndicator = app.activityIndicators["loadingIndicator"]// Wait for loading to start_= loadingIndicator.waitForExistence(timeout:5)// Wait for loading to finish_=waitForElementToDisappear(loadingIndicator, timeout:30)}
Test Structure
Setup and Teardown
classLoginTests:XCTestCase{var app:XCUIApplication!overridefuncsetUpWithError()throws{ continueAfterFailure =false app =XCUIApplication()// Reset app state for clean test app.launchArguments =["--uitesting","--reset-state"] app.launchEnvironment =["DISABLE_ANIMATIONS":"1"] app.launch()}overridefunctearDownWithError()throws{// Capture screenshot on failureif testRun?.failureCount ??0>0{let screenshot =XCUIScreen.main.screenshot()let attachment =XCTAttachment(screenshot: screenshot) attachment.name ="Failure Screenshot" attachment.lifetime =.keepAlways
add(attachment)} app.terminate()}}
Test Method Pattern
functestLoginWithValidCredentials()throws{// ARRANGE - Navigate to login screenlet loginButton = app.buttons["showLoginButton"]XCTAssertTrue(loginButton.waitForExistence(timeout:5)) loginButton.tap()// ACT - Enter credentials and submitlet emailField = app.textFields["emailTextField"]XCTAssertTrue(emailField.waitForExistence(timeout:5)) emailField.
Implementation Guide
Prerequisites
›Claude Desktop or compatible AI client with skill support
›Clear understanding of task or problem to solve
›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
1Install skill using provided installation command
2Test with simple use case relevant to your work
3Evaluate output quality and relevance
4Iterate on prompts to improve results
5Integrate into regular workflow if valuable
Common Pitfalls
⚠Expecting perfect results without iteration
⚠Not providing enough context in prompts
⚠Using skill for tasks outside its intended scope
⚠Accepting outputs without review and validation
Best Practices
✓ Do
+Start with clear, specific prompts
+Provide relevant context and constraints
+Review and refine all outputs before using
+Iterate to improve output quality
+Document successful prompt patterns
✗ Don't
−Don't use without understanding skill limitations
−Don't skip validation of outputs
−Don't share sensitive information in prompts
−Don't expect skill to replace human judgment
💡 Pro Tips
★Be specific about desired format and style
★Ask for multiple options to choose from
★Request explanations to understand reasoning
★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
1Familiarize yourself with skill capabilities and limitations
2Start with low-risk, non-critical tasks
3Progress to more complex and valuable use cases
4Build expertise through regular use and experimentation
