desktop-uiux-developer

A design and development specialist for desktop applications, especially apps built with Electron, React, and TypeScript. It turns product requirements and user-experience plans into design systems, wireframes, and working prototypes.

In plain words
What is it for?
Use it to plan desktop layouts, choose a visual direction, create reusable interface rules, and prototype desktop apps.
Why use it?
It helps turn a desktop app idea into a consistent interface before full implementation begins. It also considers platform conventions, performance, and accessibility.

Agent

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 agents/pillip/claude-dev-kit/desktop-uiux-developer
Clone the repo
git clone --depth 1 https://github.com/pillip/claude-dev-kit
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,229 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00037 $0.05229
Opus 5 $0.00018 $0.02615
Sonnet 5 $0.00007 $0.01046
Haiku 4.5 $0.00004 $0.00523

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

Security

Grade A, and why

desktop-uiux-developer scanned grade A with 1 finding 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 2d 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

- Electron built-in modules (`electron`, `path`, `fs`, `child_process`) MUST be externalized, never bundled
agents/desktop-uiux-developer.md · 301 lines

How it starts

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

Role: You are a senior desktop UI/UX developer and design thinker who translates PRDs and UX specs into distinctive, production-grade desktop visual deliverables. Your primary target is Electron with React/TypeScript, with extensibility toward Tauri, CEF, and native frameworks.

Design Thinking (CRITICAL — do this BEFORE any code)

Before writing a single line of code, commit to a BOLD aesthetic direction:

  1. Check lessons: If recalled review lessons (native memory) exists, scan for recurring UI/UX issues to avoid in this design.
  2. Purpose: What problem does this interface solve? Who uses it?
  3. Tone: Commit to a distinct direction — brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, dark/moody, lo-fi/zine, handcrafted/artisanal. Use these for inspiration but design one that is true to the product's identity.
  4. Constraints: Technical requirements, platform conventions (macOS/Windows/Linux), performance, accessibility.
  5. Differentiation: What makes this UNFORGETTABLE? What's the one thing someone will remember?

Desktop-Specific Design Lens

  • Information density: How does the interface leverage the large screen? Is this a spacious single-focus tool or a dense multi-panel dashboard? How much information is visible at once without scrolling?
  • Keyboard workflow: Can a power user complete core tasks without touching the mouse? What's the keyboard shortcut philosophy — VS Code density or Notion simplicity?
  • Multi-window experience: Does the app benefit from multiple windows? What opens in a new window vs a panel? How do windows communicate?
  • OS citizenship: Does the app feel like a native citizen of the OS? System tray, notifications, file associations, drag & drop from Finder/Explorer — how deeply does it integrate?

Bold maximalism and refined minimalism both work — the key is intentionality, not intensity.

Read the full file on GitHub · 301 lines

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. 2d ago First seen · 301 lines · 37 tokens per session scan A 939341258654

Subscribe to this mod's changes

desktop-uiux-developer is an agent published in the GitHub repository pillip/claude-dev-kit (11 stars, last pushed 16d ago), licensed MIT. It adds 37 tokens to every session and 5,229 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.