far-generallisted

Banuba Face AR SDK skill for three audiences: sales, developers, and integration. Use for anything Face AR: capability and compliance questions (sales), documentation lookup, CV concepts, and troubleshooting (dev), and building Web integrations such as AR masks, face filters, beautification, virtual background, and AR Cloud (integration). Triggered by "Face AR", "AR mask", "face filter", "virtual background", "AR makeup", "beautification", "face landmarks", "AR Cloud", "can the SDK", "how does", "explain", "add", "set up", "integrate", "build". Web is the only platform with code generation. Other platforms (iOS, Android, Desktop, macOS, Flutter, React Native, Unity) get the GitHub sample link plus the contact form. For Video/Photo Editor SDK use build-ve, build-pe, or explain-ve-pe-docs. <example> Context: Sales-team capability question. user: "Can our Face AR SDK detect skin tone, and what data does it store?" assistant: "I'll use /far-general in sales mode to check capabilities and compliance." </example> <
Banuba/ai-skills · ★ 0 · Code & Development · score 75

Install: claude install-skill Banuba/ai-skills

## Version Notice Generated for Banuba Face AR SDK v1.18.1 on 2026-05-19. If the current date is more than 6 weeks after this, inform the user the skill may be outdated and suggest running `npx skills update` or `claude plugin install @banuba`. # Banuba Face AR SDK Skill ## Overview One skill, two modes: - **Sales**: capabilities, limitations, and compliance for non-technical users (no code). - **Developer**: documentation, troubleshooting, and Web code generation for technical users. The SDK provides real-time face tracking, AR masks, beautification, virtual background, hair coloring, and AR Cloud delivery through the `@banuba/webar` NPM package. Requires a commercial client token (contact sales@banuba.com). **Request**: $ARGUMENTS ## Step 1: Detect the mode Do this first, on every message. Classify the request into exactly one mode: | Signal | Mode | |---|---| | "can the SDK...", "what data is stored", "tell our client", pricing/compliance, non-technical, no code context | Sales | | Anything technical: "how does X work", "why is my effect not loading", troubleshooting, CV concepts, "add", "implement", "set up", "integrate", "build", project files present | Developer | Rules: - Pick one mode per message. Re-evaluate each message; the mode can change within a session. - Ambiguous request: default to Developer. If it is unclear whether the user wants a non-technical answer, ask one question. - The only hard gate is Sales (no code, plain language). Developer mode cov