sergekostenchuk/ui-ux-agent-skill-system

figma-design-to-code-bridge

Translate Figma frames and design context into implementation-ready frontend plans, component mappings, and code handoffs.

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill figma-design-to-code-bridge

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

Figma Design To Code Bridge

Use this skill after figma-context-reader when the goal is implementation. The output is not "code by screenshot"; it is a mapping from design intent, tokens, and components to the existing codebase.

Modes

  • handoff-plan: create a build/refactor plan from a Figma frame.
  • component-map: map Figma components/variants to existing code components.
  • code-connect: prepare or review Figma Code Connect work.
  • gap-report: identify where the design and code system diverge.
  • implementation-route: hand off to webapp-ui-skill or marketing-site-skill.

Workflow

  1. Get Figma context through figma-context-reader or a provided context brief.
  2. Inspect the local codebase before recommending component choices.
  3. If Code Connect is requested, invoke the installed figma:figma-code-connect skill before Code Connect-specific work.
  4. Map tokens, components, variants, states, and responsive constraints to local implementation primitives.
  5. Route dense product/app work to webapp-ui-skill; route public landing/product pages to marketing-site-skill.
  6. Require local visual verification after implementation. Figma match alone is not validation.

Output Shape

Use assets/design-to-code-handoff.md.

Decision Rules

  • Prefer existing project components and design tokens over generating one-off CSS.
  • Preserve UX intent when exact visual parity conflicts with accessibility, responsiveness, or codebase conventions.
  • Treat Figma-generated code or MCP-generated code as a draft until reviewed against local architecture.
  • If the Figma file lacks states, include loading, empty, error, disabled, focus, hover, and mobile states in the implementation plan.

Safety And Privacy

  • Treat non-public Figma files, screenshots, variables, component names, and source code as sensitive.
  • Do not send private code or Figma context to external tools without explicit approval and a data-transfer note.
  • Do not overwrite local components simply to match a Figma frame; propose a scoped implementation plan first.

Validation And Eval

  • Verify that the handoff includes both Figma-to-code component mapping and local validation steps.
  • For implemented work, require browser or screenshot evidence from the local app.
  • Use evals/evals.json to test app-frame routing, marketing-page routing, and Code Connect gap behavior.

Resources

  • Read $CODEX_SKILLS_DIR/senior-figma-orchestrator/references/figma-mcp-compatibility.md when current Figma tools matter.

Relacionados por tarea

del mismo repositorio

Más Skills

Todos los Skills
sergekostenchuk
Comunidad

admin-ui-builder

Use when admin/CMS/back-office screens need to be built or specified after admin-ui-orchestrator defines roles, permissions, workflows, and safety gates. Covers tables, forms, editors, moderation queues, dashboards, CRUD surfaces, and state coverage without production destructive actions.

Instalaciones / 1h
1
GitHub Stars
35
Actualizado
13 sept
sergekostenchuk
Comunidad

admin-ui-orchestrator

Use when a project needs admin/CMS/back-office UI architecture: roles, permissions, content workflows, AI assistant boundaries, audit logs, destructive-action confirmations, and builder handoff. Planning only; do not perform production admin actions or expose secrets.

Instalaciones / 1h
1
GitHub Stars
35
Actualizado
13 sept
sergekostenchuk
Comunidad

analytics-setup-architect

Use when a website or web app needs privacy-aware analytics architecture: GA4, Yandex Metrica, self-hosted analytics, consent, UTM, event taxonomy, funnels, dashboards, and launch verification. Do not mutate real analytics accounts or store credentials without explicit approval.

Instalaciones / 1h
1
GitHub Stars
35
Actualizado
13 sept
sergekostenchuk
Comunidad

editorial-quality-gate

Review public site content for editorial quality, source support, prompt residue, duplicate blocks, translation drift, hidden filler, and human usefulness before SEO or LLM-friendly publication. Use this skill when the user asks to quality-gate news briefs, longform explainers, blog posts, topic pages, project pages, translated content, or generated article drafts without changing the live publishing pipeline.

Instalaciones / 1h
1
GitHub Stars
35
Actualizado
13 sept