Agent skill

Anima CI Integration

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Configure CI/CD pipeline for automated Figma-to-code generation with Anima.

MITAuto-check passedDevOps & Cloud

Install Anima CI Integration

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill anima-ci-integration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace anima-ci-integration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/anima-ci-integration .claude/skills/anima-ci-integration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
anima-ci-integration
GitHub stars
2.8k
Token cost
~1.6k tokens
SKILL.md length
361 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Configure CI/CD pipeline for automated Figma-to-code generation with Anima.

  • Works in 2 steps: GitHub Actions Workflow → Generation Script for CI
  • Automating design-to-code in GitHub Actions
  • SKILL.md covers Overview, Prerequisites, Instructions and Tool Discipline, plus 4 more sections
  • Needs ANIMA_TOKEN and FIGMA_TOKEN

What it does

Anima CI Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure CI/CD pipeline for automated Figma-to-code generation with Anima. Use when automating design-to-code in GitHub Actions, setting up PR-based component generation, or integrating Anima into design handoff workflows. Trigger with: "anima CI", "anima GitHub Actions", "anima automated generation".

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Requires Node.js 20+, approved Anima API access, current Anima SDK documentation, and authorized Figma or website source access

It sits in DevOps & Cloud, covering CI/CD and Design to code. It works with GitHub Actions and Figma. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Automating design-to-code in GitHub Actions
  • Setting up PR-based component generation
  • Integrating Anima into design handoff workflows
  • Anima GitHub Actions

Example prompts

  • “anima CI”
  • “anima GitHub Actions”
  • “anima automated generation”
  • “/anima-ci-integration”

Requirements

  • Node.js
  • A credential in ANIMA_TOKEN
  • A credential in FIGMA_TOKEN
  • Compatibility (from SKILL.md): Requires Node.js 20+, approved Anima API access, current Anima SDK documentation, and authorized Figma or website source access
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(npm:*), Grep

Workflow steps

2 steps, taken from the step headings in SKILL.md.

  1. GitHub Actions Workflow
  2. Generation Script for CI

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(npm:*)
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml and typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.animaapp.com
    • docs.github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • ANIMA_TOKEN
    • FIGMA_TOKEN
    • FIGMA_FILE_KEY
    • GH_TOKEN
    • GITHUB_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires Node.js 20+, approved Anima API access, current Anima SDK documentation, and authorized Figma or website source access

    From compatibility in the SKILL.md frontmatter.

Context cost

Anima CI Integration loads about 1.6k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 81 tokens; SKILL.md has 361 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 361 words, ~1,619 tokens.

Download SKILL.mdSave it as .claude/skills/anima-ci-integration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
anima-ci-integration
description
Configure CI/CD pipeline for automated Figma-to-code generation with Anima. Use when automating design-to-code in GitHub Actions, setting up PR-based component generation, or integrating Anima into design handoff workflows. Trigger with: "anima CI", "anima GitHub Actions", "anima automated generation".
allowed-tools
Read, Write, Edit, Bash(npm:*), Grep
compatibility
Requires Node.js 20+, approved Anima API access, current Anima SDK documentation, and authorized Figma or website source access
version
2.0.0
argument-hint
[workflow-file] [figma-file-key]
model
inherit
effort
high
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, design, figma, anima, ci-cd

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
yaml
# .github/workflows/design-sync.yml
name: Design-to-Code Sync

on:
  schedule:
    - cron: '0 9 * * 1-5'  # Weekdays at 9am
  workflow_dispatch:         # Manual trigger

jobs:
  generate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with: { node-version: '20' }
      - run: npm ci
      - name: Generate components from Figma
        env:
          ANIMA_TOKEN: ${{ secrets.ANIMA_TOKEN }}
          FIGMA_TOKEN: ${{ secrets.FIGMA_TOKEN }}
          FIGMA_FILE_KEY: ${{ secrets.FIGMA_FILE_KEY }}
        run: npx tsx scripts/generate-components.ts
      - name: Lint generated code
        run: npx eslint src/components/generated/ --fix
      - name: Check for changes
        id: changes
        run: |
          if git diff --quiet src/components/generated/; then
            echo "changed=false" >> $GITHUB_OUTPUT
          else
            echo "changed=true" >> $GITHUB_OUTPUT
          fi
      - name: Create PR with generated components
        if: steps.changes.outputs.changed == 'true'
        run: |
          git checkout -b design-sync/$(date +%Y%m%d)
          git add src/components/generated/
          git commit -m "chore: sync generated components from Figma"
          git push -u origin HEAD
          gh pr create --title "Design sync: updated generated components" \
            --body "Auto-generated from Figma via Anima SDK"
        env:
          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Step 2: Generation Script for CI
typescript
// scripts/generate-components.ts
import { Anima } from '@animaapp/anima-sdk';
import fs from 'fs';
import path from 'path';

const anima = new Anima({ auth: { token: process.env.ANIMA_TOKEN! } });

const COMPONENTS = [
  { nodeId: '1:2', name: 'Hero' },
  { nodeId: '3:4', name: 'Card' },
  { nodeId: '5:6', name: 'Navigation' },
];

async function main() {
  const outputDir = 'src/components/generated';
  fs.mkdirSync(outputDir, { recursive: true });

  for (const comp of COMPONENTS) {
    const { files } = await anima.generateCode({
      fileKey: process.env.FIGMA_FILE_KEY!,
      figmaToken: process.env.FIGMA_TOKEN!,
      nodesId: [comp.nodeId],
      settings: { language: 'typescript', framework: 'react', styling: 'tailwind', uiLibrary: 'shadcn' },
    });

    for (const [fileName, file] of Object.entries(files)) {
      if (file.isBinary) throw new Error(`Binary output needs asset handling: ${fileName}`);
      const root = path.resolve(outputDir);
      const target = path.resolve(root, fileName);
      if (!target.startsWith(`${root}${path.sep}`)) throw new Error('Unsafe output path');
      fs.mkdirSync(path.dirname(target), { recursive: true });
      fs.writeFileSync(target, file.content);
    }
    console.log(`Generated: ${comp.name}`);
    // Stop on a provider/Figma rate-limit result; do not guess a safe quota.
  }
}

main().catch(() => {
  console.error({ failureClass: 'design-sync-failed' });
  process.exit(1);
});

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
Show full SKILL.md (168 more words)Show less

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.

Error Handling

FailureResponse
Design token or file access is deniedFail the job without printing credentials; verify scoped secret configuration.
Generator writes outside the approved directoryRefuse to commit or open a PR and investigate the path mapping.
Generated code fails lint or testsKeep the branch unmerged and return the actionable failure to the design/code owners.
Scheduled run has no approved changesExit cleanly without creating an empty PR or deployment.

Resources

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/anima-ci-integration of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Anima CI Integration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Anima CI Integration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Anima CI Integration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.6kAutomated safety check: PassMIT
Sync Iconswanteddev/montage-web117—~1.9kAutomated safety check: PassMIT
Auto Page Synckennyzir/7deer_skills322—~1.7kAutomated safety check: PassMIT
Cicd Integrationmurphytrueman/design-system-ops206—~5.4kAutomated safety check: PassMIT
Actions ManagerCommunity-Access/accessibility-agents423—~904Automated safety check: PassMIT
Analyze GitHub Action Logswithastro/astro63k1 repos~1.3kAutomated safety check: PassCustom licence

Similar skills

  • Sync Icons

    wanteddev/montage-web

    Sync icons from the Figma file into icon and open a PR by dispatching the figma-icon-sync-code-connect.yml GitHub Actions workflow.

    117 GitHub stars~1.9k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Auto Page Sync

    kennyzir/7deer_skills

    仓库 Markdown/JSON 内容自动同步到前端页面,配置 GitHub Actions 定时拉取 + 部署,保持 Google SEO 内容新鲜度。支持日报、博客、Changelog、Landing Page 等多种页面模式。

    322 GitHub stars~1.7k tokensUpdated 12 days ago
    DevOps & CloudAuto-check passed
  • Cicd Integration

    murphytrueman/design-system-ops

    Generate CI pipeline files and check scripts (GitHub Actions, GitLab, CircleCI, Bitbucket) that automate design system checks: token validation, hardcoded values, a11y scans, visual regression…

    206 GitHub stars~5.4k tokensUpdated 17 days ago
    DevOps & CloudAuto-check passed
  • Actions Manager

    Community-Access/accessibility-agents

    GitHub Actions: workflow runs, logs, re-runs and CI failure triage.

    423 GitHub stars~904 tokensUpdated 17 days ago
    DevOps & CloudAuto-check passed
  • Official

    Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.

    63k GitHub starsUsed in 1 repo~1.3k tokens
    DevOps & CloudAuto-check passed
  • GitHub Actions Templates

    bartstc/vite-ts-react-template

    Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications.

    122 GitHub starsUsed in 14 repos~1.9k tokens
    DevOps & CloudAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Anima CI Integration

What does Anima CI Integration do?

Configure CI/CD pipeline for automated Figma-to-code generation with Anima. Anima CI Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure CI/CD pipeline for automated Figma-to-code generation with Anima.

When should I use Anima CI Integration?

Anima CI Integration fits situations like: automating design-to-code in GitHub Actions; setting up PR-based component generation; integrating Anima into design handoff workflows; anima GitHub Actions.

How do I install Anima CI Integration in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill anima-ci-integration -a claude-code`. Or copy the skill folder (skills/.curated/anima-ci-integration in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/anima-ci-integration in your project. Claude Code loads it when a task matches its description.

How do I install Anima CI Integration in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill anima-ci-integration -a codex`. Or copy the skill folder (skills/.curated/anima-ci-integration in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/anima-ci-integration in your project. Codex loads it when a task matches its description.

Can I use Anima CI Integration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill anima-ci-integration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/anima-ci-integration, .gemini/skills/anima-ci-integration, .github/skills/anima-ci-integration and .opencode/skills/anima-ci-integration in your project.

What does Anima CI Integration need to run?

Going by SKILL.md and its folder, Anima CI Integration needs credentials named ANIMA_TOKEN, FIGMA_TOKEN, FIGMA_FILE_KEY and GH_TOKEN. Our summary lists: Node.js; A credential in ANIMA_TOKEN; A credential in FIGMA_TOKEN. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(npm:*), Grep. Compatibility (from SKILL.md): Requires Node.js 20+, approved Anima API access, current Anima SDK documentation, and authorized Figma or website source access.

Does Anima CI Integration access the network?

SKILL.md names 2 domains. As links in the text: docs.animaapp.com and docs.github.com. This is read from the text; nothing was executed.

Is Anima CI Integration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Anima CI Integration use?

Anima CI Integration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Anima CI Integration use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 187 tokens, read only when the agent opens those files.

What are the alternatives to Anima CI Integration?

Skills that share tags, products or a category with Anima CI Integration: Sync Icons (wanteddev/montage-web, 117 stars), Auto Page Sync (kennyzir/7deer_skills, 322 stars), Cicd Integration (murphytrueman/design-system-ops, 206 stars) and Actions Manager (Community-Access/accessibility-agents, 423 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Anima CI Integration?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.