Add Camera
Internal implementation skill invoked by /add-native for camera, image picker, barcode...
Install
npx skills add microsoft/power-platform-skills --skill add-camera -g -a claude-code -y- Repository
- microsoft/power-platform-skills1.1k
- Category
- Media
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Internal implementation skill invoked by /add-native for camera, image picker, barcode scanner, QR scanner, and camera/gallery Dataverse artifact workflows.
Shared instructions: shared-instructions.md, read first.
Working directory: before any project read or command, execute
native-artifact-compatibility.md Step 0.
Inherit /add-native's resolved absolute working_dir; bind every shell call and
file tool to it, even when this helper starts from another directory.
References:
- dataverse-reference.md, File/image column upload patterns (Step 7, 8)
Add Camera
Internal helper. Users should invoke /add-native camera, /add-native image-picker, /add-native barcode-scanner, or /add-native qr-scanner; /add-native routes here after resolving the capability.
Generate typed camera + image-picker wrappers, an optional barcode/QR scanner control, and optional custom-upload guidance for Dataverse image/file workflows.
This skill only writes JS files under src/native/. It does not install
modules or touch package.json / app.config.js. Only the modules required by
the approved artifact set below must already ship in the template/native build;
if a required module is missing, STOP. Do not require unrelated capture packages
for a scanner-only or upload-only request.
Why: customer binaries are built from a pre-built rewrap base, not from the customer's package.json. Adding a native module here would compile against modules the binary doesn't actually contain, causing runtime crashes after rewrap. See /add-native for the same hard rules.
Required modules depend on the approved artifact set (all must already be in
package.json):
