Quick Start
For an overview of what’s included (free browser automation vs optional AI/cloud features), see What is Shiplight AI?.
Step 1: Add MCP and Skills
claude plugin marketplace add ShiplightAI/claude-code-plugin && claude plugin install mcp-plugin@shiplight-pluginsThe plugin includes MCP tools and /verify, /create_e2e_tests, /triage, /cloud skills for UI verification, test authoring, test healing, and cloud sync.
Step 2: Verify UI changes
After your coding agent makes frontend changes, use /verify to have it open a browser, inspect the page, and confirm the result.
Update the navbar to include "Pricing" and "Blog" links, then use /verify to confirm they appear correctly on localhost:3000.Step 3: Create regression tests
Use /create_e2e_tests to scaffold a test project and write YAML tests by walking through your app in a real browser. Tests run locally with npx shiplight test.
Use /create_e2e_tests to set up a test project at ./tests and write a login flow test for localhost:3000.Step 4: Triage failing tests
When tests break after UI changes, deployments, or flow updates, use /triage to automatically reproduce failures, diagnose root causes, and fix the YAML tests. If the application itself is broken, triage reports the bug without modifying tests.
Use /triage to fix failing tests in ./tests after the latest deployment.Step 5: Sync to cloud (optional)
With a Shiplight account, use /cloud to sync local tests to the cloud for scheduled runs, team collaboration, and result tracking. Set SHIPLIGHT_API_TOKEN in your project's .env to enable cloud tools.
Use /cloud to sync all test cases in ./tests to Shiplight cloud.Configuration
| Variable | Required | Description | Default |
|---|---|---|---|
SHIPLIGHT_API_TOKEN | For cloud features | Shiplight API token — enables cloud sync tools. Get your token from app.shiplight.ai/settings/api-tokens. | — |
Next Steps
- Browser Automation - Full reference for browser automation tools and actions
- Understanding YAML Test Format - Statement types, actions, conditionals, loops, variables, and templates
- Local Testing - Export tests as standalone Playwright files for local or CI execution
- Cloud Testing - Create test cases, trigger cloud runs, and analyze results