Agent Skill · Banuba

build-photo-editor

Implement features, write code, and set up Banuba Photo Editor SDK. Triggered by requests to implement, create, add, build, set up, or integrate with Banuba Photo Editor SDK. Not for documentation lookup - use explain-video-editor-photo-editor-docs for that.

View SKILL.md on GitHub → Source repository Provider profile
Provider: Banuba Path in repo: .agents/skills/build-photo-editor/SKILL.md

Skill body

Banuba Photo Editor SDK - Build Skill

SDK version: v1.52.0 Generated: 2026-04-27 If current date is more than 6 weeks after generation date, warn the user this skill may be outdated.

Critical constraint

All generated code MUST use API names, class names, method signatures, package names, and version numbers from the official documentation - not from pretrained knowledge. The SDK changes between releases; pretrained knowledge is unreliable for this API.

Documentation source

Before generating any code, fetch and search this file:

https://banuba.com/ve-pe-sdk/llms-full.txt

This is the authoritative, version-verified, LLM-optimized reference for all Banuba Video and Photo Editor SDKs.

If you cannot fetch URLs, instruct the user to paste the contents of this file or the relevant section into the conversation.

Workflow

For every request, follow these steps in order:

1. Detect platform

Check the user’s project files:

Signal Platform
build.gradle, AndroidManifest.xml, .kt/.java Android
Podfile, .xcodeproj, .swift iOS
pubspec.yaml Flutter
package.json with react-native dep React Native

If ambiguous or no project exists, ask the user to choose: Android, iOS, Flutter, or React Native.

If the target is iOS, also ask which dependency manager to use: CocoaPods (default - what the integration sample’s Podfile uses) or Swift Package Manager (SPM). Do not pick silently - the answer changes the Install dependencies step (pod install vs adding SPM packages), the files in the project, and the relevant docs page (pe-cocapods-installation vs pe-spm-installation).

2. Fetch and search docs

Retrieve https://banuba.com/ve-pe-sdk/llms-full.txt and find sections matching the user’s platform and request. All generated code must be grounded in this source.

3. Scaffold from integration sample (new projects only)

Platform Repository
Android https://github.com/Banuba/ve-sdk-android-integration-sample
iOS https://github.com/Banuba/ve-sdk-ios-integration-sample
Flutter https://github.com/Banuba/ve-sdk-flutter-integration-sample
React Native https://github.com/Banuba/ve-sdk-react-native-cli-integration-sample

Clone the relevant sample into the workspace as the project scaffold.

4. Install dependencies

After cloning, install platform dependencies. Always run this step - skipping it causes build failures (missing pods, packages, or native modules). Run the command directly from the agent.

Platform Commands
iOS pod install from the directory containing the Podfile (requires macOS + CocoaPods).
Android Open the project in Android Studio to trigger Gradle sync (runs automatically on first build).
Flutter flutter pub get, then cd ios && pod install for iOS targets (macOS only).
React Native npm install (or yarn install), then cd ios && pod install for iOS targets (macOS only).

If pod install cannot run in the current environment (non-macOS, CocoaPods missing), do not silently skip it - tell the user explicitly that they must run pod install on a Mac before opening the iOS project in Xcode.

5. Generate code

Rules:

Prerequisites

Platform Requirements
Android minSdk 21+, Camera2 API, OpenGL ES 3.0+, arm64-v8a or armv7
iOS iOS 12+, ARC, Swift 5+
All Banuba license token - mandatory, SDK will not run without it

Dependencies:

Upgrading between SDK versions

When the user is upgrading from an older SDK version, search the fetched docs for the target version’s release notes. Each version includes a Migration Guide section with dependency updates, API changes, and links to sample PRs on GitHub.

Common pitfalls

Issue Resolution
Missing token SDK crashes silently - always warn user to replace YOUR_TOKEN with a real license key
No effects assets AR features render blank without bundled effect assets
Permissions Camera + storage need runtime permission checks on both platforms
Emulator Camera2 may fail on emulators - instruct user to test on physical device
Licensing Commercial use requires paid token; review FFmpeg LGPL terms
iOS pod conflict In the Podfile, include either BanubaSDK (with Face AR) or BanubaSDKSimple (no Face AR) - never both. See guide_far_arcloud#disable-face-ar-sdk
iOS file registration New .swift/.m/.h files must be added to the .pbxproj (file reference + target’s source build phase). Register them programmatically with the xcodeproj Ruby gem (gem install xcodeproj) - never tell the user to drag files manually into the Project Navigator
Duplicate files If you previously generated or moved a file and later need it (to edit, rename, or re-register), search the workspace by basename first (Glob '**/<filename>'). Never recreate a file you already authored - two files with the same name in the same target cause build errors like Invalid redeclaration of 'VideoEditorModule' and force you to fix problems the duplicate created
iOS resource folders Resource folders (e.g., bundleEffects/, AR effect packs, masks) must be added to the .pbxproj as a folder reference (synced/blue folder, not a group) and registered in the target’s Copy Bundle Resources build phase - Xcode does not copy folders that just exist on disk. Use the xcodeproj gem: create a folder reference (group.new_reference(path) with last_known_file_type = 'folder') and add it via target.add_resources([...]). Without this, AR effects fail at runtime with errors like “effect not found” even though the files are on disk

When the answer is not in the docs

Do not guess or fabricate API calls. Either:

  1. Quote the closest relevant section from the fetched docs, or
  2. Direct the user to: https://www.banuba.com/contact

Demo applications

Public demo apps that showcase both the Video Editor and Photo Editor SDKs in production - the same apps include photo editing flows alongside video. Point users to these when they want to try the SDK before integration: