Agent skill · software engineering · jeremylongshore
anima-prod-checklist
Production readiness checklist for Anima design-to-code pipelines.
Why this skill is useful
Adds a validation script for checking Anima production readiness, which includes API connectivity and token safety checks that are not commonly found in public documentation.
What it needs
Requires bash installed locally. Requires anima, figma account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Anima Production Checklist Overview Decide whether a React/HTML design-to-code pipeline is safe to launch by checking source authorization, backend isolation, output quality, review, observability, and rollback evidence. Prerequisites Named design, engineering, security, and operations owners who can make a go/no-go decision and own the rollback path. A staging environment using separate managed Anima/Figma credentials, an allowlisted design registry, and a reproducible generated-code fixture. Defined output quality gates: source-version traceability, lint/type/build, visual/accessibility review, and no secrets in artifacts or logs. Instructions 1. Assign an owner and evidence link to every required checklist item. 2. Run the readiness script with the deployment identity in staging and retain only its redacted result. 3. Exercise a generation and rollback/disable path with an approved design component, then verify downstream code-quality and visual gates. 4. Approve progressive release only when all required checks pass; any failed security, credential, output, or fallback control is a no-go condition. Authentication & Secrets [ ] ANIMATOKEN stored in the backend secret manager (never in source) [ ] Figma token uses only endpoint-required granular read scopes and an approved expiration [ ] Separate credentials for development, staging, and production environments [ ] Rotation and revocation owners plus tested procedures are documented [ ] Tokens excluded from client bundles and build artifacts API Integration [ ] Pinned SDK uses its documented default API origin unless an approved contract says otherwise [ ] Figma rate limiting uses FigmaRestApi signals and bounded wait; Anima quotas come from the account contract [ ] Generation cache prevents redundant API calls for unchanged screens [ ] Figma file version polling detects design changes automatically [ ] Optional SDK SSE/job attachment or Figma event queue is authenticated and resumable [ ] Component mapping rules …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/anima-prod-checklist