Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/anima-common-errors

@820dfc8
Run it yourself

Diagnose and fix common Anima SDK design-to-code errors. Use when encountering Figma token errors, code generation failures, node not found issues, or output quality problems. Trigger with: "anima error", "anima not working", "anima debug", "figma to code error".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/anima-common-errors

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈71 tokens for metadata: the name and description. ≈1.5k when used: this file. ≈189 more on demand in 1 file.

Description uses 3.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈285 characters, or 3.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Anima Common Errors

Overview

Use this guide to diagnose design-to-code failures without widening design-file access or leaking tokens. Start from a reproducible file/node/settings tuple and use a least-privilege development credential for all verification.

Prerequisites

  • A sanitized error record with the design file identifier, node identifier, selected generation settings, timestamp, and request ID where available.
  • Scoped Anima and Figma credentials held in a secret store; never paste a personal access token into a ticket, source file, or shared diagnostic log.
  • A staging or disposable design fixture so fixes can be reproduced without mutating a production design file.

Instructions

  1. Classify the failure as authentication, file/node resolution, generator configuration, timeout/rate limit, or rendered-output quality.
  2. Reproduce it with the smallest approved frame/component and the diagnostic commands, capturing only sanitized results.
  3. Correct the matching design input, entitlement, or generation configuration and rerun only that fixture.
  4. Validate the generated file location, lint/build result, and visual review before updating a broader component set.

Error Reference

Authentication Errors

Error Root Cause Fix
Invalid Anima token Token not provisioned or expired Request new token from Anima team
Invalid Figma token PAT expired or revoked Generate new PAT: Figma > Settings > Access Tokens
Unauthorized Token lacks file access Ensure Figma PAT has file read permission

File & Node Errors

Error Root Cause Fix
File not found Wrong file key Extract from Figma URL: figma.com/file/{KEY}/...
Node not found Invalid node ID Copy node link from Figma: right-click > Copy link
No renderable content Selected a page or group Select a frame, component, or component set
Empty files record Node is empty or hidden Unhide layers; ensure node has visible content

Code Generation Errors

// Classify without printing provider messages, which can contain source details.
async function safeGenerate(anima: Anima, params: Parameters<Anima['generateCode']>[0]) {
  try {
    return await anima.generateCode(params);
  } catch (error: unknown) {
    const status = typeof error === 'object' && error !== null && 'status' in error
      ? Number(error.status)
      : undefined;
    const failureClass = status === 401 || status === 403
      ? 'authentication-or-permission'
      : status === 429
        ? 'rate-limited'
        : status !== undefined && status >= 500
          ? 'provider-transient'
          : 'generation-failed';
    console.error({ failureClass, status });
    return null;
  }
}

Output Quality Issues

Symptom Cause Fix
Messy layout No auto-layout in Figma Convert frames to auto-layout
Wrong colors Hardcoded hex instead of Figma variables Use Figma color variables/styles
Missing text Text is inside masked groups Flatten masks before generating
Extra wrappers Deeply nested groups Flatten group hierarchy
Wrong component names Unnamed Figma layers Name layers descriptively

Valid Settings Combinations

Framework Language Styling UI Library
react typescript, javascript plain_css, tailwind, inline_styles omit, mui, antd, radix, shadcn, clean_react, custom_design_system
html typescript, javascript plain_css, tailwind, inline_styles omit

Diagnostic Script

# Verify Figma token
curl -s "https://api.figma.com/v1/me" \
  -H "X-Figma-Token: ${FIGMA_TOKEN}" | jq '.handle // .err'

# Verify file access
curl -s "https://api.figma.com/v1/files/${FIGMA_FILE_KEY}" \
  -H "X-Figma-Token: ${FIGMA_TOKEN}" | jq '.name // .err'

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

  • Error classified and root cause identified
  • Valid settings matrix for reference
  • Diagnostic commands for token and file verification

Examples

When a staging generation returns Node not found, compare the copied node ID with the approved Figma link, then run the file-access diagnostic using a scoped development token. Regenerate only that small frame after correcting the ID and confirm files are emitted to the expected generated-code directory. If access is denied, the node remains hidden, or output is empty, stop the run and ask the file owner to correct permissions or visibility; do not expand the token’s scope or substitute a personal token to get past the error.

Error Handling

Failure Response
Token is invalid, expired, or over-scoped Stop the diagnostic, replace it through managed secret rotation, and avoid logging the value.
File or node cannot be resolved Verify the approved link and visibility with the design owner before retrying.
Generator times out or rate-limits Use bounded backoff or simplify the fixture; do not fan out uncontrolled retries.
Generated output is unsafe or wrong Keep it out of the main branch, correct source design/settings, and rerun targeted validation.

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides diagnostic guidance for Anima SDK errors. It includes diagnostic scripts for verifying Figma API credentials and file access using environment variables. While it processes external identifiers, it follows security best practices by recommending scoped tokens and data sanitization.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Edits files Runs commands
Modelinherit
version
2.0.0
argument-hint
[error-or-symptom]
model
inherit
All 5 allowed tools
ReadWriteEditBash(curl:*)Grep
Other metadata
effort
high
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
[
  "saas",
  "design",
  "figma",
  "anima",
  "troubleshooting"
]
compatibility
Requires Node.js 20+, approved Anima API access, current Anima SDK documentation, and authorized Figma or website source access

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/anima-common-errors