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 /cesdk: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 /cesdk:build to implement text overlays." </example>
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>
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>
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>
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>
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>
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>
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>