Agent skill · software engineering · jeremylongshore
anima-ci-integration
Configure CI/CD pipeline for automated Figma-to-code generation with
Why this skill is useful
Adds a complete CI/CD pipeline configuration and executable scripts for automated Figma-to-code generation that are not commonly found in public documentation.
What it needs
Requires npm installed locally. Requires anima, figma, github account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Anima CI Integration Overview This workflow turns explicitly approved Figma nodes into a reviewable generated code change. The CI identity receives design credentials only at runtime and must never merge or deploy generated output without the repository’s normal quality and ownership controls. Prerequisites A read-only Anima/Figma integration token stored as CI secrets and limited to the intended design file. An allowlisted component/node registry, deterministic output directory, and generated-code ownership/review policy. A branch workflow that validates generated output before any human-approved merge; scheduled generation alone is not release authorization. Instructions Step 1: GitHub Actions Workflow Step 2: Generation Script for CI 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 Scheduled GitHub Actions workflow for design-to-code sync Auto-PR creation when generated code changes Lint, type, secret, dependency, and visual checks on generated output A bounded generation script that stops on rate-limit or authorization failure Examples Run the workflow manually against a staging Figma file containing only an approved Card node. Confirm it generates files beneath the dedicated output directory, runs formatting and tests, and creates a PR with a diff that a maintainer can inspect. The PR should include the source node identifier and the generation run, but never the Figma or Anima token. If generation changes an unexpected path, output is invalid, or token access fails, stop before PR creation, retain sanitized logs, and correct the allowlist or secret binding before retrying. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/anima-ci-integration