> anima-core-workflow-a
Build automated Figma-to-React pipeline with the Anima SDK. Use when automating design handoff, building CI/CD design-to-code workflows, or creating a design system code generator from Figma components. Trigger: "anima design pipeline", "figma to react pipeline", "automated design handoff", "anima component generator".
curl "https://skillshub.wtf/jeremylongshore/claude-code-plugins-plus-skills/anima-core-workflow-a?format=md"Anima Core Workflow A — Figma-to-React Pipeline
Overview
Primary workflow: automated pipeline that watches a Figma file, generates React components whenever the design changes, and integrates them into your codebase. This replaces manual design handoff with continuous design-to-code automation.
Prerequisites
- Completed
anima-install-authsetup - Figma file with organized components (auto-layout recommended)
- React project (Next.js, Vite, or CRA)
Instructions
Step 1: Design System Scanner
// src/pipeline/figma-scanner.ts
import { Anima } from '@animaapp/anima-sdk';
interface FigmaComponent {
nodeId: string;
name: string;
type: 'COMPONENT' | 'FRAME' | 'COMPONENT_SET';
}
const anima = new Anima({
auth: { token: process.env.ANIMA_TOKEN! },
});
// Fetch all top-level components from a Figma page
async function scanFigmaComponents(fileKey: string): Promise<FigmaComponent[]> {
const response = await fetch(
`https://api.figma.com/v1/files/${fileKey}/components`,
{ headers: { 'X-Figma-Token': process.env.FIGMA_TOKEN! } }
);
const data = await response.json();
return data.meta.components.map((comp: any) => ({
nodeId: comp.node_id,
name: comp.name,
type: comp.containing_frame?.type || 'COMPONENT',
}));
}
Step 2: Batch Code Generator
// src/pipeline/batch-generator.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! },
});
interface GenerationConfig {
fileKey: string;
outputDir: string;
settings: {
language: 'typescript' | 'javascript';
framework: 'react' | 'vue' | 'html';
styling: 'tailwind' | 'css' | 'styled-components';
uiLibrary?: 'none' | 'mui' | 'antd' | 'shadcn';
};
}
async function generateComponentBatch(
config: GenerationConfig,
nodeIds: string[],
): Promise<{ generated: number; failed: string[] }> {
const failed: string[] = [];
let generated = 0;
fs.mkdirSync(config.outputDir, { recursive: true });
// Generate each component (Anima processes one node at a time)
for (const nodeId of nodeIds) {
try {
const { files } = await anima.generateCode({
fileKey: config.fileKey,
figmaToken: process.env.FIGMA_TOKEN!,
nodesId: [nodeId],
settings: config.settings,
});
for (const file of files) {
const filePath = path.join(config.outputDir, file.fileName);
fs.writeFileSync(filePath, file.content);
console.log(`Generated: ${file.fileName}`);
}
generated++;
} catch (err) {
console.error(`Failed to generate node ${nodeId}:`, err);
failed.push(nodeId);
}
// Rate limit: Anima API has per-minute limits
await new Promise(r => setTimeout(r, 2000));
}
return { generated, failed };
}
export { generateComponentBatch, GenerationConfig };
Step 3: Figma Change Detection
// src/pipeline/change-detector.ts
interface FileVersion {
id: string;
created_at: string;
label: string;
}
async function getLatestVersion(fileKey: string): Promise<FileVersion> {
const response = await fetch(
`https://api.figma.com/v1/files/${fileKey}/versions`,
{ headers: { 'X-Figma-Token': process.env.FIGMA_TOKEN! } }
);
const data = await response.json();
return data.versions[0];
}
// Check if file changed since last generation
let lastVersionId = '';
async function hasDesignChanged(fileKey: string): Promise<boolean> {
const latest = await getLatestVersion(fileKey);
if (latest.id !== lastVersionId) {
lastVersionId = latest.id;
return true;
}
return false;
}
export { hasDesignChanged, getLatestVersion };
Step 4: Full Pipeline Runner
// src/pipeline/run.ts
import { scanFigmaComponents } from './figma-scanner';
import { generateComponentBatch, GenerationConfig } from './batch-generator';
import { hasDesignChanged } from './change-detector';
const config: GenerationConfig = {
fileKey: process.env.FIGMA_FILE_KEY!,
outputDir: './src/components/generated',
settings: {
language: 'typescript',
framework: 'react',
styling: 'tailwind',
uiLibrary: 'shadcn',
},
};
async function runPipeline() {
console.log('Scanning Figma file for components...');
const components = await scanFigmaComponents(config.fileKey);
console.log(`Found ${components.length} components`);
console.log('Generating code...');
const result = await generateComponentBatch(
config,
components.map(c => c.nodeId)
);
console.log(`\nPipeline complete: ${result.generated} generated, ${result.failed.length} failed`);
}
// Watch mode: re-generate on design changes
async function watchMode() {
console.log('Watching for Figma design changes...');
setInterval(async () => {
if (await hasDesignChanged(config.fileKey)) {
console.log('Design changed — regenerating...');
await runPipeline();
}
}, 60000); // Check every minute
}
runPipeline().catch(console.error);
Output
- Automated Figma component scanning and enumeration
- Batch code generation for entire design systems
- Change detection for continuous design-to-code sync
- Watch mode for iterative design development
Error Handling
| Error | Cause | Solution |
|---|---|---|
| Rate limited | Too many API calls | Add 2s delay between component generations |
| Component not renderable | Figma node is group, not frame | Ensure components use auto-layout |
| Inconsistent output | Complex nested structures | Flatten deep nesting in Figma |
| Missing styles | Custom fonts not available | Map fonts in Anima settings |
Resources
Next Steps
For website-to-code cloning, see anima-core-workflow-b.
> related_skills --same-repo
> fathom-cost-tuning
Optimize Fathom API usage and plan selection. Trigger with phrases like "fathom cost", "fathom pricing", "fathom plan".
> fathom-core-workflow-b
Sync Fathom meeting data to CRM and build automated follow-up workflows. Use when integrating Fathom with Salesforce, HubSpot, or custom CRMs, or creating automated post-meeting email summaries. Trigger with phrases like "fathom crm sync", "fathom salesforce", "fathom follow-up", "fathom post-meeting workflow".
> fathom-core-workflow-a
Build a meeting analytics pipeline with Fathom transcripts and summaries. Use when extracting insights from meetings, building CRM sync, or creating automated meeting follow-up workflows. Trigger with phrases like "fathom analytics", "fathom meeting pipeline", "fathom transcript analysis", "fathom action items sync".
> fathom-common-errors
Diagnose and fix Fathom API errors including auth failures and missing data. Use when API calls fail, transcripts are empty, or webhooks are not firing. Trigger with phrases like "fathom error", "fathom not working", "fathom api failure", "fix fathom".