agentmods.dev

igniteui-react-generate-from-image-design

igniteui-react-generate-from-image-design is a skill for Claude Code, Codex from IgniteUI/igniteui-cli. It costs 137 tokens per session (3,768 once invoked), scanned A, original, MIT.

A guide for building React screens from design images with Ignite UI components, which are ready-made interface elements for web apps. It covers interpreting screenshots, mockups, or wireframes and matching them to React components.

In plain words
What is it for?
Use it to implement React views from images, select suitable Ignite UI components, verify their documentation, and apply React-specific themes and practices.
Why use it?
It reduces guesswork when translating a visual design into JSX and TypeScript. It also guides component discovery, documentation checks, package choices, and theming.

Skill for Claude CodeCodex

not rated 136 yesterday A scan 137 tokens original MIT
View the source file IgniteUI/igniteui-cli
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/igniteui/igniteui-cli/igniteui-react-generate-from-image-design
Any agent
npx skills add IgniteUI/igniteui-cli --skill igniteui-react-generate-from-image-design
Clone the repo
git clone --depth 1 https://github.com/IgniteUI/igniteui-cli

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for igniteui-react-generate-from-image-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-react-generate-from-image-design.svg)](https://agentmods.dev/skills/igniteui/igniteui-cli/igniteui-react-generate-from-image-design)
Your own site
<a href="https://agentmods.dev/skills/igniteui/igniteui-cli/igniteui-react-generate-from-image-design"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-react-generate-from-image-design.svg" alt="Measured on agentmods" height="20"></a>
Per session 137 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,768 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00137 $0.03768
Opus 5 $0.00068 $0.01884
Sonnet 5 $0.00027 $0.00754
Haiku 4.5 $0.00014 $0.00377

Measured 5d ago against content hash 84015e821db2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

igniteui-react-generate-from-image-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

packages/cli/templates/react/igr-ts/projects/ai-config/files/skills/igniteui-react-generate-from-image-design/SKILL.md · 230 lines

How it starts

The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implementing Ignite UI React Views from Design Images

MANDATORY AGENT PROTOCOL

Before writing any implementation code, you must complete these steps in order:

  1. Analyze the image and identify all visible regions and UI patterns.
  2. Read reference/component-mapping.md and reference/gotchas.md.
  3. This skill is React-only. Check package routing, theme CSS imports, or licensing only when imports, packages, or theming depend on it.
  4. To apply a theme, use the theming workflow from this skill and the dedicated igniteui-react-customize-theme skill; use the igniteui-theming MCP tools instead of styling from memory. This skill is React-only, so hardcode platform: "react" in theme-generation calls.
  5. Call get_doc for every chosen component family before using it.
  6. Only then start coding.

Workflow

  1. Analyze the design image - Read the image, identify every UI section, component, and layout structure.
  2. Confirm package routing or theme setup if needed - this skill is React-only; check package routing, theme CSS imports, or licensing only when imports, packages, or theming depend on it.
  3. Discover components - Call list_components with targeted filters to find matching components for each UI pattern.
  4. Look up component docs - Call get_doc for every chosen component family before coding.
  5. Generate theme - (a) To generate a theme, first extract colors and create a color palette using create_palette or create_custom_palette depending on the scenario. Then extract elevations and call create_elevations. Then extract typography and call create_typography. Then call create_theme with the palette, elevations, and typography. (b) After a theme exists, prefer design tokens, or scoped semantic CSS variables over raw literals. (c) For every Ignite UI component, call get_component_design_tokens, map extracted image tokens to token roles, then call create_component_theme with the tokens differing from the global theme for the specific component.
  6. Implement - Build the screenshot-first layout, data, and view components.
  7. Refine - Use the set_size, set_spacing, and set_roundness tools to refine the view's visual fidelity against the image, then iterate on implementation and theming until the view matches the design closely.
  8. Validate - Build, test, run, compare against the image, and fix differences.

Read the full file on GitHub · 230 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 230 lines · 137 tokens per session scan A 84015e821db2

Subscribe to this mod's changes

igniteui-react-generate-from-image-design is a skill published in the GitHub repository IgniteUI/igniteui-cli (136 stars, last pushed yesterday), licensed MIT. It adds 137 tokens to every session and 3,768 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

FrontendReactWriting and docsangularbuild-automationcliignite-uijquery
Related

Other skills, from other repositories

update-cnw-templates

Update the CNW (create-nx-workspace) template repos (nrwl/empty-template, nrwl/react-template, etc.) to a target nx version via nx migrate, verify each repo, and open a PR per repo. Clones repos it needs - assumes no local checkout. Use when asked to "update the CNW templates", "migrate the templates to nx X", "bump…

nrwl/nx · 107 tokens

authoring-projects

Author a new standalone NVIDIA Elements workspace project containing a Lit component, including package files, the five test types, Wireit tasks, workspace and CI registration, metadata generation, documentation-site integration, dependency-lint configuration, and generated lock/notice files. Use when creating or…

NVIDIA/elements · 97 tokens

authoring-components

Guide for creating new Elements components with all required files, base classes, metadata patterns, and test boilerplate. Use this skill whenever the user wants to create, scaffold, or set up a new component from scratch, needs to understand the required 10-file structure, asks about base classes and mixins…

NVIDIA/elements · 109 tokens

guidance-api-design

Component API design patterns following Elements conventions for properties, attributes, CSS custom properties, slots, and events. Use this skill whenever the user is designing or deciding on a component API, choosing between properties vs attributes vs slots, naming CSS custom properties, designing events, avoiding…

NVIDIA/elements · 103 tokens

authoring-examples

Guidelines for writing example template files (.examples.ts) including naming conventions, @summary JSDoc comments, and stateless HTML patterns. Use this skill whenever the user creates, modifies, or reviews .examples.ts files, asks about example naming rules (PascalCase, 3-word max, no component prefix), needs to…

NVIDIA/elements · 105 tokens

ionic-framework-docs

Ionic Framework 8.x — UI components, Angular/React/Vue integrations, theming, CLI, Capacitor, navigation.

pledgeandgrow/pledge-skills · 32 tokens