create-screen-from-image

Reconstructs UI screenshots into Glyvio framework screens via visual decomposition and component catalog mapping.

1|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/devena/glyvio-forge --skill create-screen-from-image-devena
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-screen-from-image
Source: https://github.com/devena/glyvio-forge/tree/main/claude/skills/create-screen-from-image
Command: npx skills add https://github.com/devena/glyvio-forge --skill create-screen-from-image-devena

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a UI screenshot into working framework code usually requires manually interpreting the design and guessing which components to use. This Skill reads the actual image, decomposes it into a structured component tree, and generates a Glyvio screen that faithfully matches the original pixels. ## Core Features & Use Cases - Vision-driven decomposition: Reads the screenshot directly and breaks it down top-down into page type, app bar, layout regions, repeated cells, and atomic widgets. - Catalog-grounded mapping: Maps every visual element to a concrete glyvio_core design class verified against @types, preferring the most specific component available. - Spec-gated code generation: Produces an approved visual spec (JSON component tree plus analysis summary) before delegating code generation to the matching create-* page skill. - Use Case: A designer sends a PNG of an orders list screen. The Skill identifies it as a list page, maps each card element to catalog components, gets the spec approved, then generates the screen with correct routes, menu registration, and view permissions. ## Quick Start Provide a screenshot file path, target entity, plugin namespace, route path, and menu group, then ask the agent to recreate the screen from the image using Glyvio components.

Frequently Asked Questions about create-screen-from-image

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a UI screenshot into working frontend code?▼

Provide the image file path, target entity, plugin namespace, route path, and menu group. The skill reads the image, decomposes it into a component tree mapped to glyvio_core classes, gets your approval on the visual spec, then generates the screen code via the matching create-* page skill.

How does the skill choose which components to use for each visual element?▼

Every element is mapped against the component catalog, which is the ground truth for visual-to-class mapping. The skill always prefers the most specific component, such as ChipDesign over a colored BoxDesign, and verifies each class exists in @types before using it.

Can it generate a screen without the actual image file?▼

No. The skill is vision-driven and requires the actual screenshot file (PNG or JPG). If you only describe the screen in text, it stops and asks for the image rather than guessing the structure.

What happens when a UI element has no matching Glyvio component?▼

The skill flags the un-mappable element explicitly in the visual analysis instead of inventing a substitute. It never hand-rolls components that the catalog does not cover or uses classes outside @types.

How are entity and foreign key fields handled in generated forms?▼

Entity and FK fields must use the entity-specific subclass of EntityAutocompleteSingleTextfieldDesign. The base class and generic StringTextfieldDesign are never allowed for these fields.