Run Wix Engine (mobile-apps-engine) iOS E2E tests locally to validate RNN changes. Use when you need to test RNN fixes against the Engine's Detox test suite.
npx skills add https://github.com/wix/react-native-navigation --skill engine-e2e
The Engine app (@wix/wix-one-app-engine) in ~/Documents/mobile-apps-engine consumes RNN
from node_modules/react-native-navigation. To test RNN changes against the Engine's E2E
suite, you patch the Engine's copy of RNN, rebuild the native binary, and run the tests.
nvm use default)CI env var must be unset (not 0, fully unset) to avoid CI-specific codepaths.Use env -u CI before every command.
~/Documents/mobile-apps-engine with yarn install already done.Apply your RNN source changes to the corresponding files under:
~/Documents/mobile-apps-engine/node_modules/react-native-navigation/ios/
The directory structure mirrors the RNN repo's ios/ folder exactly.
cd ~/Documents/mobile-apps-engine
unset PREFIX && . ~/.nvm/nvm.sh > /dev/null && nvm use default > /dev/null
env -u CI yarn workspace @wix/mobile-apps-engine-native-builds build-local-ios
This runs xcodebuild with -quiet flag — expect no output until it finishes.
Takes ~10-15 minutes on M-series Macs.
The build output (.app bundle) lands in:
packages/native/mobile-apps-engine-native-builds/dist/binaries.json
SecKeychainUnlock): The CI env var is set. Use env -u CI.These are needed once per checkout. Skip if already built.
env -u CI yarn workspace @wix/mobile-apps-engine-extra-bundle local:build
env -u CI yarn workspace @wix/mobile-apps-dependencies local:build
cd ~/Documents/mobile-apps-engine
unset PREFIX && . ~/.nvm/nvm.sh > /dev/null && nvm use default > /dev/null
env -u CI yarn workspace @wix/wix-one-app-engine test:e2e:ios -w d <suite_files...>
The -w d flag selects the Detox worker count.
| Suite file | What it tests |
|-----------|---------------|
| e2e/suites/ExternalLinks.test.js | Deep link navigation, back button |
| e2e/suites/ExternalLinksModes.test.js | Deep link modes (pop to root, tab switch) |
| e2e/suites/ExternalLinksPushNotifications.test.js | Push notification deep links |
| e2e/suites/ExtenalLinksWithSiteSelect.test.js | Deep links with site selection |
| e2e/suites/EngineUIComponents.test.js | Error screen, UI components |
| e2e/suites/LaunchArgs.test.js | Launch arguments |
| e2e/suites/LazyModules.test.js | Lazy-loaded modules |
env -u CI yarn workspace @wix/wix-one-app-engine test:e2e:ios -w d \
e2e/suites/ExternalLinks.test.js \
e2e/suites/ExternalLinksModes.test.js \
e2e/suites/ExternalLinksPushNotifications.test.js
Error: No dist version found: The native build hasn't run or failed.Run step 2 again.
Cannot find module .../mobile-apps-engine-extra-bundle/index.js:Run step 3 (local:build for extra-bundle).
ENOENT .../metadata.json: Run step 3 (local:build for mobile-apps-dependencies).Unable to resolve module @rozenite/...: The Rozenite plugin import is broken.Patch packages/wix-one-app-engine/src/rozenitePlugin/helper/rozenite-network-inspector.ts
to make the import optional with a no-op fallback.
navigateBack(): The navigateBack() helper tapselement(by.id('pop')) on iOS. This relies on RNN's setBackButtonTestID working
correctly. If the back button's view hierarchy changed (e.g., iOS 26 Liquid Glass),
the testID isn't applied and the element can't be found.
| File | Purpose |
|------|---------|
| packages/wix-one-app-engine/e2e/helpers/utils.js | Test helpers including navigateBack() |
| packages/wix-one-app-engine/demo-modules/deep-links/module.js | Deep link route definitions |
| packages/wix-one-app-engine/demo-modules/deep-links/Screens.js | Deep link screen components |
| packages/wix-one-app-engine/internalScripts/test-e2e.js | E2E test runner script |
| packages/native/mobile-apps-engine-native-builds/local_build_scripts/build_ios.js | Local iOS build script |
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when implementing any feature or bugfix, before writing implementation code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
Take wix/engine-e2e from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.