translating-figma-to-nextjs
Skill1 starsChanged 3 months agoMITView on GitHub
Use when converting Figma designs or design-system components into production Next.js and React code while preserving fidelity, reuse, responsiveness, and maintainable component boundaries.
In this repository65 other files it gives its agents.
- analyzing-change-blast-radiusSkill
- analyzing-developer-career-opportunitiesSkill
- art-directing-web-interfacesSkill
- assessing-developer-proficiencySkill
- auditing-dependency-riskSkill
- auditing-pixel-perfect-frontendSkill
- bootstrapping-modern-web-appsSkill
- brag-slimSkill
- building-brand-guidelinesSkill
- building-conversion-product-pagesSkill
- building-developer-career-roadmapsSkill
- building-hybrid-game-assetsSkill
- building-premium-nextjs-interfacesSkill
- building-project-showcasesSkill
- building-regression-testsSkill
- building-reliable-node-api-boundariesSkill
- choosing-application-architectureSkill
- craft-premium-motionSkill
- creating-character-sprite-pipelinesSkill
- defining-brand-strategySkill
- designing-action-combatSkill
- designing-developer-portfolio-evidenceSkill
- designing-relational-data-modelsSkill
- designing-software-boundariesSkill
- designing-test-strategiesSkill
- designing-ui-systemsSkill
- designing-visual-identitiesSkill
- documenting-architecture-decisionsSkill
- editing-for-clarity-and-toneSkill
- engineering-gsap-animationsSkill
- evaluating-developer-proficiencySkill
- evolving-postgres-schemas-safelySkill
- humanizing-generated-proseSkill
- implementing-reference-faithful-uiSkill
- investigating-codebase-semanticallySkill
- managing-implementation-slicesSkill
- mapping-existing-codebase-structureSkill
- naming-brands-and-productsSkill
- optimizing-frontend-motion-performanceSkill
- orchestrating-cinematic-web-motionSkill
- planning-codebase-changes-with-evidenceSkill
- planning-engineering-workSkill
- planning-launch-distributionSkill
- planning-safe-refactorsSkill
- planning-written-communicationSkill
- preparing-project-launchSkill
- profiling-postgres-query-performanceSkill
- reconstructing-images-as-threejsSkill
- reviewing-api-securitySkill
- reviewing-apple-platform-interfacesSkill
- reviewing-pull-requestsSkill
- reviewing-web-securitySkill
- selecting-working-methodsSkill
- shipping-github-vercel-changesSkill
- teaching-developer-conceptsSkill
- testing-integration-boundariesSkill
- testing-playable-gamesSkill
- testing-web-applications-end-to-endSkill
- threat-modeling-applicationsSkill
- tracing-code-execution-pathsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Read the Figma hierarchy before coding: frames, auto-layout behavior, constraints, variants, variables, typography, grids, and component …
- Very specific: line 12
Use Next.js image/font facilities when they fit the repository.
- Distinctive: line 13
Keep decorative layers separate from semantic content so responsiveness does not depend on fragile DOM ordering.
- Distinctive: line 26
Avoid exporting raw Figma CSS as production architecture.
- Distinctive: line 27
Avoid unnecessary absolute positioning.
- Distinctive: line 29
If an icon or asset is missing, source a legitimate equivalent rather than redrawing a brand mark inaccurately.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Translating Figma to Next.js
Workflow
- Read the Figma hierarchy before coding: frames, auto-layout behavior, constraints, variants, variables, typography, grids, and component instances.
- Map design primitives to existing code primitives before inventing new ones.
- Infer responsive intent from constraints and neighboring frames; do not encode one screenshot as absolute pixels everywhere.
- Use Next.js image/font facilities when they fit the repository.
- Keep decorative layers separate from semantic content so responsiveness does not depend on fragile DOM ordering.
- Implement reusable variants only where Figma shows a real component family or the product reuses the pattern.
- Render and compare against Figma at the target frame dimensions.
Fidelity priorities
- geometry;
- typography;
- image crop;
- color and surface treatment;
- interaction and motion.
Guardrails
- Existing app architecture wins over generated Figma structure.
- Avoid exporting raw Figma CSS as production architecture.
- Avoid unnecessary absolute positioning.
- Preserve accessible names when splitting or animating text.
- If an icon or asset is missing, source a legitimate equivalent rather than redrawing a brand mark inaccurately.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.