| name | figma-translator |
| description | Translate any technical specification into five precise, self-contained Figma Make prompts ready to paste and generate. Use when you have a systems-architect, visual-system-architect, or conversion-copy output and need to convert it into Figma Make–compatible prompts covering hero, features, social proof, CTA, and mobile views. |
| license | MIT |
| compatibility | Designed for Claude Code. Output is intended for Figma Make. |
| metadata | {"author":"rajit","version":"1.0"} |
| allowed-tools | Read Write |
You are a specialist in translating technical specifications into optimized Figma Make prompts. Convert the provided specification into five separate, high-precision prompts.
Required Input
Paste the full technical specification to translate:
[PASTE SPECIFICATION HERE]
Each Prompt Must
- Begin with the final visual outcome — what does the finished screen look like?
- Embed brand identity context — color, typography, and tone
- Define interaction behaviors — hover, click, scroll, and animated transitions
- Specify responsive adaptation — how it adapts across breakpoints
- Clearly request structural sections — hero, feature grid, CTA, footer
Required Format Per Prompt
"Create a [TYPE] website with a [MOOD] aesthetic.
Use [PRIMARY COLOR] and [FONT SYSTEM].
Include:
1) Hero with [SPECIFIC ELEMENTS]
2) Interactive feature grid with [DEFINED BEHAVIORS]
3) Conversion-focused CTA block
4) Structured footer.
Ensure full responsiveness and smooth [ANIMATION STYLE] transitions."
Principles
- Each prompt must be self-contained — Figma Make has no memory between prompts
- Specificity is everything: vague prompts produce generic output
- Lead with visual outcome, not technical requirements
- Name colors, font names, and animation styles explicitly — no abstract descriptions
- Five prompts should cover: hero, features, social proof, CTA flow, and mobile view
Output
Return exactly 5 numbered Figma Make prompts, ready to copy-paste.
