About barcode-capture-capacitor
A skill for developers integrating Scandit BarcodeCapture in Capacitor apps or migrating existing scanners. It selects focused references for each task and emphasizes API verification, plugin initialization, and native-platform requirements.
Key features
- 01Routes integration, upgrade, and replacement tasks
- 02Verifies Scandit APIs against references
- 03Covers plugin initialization and native requirements
- 04Guides licence key setup
Use cases
- 01Add barcode scanning to a Capacitor app
- 02Upgrade between Scandit SDK versions
- 03Migrate from a third-party scanner to BarcodeCapture
MCP support
It can use the Scandit MCP server to configure scanner setup and retrieve licence keys, and explains how to connect that remote server.
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ scandit/ skills --skill barcode-capture-capacitorAfter installing, type/barcode-capture-capacitorin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
references/integration.mdmigration.mdthird-party-migration.mdDetails
From the project READMEBarcodeCapture Capacitor Skill
Critical: Do Not Trust Internal Knowledge
Your training data may contain outdated or incorrect Scandit SDK APIs. The BarcodeCapture API changes between major SDK versions — properties get renamed, removed, or restructured, and the Capacitor plugin surface (imports, plugin initialization, native sync steps) has also evolved.
Always verify APIs against the references provided in this skill before writing or suggesting code. Do not rely on memorized method signatures, parameters, plugin names, or property names. If you cannot find an API in the provided references, fetch the relevant documentation page before responding.
Capacitor-specific gotchas worth flagging:
ScanditCaptureCorePlugin.initializePlugins()must be called (and awaited) before any other Scandit API — includingDataCaptureContextconstruction. Forgetting this produces runtime errors that look unrelated to initialization.npx cap syncmust be run after every plugin version change to propagate native artifacts into iOS/Android. Skipping it yields a web/native version mismatch at runtime.- BarcodeCapture renders into a
DataCaptureViewthat is connected to a DOM element viaview.connectToElement(...). The view itself is a native overlay, but the DOM container determines its size and position. ABarcodeCaptureOverlaymust be created and added to the view to visualize recognized barcodes. - The camera is a separate component:
Camera.default(orCamera.withSettings(BarcodeCapture.createRecommendedCameraSettings())), set viacontext.setFrameSource(camera), then started viacamera.switchToDesiredState(FrameSourceState.On). - Disable the mode while handling a scan: the
didScancallback blocks further frame processing on Capacitor. If you do any meaningful work (database lookup, navigation, network) insidedidScan, setbarcodeCapture.isEnabled = falsefirst, perform the work, then re-enable. This is documented behavior on Capacitor specifically. - BarcodeCapture only renders on native platforms (iOS, Android). If your app also targets the web build of Capacitor, guard initialization with
Capacitor.isNativePlatform().
Intent Routing
Based on the user's request, load the appropriate reference file before responding:
- Integrating BarcodeCapture from scratch (e.g. "add BarcodeCapture to my app", "set up barcode scanning", "how do I use BarcodeCapture in Capacitor", "wire up the overlay", "handle the camera lifecycle") → read references/integration.md and follow the instructions there.
- Migrating or upgrading an existing BarcodeCapture integration (e.g. "upgrade from v6 to v7", "migrate my BarcodeCapture", "bump the Scandit plugins to v8", "what changed between SDK versions") → read references/migration.md and follow the instructions there.
- Replacing a third-party scanner (e.g. "switch from @capacitor-mlkit/barcode-scanning / ML Kit to Scandit", "replace BarcodeScanner.startScan and barcodesScanned with BarcodeCapture") → read references/third-party-migration.md and follow the instructions there.
API Usage Policy
Only use APIs that are explicitly documented in the Scandit references below. Do not invent or guess method signatures, parameters, property names, or imports. If unsure whether an API exists or how it is called — or if a TypeScript / runtime error occurs — fetch the relevant reference page before responding. Do not tell the user to check the docs themselves. After answering, always include the relevant link so the user can explore further.
Never construct or guess documentation URLs. When you need a specific class or property's API page:
- First check whether the page you already fetched (e.g. the Advanced Configurations page) contains a direct hyperlink to it — topic pages link directly to relevant API symbols. Always request links alongside content in your fetch prompt.
- If no direct link was found, fetch the API index (see Full API reference in the table below), extract the actual link from it, and follow that.
URL structures vary across SDK versions and plugin paths (e.g. api/ui/ subdirectory) and guessing will lead to 404s.
Framework variant policy
Capacitor is a WebView-based framework. Examples in this skill use plain JavaScript (ES modules). TypeScript projects can use the same imports and APIs verbatim — just add types — but this skill does not assume a TypeScript project by default. If the target project is clearly TypeScript (.ts files, tsconfig.json), adapt the final output to TypeScript syntax; otherwise stay in plain JS.
Licence key
Scanning needs a Scandit licence key. For this skill the licence product is native and the licence platforms are ios and android.
Work through these in order — never block the user on MCP:
-
The Scandit MCP server is connected — call
ensure_scanner_setupwith productnativeand platformsiosandandroid,app_identifier(the app's bundle or application id; for web, its production domain, neverlocalhost) andenv_varSCANDIT_LICENSE_KEY. Do not run the command it returns. Then callget_license_keywith the key's id, from that result or fromlist_license_keys; iflist_license_keysshows the key is not a trial, ask the user before fetching it. Show at most a masked preview in chat; never print a full key. -
It is not connected — tell the user once that they can connect the remote Scandit MCP server,
https://ssl.scandit.com/mcp, in their MCP client, then continue from step 1. Do not edit MCP client configuration yourself.Authentication is browser-based, so it is not supported headless or in CI. The server provisions trial keys only; it never creates, revokes, or modifies production licences.
-
The user declines, or has no MCP client — they generate a key themselves at https://ssl.scandit.com (no account yet: https://ssl.scandit.com/dashboard/sign-up?p=test) and paste it in.
Then put the key into the code: write it into the licence-key call in place of the placeholder — the key get_license_key returned, or the one the user pastes or gives you — still showing only a masked preview in chat. Do not search the project, its files or the environment for a key.
References
Direct users to the right resource based on their question:
| Topic | Resource |
|---|---|
| Capacitor integration | Get Started · Samples |
| Advanced topics (custom feedback, viewfinders, location selection, scan intention) | Advanced Configurations |
| Migration between major SDK versions | 6 → 7 · 7 → 8 |
| Full API reference | BarcodeCapture API |