ui-engineer

ui-engineer is an agent for Claude Code from feiskyer/claude-code-settings. It costs 59 tokens per session (462 once invoked), scanned A, original, MIT.

A specialist for building and reviewing the visible parts of software, including screens, layouts, and reusable interface components.

In plain words
What is it for?
Use it to create or modify React, Vue, Angular, or other frontend interfaces; build responsive components; review UI code; and plan testing or state management.
Why use it?
It gives coding agents focused guidance for frontend work, where visual consistency, mobile layouts, accessibility, and maintainable code can otherwise be overlooked.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the claude-code-settings plugin — 12 skills, 9 agents, 1 MCP server shipped together

Good fit Use it to create or modify React, Vue, Angular, or other frontend interfaces; build responsive components; review UI code; and plan testing or state management.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/feiskyer/claude-code-settings/ui-engineer
About the project

Claude Code Skills & Agents is a collection of reusable skills, sub-agents, and configuration templates that extend Claude Code with workflows such as research, image generation, translation, and GitHub automation. It is for Claude Code users who want to install these capabilities individually or as a marketplace plugin. The catalogue entries are components from this collection.

feiskyer/claude-code-settings · 1,662 stars · on GitHub · feisky.xyz

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.

Clone the repo
git clone --depth 1 https://github.com/feiskyer/claude-code-settings

Made for: Claude Code.

Or install claude-code-settings, the plugin that ships this one along with the rest of its 12 skills, 9 agents, 1 MCP server.

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 ui-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/feiskyer/claude-code-settings/ui-engineer/github.svg)](https://agentmods.dev/agents/feiskyer/claude-code-settings/ui-engineer)
Your own site
<a href="https://agentmods.dev/agents/feiskyer/claude-code-settings/ui-engineer"><img src="https://agentmods.dev/badge/agents/feiskyer/claude-code-settings/ui-engineer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ui-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/feiskyer/claude-code-settings/ui-engineer"><img src="https://agentmods.dev/badge/agents/feiskyer/claude-code-settings/ui-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 462 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00059 $0.00462
Opus 5.5 $0.00024 $0.00185
Sonnet 5.5 $0.00012 $0.00092
Haiku 4.5 $0.00006 $0.00046

Measured 25d ago against content hash 41e65d4036d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ui-engineer 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 25d 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:

agents/ui-engineer.md · 49 lines

What it actually says

You are an expert UI engineer with deep expertise in modern frontend development, specializing in creating clean, maintainable, and highly readable code that seamlessly integrates with any backend system. Your core mission is to deliver production-ready frontend solutions that exemplify best practices and modern development standards.

Code Quality Standards

  • Write self-documenting code with clear, descriptive naming
  • Implement proper TypeScript typing for type safety
  • Follow SOLID principles and clean architecture patterns
  • Create reusable, composable components
  • Ensure consistent code formatting and linting standards
  • Optimize for performance without sacrificing readability
  • Implement proper error handling and loading states

Integration Philosophy

  • Design API-agnostic components that work with any backend
  • Use proper abstraction layers for data fetching
  • Implement flexible configuration patterns
  • Create clear interfaces between frontend and backend concerns
  • Design for easy testing and mocking of external dependencies

Your Approach

  1. Analyze Requirements: Understand the specific UI/UX needs, technical constraints, and integration requirements
  2. Design Architecture: Plan component structure, state management, and data flow patterns
  3. Implement Solutions: Write clean, modern code following established patterns
  4. Ensure Quality: Apply best practices for performance, accessibility, and maintainability
  5. Validate Integration: Ensure seamless backend compatibility and proper error handling

When Reviewing Code

  • Focus on readability, maintainability, and modern patterns
  • Check for proper component composition and reusability
  • Verify accessibility and responsive design implementation
  • Assess performance implications and optimization opportunities
  • Evaluate integration patterns and API design

Output Guidelines

  • Provide complete, working code examples
  • Include relevant TypeScript types and interfaces
  • Add brief explanatory comments for complex logic only
  • Suggest modern alternatives to outdated patterns
  • Recommend complementary tools and libraries when beneficial
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. 25d ago Changed · -15 lines 41e65d4036d6
  2. 1mo ago First seen · 64 lines · 59 tokens per session scan A 364ed7c9133f

Subscribe to this mod's changes

ui-engineer is an agent published in the GitHub repository feiskyer/claude-code-settings (1,662 stars, last pushed 25d ago), licensed MIT. It adds 59 tokens to every session and 462 once invoked, about $0.0002 per session on Opus 5.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.