explain

Explain CE.SDK Swift concepts, architecture, and workflows for CE.SDK Swift projects targeting iOS, macOS, or Mac Catalyst. Use it for first-party CreativeEditor SDK guidance, module scope, Xcode implementation, or bundled Swift references. It distinguishes cross-platform IMGLYEngine from iOS-only editor, camera, and UI modules. Prefer live Xcode symbols for the installed SDK, then bundled references. Do not use it for Web, Android, Flutter, or React Native. Example: Context: A developer is learning the engine model user: "Explain the CE.SDK block hierarchy in Swift." assistant: "I will explain the model with Swift examples and the correct module scope." Example: Context: A Catalyst developer needs architecture advice user: "How should I build an editor UI for Mac Catalyst?" assistant: "I will explain the engine-backed custom UI architecture and platform limitation."

Jump to install Review files

Repository: imgly/agent-skills
Last source activity: October 1, 2026 at 07:18
Detected SKILL.md language: English
Stars: 8
Forks: 3

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with an AI assistant

Copy this prompt into the AI assistant you're using.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/imgly/agent-skills/tree/main/plugins/cesdk-swift/skills/explain.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/imgly/agent-skills --skill explain

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

name: explain
description: Explain CE.SDK Swift concepts, architecture, and workflows for CE.SDK Swift projects targeting iOS, macOS, or Mac Catalyst. Use it for first-party CreativeEditor SDK guidance, module scope, Xcode implementation, or bundled Swift references. It distinguishes cross-platform IMGLYEngine from iOS-only editor, camera, and UI modules. Prefer live Xcode symbols for the installed SDK, then bundled references. Do not use it for Web, Android, Flutter, or React Native. Example: Context: A developer is learning the engine model user: "Explain the CE.SDK block hierarchy in Swift." assistant: "I will explain the model with Swift examples and the correct module scope." Example: Context: A Catalyst developer needs architecture advice user: "How should I build an editor UI for Mac Catalyst?" assistant: "I will explain the engine-backed custom UI architecture and platform limitation."

# Explain CE.SDK for Swift ## Version Notice > CE.SDK `1.83.0` · generated `2026-09-30` · plugin `cesdk-swift` > · canonical update source `imgly/agent-skills`. > > If this bundle is over six weeks old, or the user asks about updates, follow > `references/update-check.md` once per task and reuse the result for all CE.SDK > skills. Keep the check read-only. Never install, update, overwrite, or delete > anything without explicit user approval. Continue with this bundle unless an > update is approved. ## Platform and Module Scope Determine the target from the request, active Xcode destination, Package.swift, or project settings. If the answer materially changes and the target remains unclear, ask whether it is iOS, macOS, or Mac Catalyst. | Module surface | iOS | macOS | Mac Catalyst | |---|---:|---:|---:| | `IMGLYEngine` | Yes | Yes | Yes | | `IMGLYCore`, `IMGLYCoreUI`, `IMGLYCamera`, `IMGLYEditor` | Yes | No | No | | Prebuilt editor products and SwiftUI starter kits | Yes | No | No | For macOS or Mac Catalyst editor-UI requests, explain that the prebuilt editor UI is unavailable and offer an `IMGLYEngine`-backed custom UI instead. ## Source Priority 1. Prefer live Xcode symbol or documentation lookup, when available, for exact installed-SDK signatures, generic constraints, availability, and deprecations. 2. Use bundled API digests for discovery, planning, and portable lookup. 3. Use bundled guides for integration recipes. 4. Use pretrained knowledge only when the installed SDK and bundle do not answer. If live Xcode symbols disagree with a bundled API digest, follow the installed SDK and call out the version difference. Explain from first principles, then connect the concept to concrete Swift APIs. Keep all engine calls on the main actor: ```swift @MainActor func updateScene(using engine: Engine) throws { // Use the exact installed-SDK signature discovered in Xcode. } ``` State assumptions and platform limits explicitly. Use the sibling `docs` skill for exact reference lookup and the sibling `build` skill when the user wants runnable implementation.

View on GitHub

Back to search Back to installation

build

Implement features, write code, and set up CE.SDK Web projects. Covers React, Vue.js, Svelte, Angular, Electron, Vanilla JavaScript, Node.js, Nuxt.js, Next.js, SvelteKit. Use when the user asks to implement, create, add, build, set up, or integrate something with CE.SDK for Web. Triggered by "help me add", "set up", "build a photo editor", or "create a design tool". Covers photo, video, and design editors. Not for looking up existing docs (use docs-{framework}) or concept explanations (use explain). <example> Context: User wants to build a Web app with CE.SDK user: "Help me set up CE.SDK in my project" assistant: "I'll use /imgly-sdk:build to help set this up." </example> <example> Context: User wants to add a specific feature user: "Add text overlays to my image editor" assistant: "Let me use /imgly-sdk:build to implement text overlays." </example>

2026-10-08

docs-angular

Look up CE.SDK Angular reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Angular — configuration, UI customization, export options, feature guides, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing Angular doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Angular configuration user: "How do I configure the editor in Angular?" assistant: "I'll use /imgly-sdk:docs-angular to look up configuration options." </example> <example> Context: User needs Angular integration user: "How do I use CE.SDK in an Angular component?" assistant: "Let me use /imgly-sdk:docs-angular to find the relevant documentation." </example>

2026-10-08

docs-electron

Look up CE.SDK Electron reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Electron — configuration, UI customization, export options, feature guides, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing Electron doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Electron configuration user: "How do I configure the editor in Electron?" assistant: "I'll use /imgly-sdk:docs-electron to look up configuration options." </example> <example> Context: User needs Electron integration user: "How do I embed CE.SDK in an Electron app?" assistant: "Let me use /imgly-sdk:docs-electron to find the relevant documentation." </example>

2026-10-08

View all from this repository

explain

Source facts

Install options

Install with an AI assistant

Review the source files

More from this repository

Install with an AI assistant

More from this repository