---
name: svgator-animate
description: "Create, inspect, refine, and export editable SVGator animations, including logo reveals, motion graphics, loaders, and reusable templates. Use with an SVGator project, SVG artwork, a reference, or a written animation brief."
---

# Animate with SVGator

## Establish access and direction

Confirm that SVGator's tools are exposed and account access works. Follow [SVGator setup](../svgator-setup/SKILL.md) if connection or authentication is unresolved. Do not simulate an MCP call or claim a project exists without a successful server result.

Infer the placement, artwork, and motion direction from the request. Ask only for inputs that materially affect the result; choose and state reasonable timing and canvas defaults otherwise. Use a supplied SVG or project to preserve its identity. For missing artwork, author suitable shapes and text; treat raster references as references unless the available workflow supports their import. Rebuild editable vector parts when individual shape animation is needed. Never present an embedded bitmap as independently editable vector geometry.

Use brand assets and supplied geometry faithfully. For CFMoon work, retain the CFMoon spelling and the user's provided mark. Apply geometric energy effects or Hina styling only when the request calls for them.

## Apply the packaged craft layer when it matters

For substantial composition, motion-language, choreography, or interactive
asset work, follow the packaged [motion-design skill](../svgator-motion-design/SKILL.md)
and read only the references relevant to the brief. Skip that extra craft layer
for setup, audits, export-only work, or trivial edits.

Treat the connected server's live tool schemas and `describe_shape` results as
authoritative for mechanics. Do not load a second live motion-design prompt on
top of the packaged adaptation during ordinary work; it can drift or duplicate
the guidance selected for this plugin.

Consult the exposed authoring-reference tool, such as `describe_shape`, for the actual element, animation, and export contracts before constructing project data. Never invent schemas from remembered examples.

## Inspect-only requests

When the user asks to review or validate a project without editing, follow the dedicated [read-only audit skill](../svgator-audit/SKILL.md). Never duplicate a project as part of a read-only audit.

## Build or revise incrementally

For an existing project, inspect its summary and structure, locate the target, then read only the affected elements or properties. Distinguish static properties from values controlled by keyframes. Change the animated channel when animation overrides a static value. Reuse server-returned element IDs and inserted-item paths.

Before substantial changes, record source project ID, target IDs, relevant properties and animator keyframe counts with `get_project`, `get_skeleton` and targeted `read_part` calls. Preserve unrelated layers, editable text, and project settings. For template variants or rebranding, duplicate the original first and edit only the returned copy ID. An element's title alone does not prove its type or replaceability. Prefer incremental edits for refinements; use whole-document creation for a genuinely new project. Avoid replacing an existing document wholesale unless the requested change requires it and its scope is clear.

Plan a readable sequence with a dominant motion, purposeful easing, and a settled finish or seamless loop. Coordinate supporting effects with the main action. Adapt motion amplitude and playback to the intended placement. Keep replaceable logo, headline, and image elements clearly named when building a reusable template.

After each meaningful edit, re-read the changed IDs and animator channels, and compare unrelated structural counts with the pre-edit snapshot where possible. Report unintended differences instead of assuming they were preserved. Confirm text remains real editable text after rebranding. Use the server's validation result and available preview to inspect the affected result. Check clipping, stacking, typography, pacing, easing, final state, and loop continuity. Correct failures before continuing. Do not claim to have watched playback when only static evidence is available.

## Deliver the editable result

Use current export schemas and the account's actual plan capabilities for the requested formats. Preserve transparency when requested. For video or GIF, an `export_project` response initiates an asynchronous render rather than delivering a finished file. Check `get_render` with the returned render ID and deliver only after `status: done`; report failures and watermark status. Signed links are short-lived, so request a fresh link when needed. Respect effective `plan.access_level`; never silently substitute static SVG for a requested animated export.

Return the server's editor URL, requested exports, and a short description of the motion. Distinguish saved source, visual review, and tested playback. Report export restrictions or unverified behavior plainly.

Primary references:
- [SVGator tools](https://github.com/SVGator/mcp/blob/main/tools.md)
- [Project editing](https://github.com/SVGator/mcp/blob/main/editing.md)
- [Exporting](https://github.com/SVGator/mcp/blob/main/exporting.md)