Agent skill · software engineering · jeremylongshore

anima-deploy-integration

Deploy Anima design-to-code service as a backend API endpoint.

Why this skill is useful

Adds executable scripts for deploying Anima SDK as a backend API, which are not commonly found in public documentation.

What it needs

Requires docker, gcloud, vercel installed locally. Requires anima, figma account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.

What this skill does

Anima Deploy Integration Overview Deploy the Anima SDK as a backend service. The SDK is server-side only, so deploy it behind an API endpoint that accepts Figma file/node references and returns generated code. Prerequisites A private or authenticated service boundary with an allowlisted design-file registry; do not expose arbitrary fileKey and nodesId generation to the public internet. Managed Anima and Figma secrets, separate staging/production credentials, request limits, and an audit trail that excludes token values and design content. An approved generated-output path, validation pipeline, and rollback target for every deployment revision. Instructions Step 1: Express API Wrapper Step 2: Vercel Serverless Function Step 3: Deploy Commands Tool Discipline Use Read and Grep to inspect the existing integration and generated diff before changing anything. Use Write or Edit only inside the approved generated-code, test, or configuration paths. Use the declared Bash commands only for the explicit install, validation, or diagnostic steps in this workflow; never print tokens, source designs, generated source, or private website captures. Output Express API wrapping Anima SDK for internal design tooling Vercel serverless function for lightweight deployment Cloud Run deployment with Secret Manager Examples Deploy the service to a staging environment behind the organization’s existing identity proxy and invoke /api/generate with one allowlisted file/node pair. Verify the request is authorized, output remains in the approved generated-code location, logs contain only request metadata, and generated files pass the downstream formatter and test gate before a human reviews them. If an unauthenticated caller, unknown node, or secret-binding error reaches the service, reject the request, alert the operator, and keep the prior revision active rather than opening broad access or embedding credentials in the client. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills jeremylongshore/anima-deploy-integration

View the source on GitHub

Browse the @skills marketplace