imgly

@imgly source repo

14 skills
0 followers
11 hours ago last updated

▌
Gateway Client · imgly
Build clients that integrate with the IMG.LY AI Gateway (`gateway.img.ly`) — discovering models, generating images/video/audio/text, uploading inputs, and consuming the SSE response stream. Use whenever the user wants to call, integrate with, or build a client for the IMG.LY Gateway, or mentions `gateway.img.ly`, `IMG.LY Gateway`, IMG.LY AI generation, or an IMG.LY API key starting with `sk_`.

0
installs
▌
Gateway Client Imgly · imgly
Build IMG.LY-hosted apps that call the IMG.LY AI Gateway using the end user's IMG.LY/Clerk session — no API key on the client, no token-mint backend. Activate ONLY when the user is building inside the IMG.LY hosted app surface (e.g. an app deployed under `*.img.ly`, an IMG.LY-managed Clerk session, or explicitly mentions wanting to authenticate gateway calls with a Clerk JWT issued by IMG.LY's auth setup). For external integrators bringing their own auth, use the `gateway-client` skill instead.

0
installs
▌
Docs Electron · imgly bundle
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 /cesdk: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 /cesdk:docs-electron to find the relevant documentation." </example>

1
install
▌
Docs Angular · imgly bundle
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 /cesdk: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 /cesdk:docs-angular to find the relevant documentation." </example>

1
install
▌
Docs Svelte · imgly bundle
Look up CE.SDK Svelte reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Svelte — 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 Svelte doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Svelte configuration user: "How do I configure the editor in Svelte?" assistant: "I'll use /cesdk:docs-svelte to look up configuration options." </example> <example> Context: User needs Svelte integration user: "How do I use CE.SDK in a Svelte component?" assistant: "Let me use /cesdk:docs-svelte to find the relevant documentation." </example>

1
install
▌
Docs Nuxtjs · imgly bundle
Look up CE.SDK Nuxt.js reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Nuxt.js — 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 Nuxt.js doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Nuxt.js configuration user: "How do I configure the editor in Nuxt.js?" assistant: "I'll use /cesdk:docs-nuxtjs to look up configuration options." </example> <example> Context: User needs Nuxt.js integration user: "How do I use CE.SDK in a Nuxt.js page?" assistant: "Let me use /cesdk:docs-nuxtjs to find the relevant documentation." </example>

1
install
▌
Docs Nextjs · imgly bundle
Look up CE.SDK Next.js reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Next.js — 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 Next.js doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Next.js configuration user: "How do I configure the editor in Next.js?" assistant: "I'll use /cesdk:docs-nextjs to look up configuration options." </example> <example> Context: User asks about SSR compatibility user: "Does CE.SDK work with Next.js server-side rendering?" assistant: "Let me use /cesdk:docs-nextjs to find the relevant documentation." </example>

1
install
▌
Docs React · imgly bundle
Look up CE.SDK React reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for React — 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 React doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about React configuration user: "How do I configure the editor in React?" assistant: "I'll use /cesdk:docs-react to look up configuration options." </example> <example> Context: User needs React component setup user: "How do I embed CE.SDK in a React component?" assistant: "Let me use /cesdk:docs-react to find the relevant documentation." </example>

1
install
▌
Docs · imgly bundle
Look up reference documentation, API signatures, and integration guides 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: An iOS developer needs an engine method signature user: "How do I find an asset source with IMGLYEngine?" assistant: "I will check the installed Xcode symbols, then the bundled IMGLYEngine digest." Example: Context: A macOS developer asks about editor UI user: "Can I present the prebuilt editor on macOS?" assistant: "I will verify the platform boundary and outline the custom engine-backed UI route."

1
install
▌
Docs Sveltekit · imgly bundle
Look up CE.SDK SvelteKit reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for SvelteKit — 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 SvelteKit doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about SvelteKit configuration user: "How do I configure the editor in SvelteKit?" assistant: "I'll use /cesdk:docs-sveltekit to look up configuration options." </example> <example> Context: User asks about SvelteKit SSR user: "Does CE.SDK work with SvelteKit server-side rendering?" assistant: "Let me use /cesdk:docs-sveltekit to find the relevant documentation." </example>

1
install
▌
Docs Node · imgly bundle
Look up CE.SDK Node.js reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Node.js — configuration, headless rendering, export options, batch processing, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing Node.js doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Node.js configuration user: "How do I configure the engine in Node.js?" assistant: "I'll use /cesdk:docs-node to look up configuration options." </example> <example> Context: User needs server-side generation user: "How do I use CE.SDK for server-side image generation?" assistant: "Let me use /cesdk:docs-node to find the relevant documentation." </example>

1
install
▌
Explain · imgly bundle
Explain how CE.SDK Web features work — concepts, architecture, and workflows. Covers React, Vue.js, Svelte, Angular, Electron, Vanilla JavaScript, Node.js, Nuxt.js, Next.js, SvelteKit. Use when the user says "explain", "how does X work", "walk me through", "what is", or "describe" and wants to understand a CE.SDK concept for Web development. Generates custom markdown explanations with diagrams and code examples. Not for looking up existing docs (use docs-{framework}) or writing code (use build). <example> Context: User wants to understand how text layers work user: "Explain how text layers work in CE.SDK" assistant: "I'll use /cesdk:explain to generate a detailed explanation." </example> <example> Context: User needs a concept explained user: "How does the block hierarchy work for video editing?" assistant: "Let me use /cesdk:explain to explain video block hierarchy." </example>

1
install
▌
Docs Vue · imgly bundle
Look up CE.SDK Vue.js reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Vue.js — 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 Vue.js doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Vue.js configuration user: "How do I configure the editor in Vue.js?" assistant: "I'll use /cesdk:docs-vue to look up configuration options." </example> <example> Context: User asks about Vue plugin registration user: "How do I register CE.SDK as a Vue plugin?" assistant: "Let me use /cesdk:docs-vue to find the relevant documentation." </example>

1
install
▌
Docs JS · imgly bundle
Look up CE.SDK Vanilla JavaScript reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Vanilla JavaScript — 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 Vanilla JavaScript doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Vanilla JavaScript configuration user: "How do I configure the editor in Vanilla JavaScript?" assistant: "I'll use /cesdk:docs-js to look up configuration options." </example> <example> Context: User needs vanilla JS setup user: "How do I use CE.SDK without a framework?" assistant: "Let me use /cesdk:docs-js to find the relevant documentation." </example>

1
install

14 published skills