---
name: docs-node
description: |
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).
Context: User asks about Node.js configuration
user: "How do I configure the engine in Node.js?"
assistant: "I'll use /imgly-sdk:docs-node to look up configuration options."
Context: User needs server-side generation
user: "How do I use CE.SDK for server-side image generation?"
assistant: "Let me use /imgly-sdk:docs-node to find the relevant documentation."
argument-hint: "[search-topic]"
---
## Version Notice
> CE.SDK `1.83.0` · generated `2026-09-30` · plugin `cesdk`
> · 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.
# CE.SDK Node.js Documentation
Look up documentation for IMG.LY CreativeEditor SDK (Node.js).
**Query**: $ARGUMENTS
## Remote Documentation
This skill reads the CE.SDK docs on `https://img.ly/docs/cesdk/node/`.
The website serves only the latest stable CE.SDK release. It has no older versions.
This bundle targets CE.SDK `1.83.0`. If the project uses a different CE.SDK version,
read the changelog and upgrade pages, and check the type definitions of the
installed package.
## How to Use
1. **Read the index**: Read `references/node.md`. It lists all Node.js pages with
their titles and links.
2. **Select pages**: Pick the pages that match the query.
3. **Fetch each page as Markdown**: Remove the trailing `/` from the link and add `.md`.
For example, `https://img.ly/docs/cesdk/node/export-save-publish/export/to-png-f87eaf/`
becomes `https://img.ly/docs/cesdk/node/export-save-publish/export/to-png-f87eaf.md`.
Use WebFetch. If WebFetch is not available (for example in Codex), use `curl -sL `.
4. **Answer from the fetched pages only**: Give the relevant section and code examples,
and cite the page URLs. If no page covers the request, say so. Do not fill the gap
with pre-trained knowledge.
5. **Check rules**: Before setup, initialization, or common operations, read the local
`rules/*.md` files. They list agent pitfalls that the website does not cover.
## API Lookup
For TypeScript API queries (method signatures, types, parameters):
- Node API (`@cesdk/node`): `https://img.ly/docs/cesdk/node/api/node.md`
Class and type pages follow the same `.md` rule. For example:
`https://img.ly/docs/cesdk/node/api/node/classes/blockapi.md`.
**Tip**: Verify types against the TypeScript definitions — CE.SDK evolves rapidly and type shapes may differ from pre-trained knowledge.
## Full Text
`https://img.ly/docs/cesdk/node/llms-full.txt` holds all Node.js pages in one file
(several MB). Use it only as a last resort, when the index and the pages do not
answer the query. Search it with `curl -sL | grep -n ""`. Do not read
it in full.
## Local Rules
- `rules/asset-handling.md`: Image format recommendations, URI resolution
- `rules/common-pitfalls.md`: Critical gotchas (invisible fills, SVG rendering issues)
- `rules/content-fill-mode.md`: `contentFillMode` belongs on the block, not the fill
- `rules/silent-init-errors.md`: CreativeEditor init callback swallows errors silently
- `rules/verify-properties-before-use.md`: Call `engine.block.findAllProperties()` before you get or set a property
## Additional Triggers
This skill also covers queries about CE.SDK block types, asset sources, and feature capabilities.
It handles API method lookups — BlockAPI, SceneAPI, EditorAPI, AssetAPI, method signatures,
return types, and "engine.block" style queries.
## Related Skills
- Use \`/imgly-sdk:build\` when the user needs implementation help, not just docs
- Use \`/imgly-sdk:explain\` for conceptual explanations beyond what docs cover