anima-core-workflow-b
Clone websites to React/HTML code and customize Anima output with AI. Use when converting live websites to code, customizing generated components, or building design-system-aware code from URL screenshots. Trigger: "anima website to code", "anima URL clone", "anima AI customization", "website to react", "clone website to code".
What this skill does
# Anima Core Workflow B — Website-to-Code & AI Customization
## Overview
Secondary workflow: use Anima to clone live websites into React/HTML code and customize generated output with AI-powered code modification. Anima supports URL-to-code conversion alongside Figma-to-code.
## Prerequisites
- Completed `anima-install-auth` setup
- Understanding of Anima's code generation settings
## Instructions
### Step 1: Website-to-Code Conversion
```typescript
// src/workflows/website-to-code.ts
// Anima can clone any public website and generate React or HTML code
import { Anima } from '@animaapp/anima-sdk';
const anima = new Anima({
auth: { token: process.env.ANIMA_TOKEN! },
});
// Note: URL-to-code may use a different API endpoint
// Check docs.animaapp.com for current availability
async function cloneWebsiteToReact(url: string, outputDir: string) {
// Anima's website-to-code feature captures the page and generates code
// This is available via the Anima Playground or API (partner access)
// For Figma-based workflow, use the Figma plugin to import website screenshots
// then generate code from the imported frames
console.log(`Cloning ${url} to React components...`);
// Process via Figma intermediary:
// 1. Use Anima Figma plugin to capture website layout
// 2. Generate code from the captured frames
// 3. Customize with AI post-processing
}
```
### Step 2: Post-Generation Customization
```typescript
// src/workflows/customize-output.ts
import fs from 'fs';
import path from 'path';
interface CustomizationRule {
pattern: RegExp;
replacement: string;
description: string;
}
// Apply project-specific customizations to Anima output
function customizeGeneratedCode(
files: Array<{ fileName: string; content: string }>,
rules: CustomizationRule[],
): Array<{ fileName: string; content: string }> {
return files.map(file => {
let content = file.content;
for (const rule of rules) {
content = content.replace(rule.pattern, rule.replacement);
}
return { ...file, content };
});
}
// Common customization rules
const PROJECT_RULES: CustomizationRule[] = [
{
pattern: /className="([^"]+)"/g,
replacement: 'className={cn("$1")}',
description: 'Wrap Tailwind classes with cn() utility',
},
{
pattern: /import React from 'react'/g,
replacement: "import React from 'react';\nimport { cn } from '@/lib/utils'",
description: 'Add cn import for className merging',
},
{
pattern: /export default function (\w+)/g,
replacement: 'export const $1: React.FC = function $1',
description: 'Use React.FC type annotation',
},
];
```
### Step 3: Design Token Mapper
```typescript
// src/workflows/token-mapper.ts
// Map Anima's raw Tailwind classes to your design system tokens
interface TokenMap {
colors: Record<string, string>; // Anima color → your token
spacing: Record<string, string>; // Anima spacing → your token
typography: Record<string, string>; // Anima font → your token
}
const tokenMap: TokenMap = {
colors: {
'bg-\\[#1a1a2e\\]': 'bg-primary',
'text-\\[#e94560\\]': 'text-accent',
'bg-\\[#16213e\\]': 'bg-surface',
},
spacing: {
'p-\\[24px\\]': 'p-6',
'gap-\\[16px\\]': 'gap-4',
'mt-\\[32px\\]': 'mt-8',
},
typography: {
'text-\\[32px\\]': 'text-3xl',
'font-\\[600\\]': 'font-semibold',
},
};
function applyDesignTokens(content: string, map: TokenMap): string {
let result = content;
for (const category of Object.values(map)) {
for (const [from, to] of Object.entries(category)) {
result = result.replace(new RegExp(from, 'g'), to);
}
}
return result;
}
```
### Step 4: Multi-Component Output Organizer
```typescript
// src/workflows/organizer.ts
import fs from 'fs';
import path from 'path';
function organizeGeneratedFiles(
files: Array<{ fileName: string; content: string }>,
baseDir: string,
): void {
// Organize by component type
const structure: Record<string, string> = {
'.tsx': 'components',
'.vue': 'components',
'.css': 'styles',
'.ts': 'types',
'.html': 'pages',
};
for (const file of files) {
const ext = path.extname(file.fileName);
const subDir = structure[ext] || 'misc';
const dir = path.join(baseDir, subDir);
fs.mkdirSync(dir, { recursive: true });
fs.writeFileSync(path.join(dir, file.fileName), file.content);
}
// Generate barrel export
const components = files.filter(f => f.fileName.endsWith('.tsx'));
if (components.length > 0) {
const exports = components.map(f => {
const name = path.basename(f.fileName, '.tsx');
return `export { default as ${name} } from './${name}';`;
});
fs.writeFileSync(
path.join(baseDir, 'components', 'index.ts'),
exports.join('\n') + '\n'
);
}
}
```
## Output
- Website cloning to React/HTML via Figma intermediary
- Post-generation customization rules engine
- Design token mapper for project consistency
- File organizer with barrel exports
## Error Handling
| Error | Cause | Solution |
|-------|-------|----------|
| URL not accessible | Website blocks scraping | Use Figma plugin to capture manually |
| Output doesn't match design | Complex animations/interactions | Simplify to static layout first |
| Token mapping misses | New colors/spacing in design | Update token map after each generation |
## Resources
- [Anima API](https://docs.animaapp.com/docs/anima-api)
- [Anima Playground](https://www.animaapp.com)
- [Anima Blog: GenAI Customization](https://www.animaapp.com/blog/genai/genai-figma-to-code-6-examples-of-how-to-use-animas-new-ai-code-customization/)
## Next Steps
For common errors and debugging, see `anima-common-errors`.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.