agentmods.dev

igniteui-angular-generate-from-image-design

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

A procedure for building Angular interface views from screenshots, mockups, or wireframes using Ignite UI components.

In plain words
What is it for?
Use it to analyze a design, choose matching Ignite UI components, look up their usage, create a theme, and implement the resulting Angular view.
Why use it?
It helps translate a visual design into suitable Angular components while checking their documentation and theming requirements first.

Skill for Claude CodeCodex

not rated 136 today A scan 124 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-angular-generate-from-image-design
Any agent
npx skills add IgniteUI/igniteui-cli --skill igniteui-angular-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-angular-generate-from-image-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-angular-generate-from-image-design.svg)](https://agentmods.dev/skills/igniteui/igniteui-cli/igniteui-angular-generate-from-image-design)
Your own site
<a href="https://agentmods.dev/skills/igniteui/igniteui-cli/igniteui-angular-generate-from-image-design"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-angular-generate-from-image-design.svg" alt="Measured on agentmods" height="20"></a>
Per session 124 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,544 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.00124 $0.03544
Opus 5 $0.00062 $0.01772
Sonnet 5 $0.00025 $0.00709
Haiku 4.5 $0.00012 $0.00354

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

Security

Grade A, and why

igniteui-angular-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 4d 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.

packages/igx-templates/igx-ts/projects/ai-config/files/skills/igniteui-angular-generate-from-image-design/SKILL.md · 227 lines

How it starts

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

Implementing Ignite UI Angular 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 references/component-mapping.md and references/gotchas.md.
  3. This skill is Angular-only. Check package layout 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-angular-theming skill; use the igniteui-theming MCP tools instead of styling from memory.
  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, layout structure.
  2. Confirm package layout if needed - this skill is Angular-only; check package layout 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 using 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, 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 · 227 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. 4d ago First seen · 227 lines · 124 tokens per session scan A 2f8c41d8bf78

Subscribe to this mod's changes

igniteui-angular-generate-from-image-design is a skill published in the GitHub repository IgniteUI/igniteui-cli (136 stars, last pushed today), licensed MIT. It adds 124 tokens to every session and 3,544 once invoked, about $0.0006 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.

Design and UXFrontendReactangularbuild-automationcliignite-uijquery
Related

Other skills, from other repositories

authoring-patterns

Convert validated playground templates or HTML compositions into reusable pattern files (.examples.ts) in the pattern library. Use this skill whenever the user wants to save, persist, store, or catalog a template, prototype, composition, or playground result as a reusable pattern. Trigger on phrases like "save as…

NVIDIA/elements · 106 tokens

audit-accessibility

Unified accessibility auditing workflow across static analysis, runtime testing, ARIA patterns, keyboard navigation, and color contrast. Use this skill whenever the user mentions accessibility, a11y, WCAG, ARIA roles, axe tests, screen readers, focus management, keyboard navigation, color contrast, or wants to audit…

NVIDIA/elements · 98 tokens

authoring-tests

Write and run automated tests for Elements components including unit, accessibility, visual, SSR, and lighthouse tests. Use this skill whenever the user wants to write, create, update, or debug test files (.test.ts, .test.axe.ts, .test.visual.ts, .test.ssr.ts, .test.lighthouse.ts). Also trigger when the user asks…

NVIDIA/elements · 113 tokens

frontend-review

Frontend Code Review (Angular & React): Expert review of frontend code focusing on Angular, React, component architecture, state management, performance, accessibility, and UI patterns. Use whenever the user wants a review of frontend code, component design, state management, or mentions Angular, React, TypeScript…

camilooscargbaptista/cto-toolkit · 100 tokens

elvia-design-system

Reference for UI components in Elvia's design system ("Elvis"). Covers component-specific guidelines for sizing, coloring, types, ordering, labeling, accessibility attributes, CSS setup, and web-component registration. Use when building, reviewing, or fixing UI in an Elvia frontend, even if the request doesn't name…

3lvia/designsystem · 94 tokens

chakra-ui-builder

Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…

chakra-ui/chakra-ui · 214 tokens