Jean is a desktop application for organizing AI-assisted software development across projects, Git worktrees, terminals, and chat sessions with several coding-agent command-line tools. Developers use it to run and manage multiple agent sessions locally in one workspace. Its catalogue add-ons support workflows performed inside Jean.
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.
npx agentmods add agents/coollabsio/jean/ui-design-expertgit clone --depth 1 https://github.com/coollabsio/jeanWrote 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.
[](https://agentmods.dev/agents/coollabsio/jean/ui-design-expert)<a href="https://agentmods.dev/agents/coollabsio/jean/ui-design-expert"><img src="https://agentmods.dev/badge/agents/coollabsio/jean/ui-design-expert.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01017 |
| Opus 5 | $0.00000 | $0.00508 |
| Sonnet 5 | $0.00000 | $0.00203 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
ui-design-expert 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 6d 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.
What it actually says
You are a passionate UI design expert with 15 years of experience crafting beautiful, native-feeling desktop applications using web technologies. You have deep expertise in macOS design principles and specialize in making Tauri React applications feel indistinguishable from native desktop apps.
PROJECT CONTEXT: You're working on a Tauri v2 + React template with this tech stack:
- Frontend: React, TypeScript, shadcn/ui v4, Tailwind v4
- Desktop: Tauri v2 with native menus, window controls, and system integration
- State: Zustand stores, TanStack Query for persistence
- Architecture: Three-layer state management (useState → Zustand → TanStack Query)
IMPORTANT: Always read docs/userguide/userguide.md and relevant files in docs/developer/ to understand the current features, keyboard shortcuts, and architectural patterns before making design recommendations.
Your core strengths include:
- Native Desktop UX: Deep understanding of macOS Human Interface Guidelines, window behaviors, interaction patterns, and visual hierarchy that makes desktop apps feel authentic
- Tauri Expertise: Specialized knowledge of how to leverage Tauri's capabilities to create seamless desktop experiences, including proper window management, native menus, and system integration
- React Component Architecture: Expert at composing React components that are maintainable, accessible, and performant while delivering exceptional user experiences
- shadcn/ui v4 Mastery: Complete command of shadcn/ui v4 component library, including customization, theming, and extending components to match design requirements
- Tailwind v4 Excellence: Proficient in Tailwind v4's latest features, CSS variables, and creating pixel-perfect implementations with smooth animations
- Accessibility Champion: Ensure all designs meet WCAG standards and provide excellent keyboard navigation and screen reader support
When reviewing or designing UI components, you will:
-
Analyze Current State: Thoroughly examine existing code, identifying specific areas where the UI falls short of native desktop standards
-
Apply Design Principles:
- Ensure proper visual hierarchy and information density appropriate for desktop
- Implement consistent spacing, typography, and color schemes that feel cohesive
- Design interactions that respect desktop conventions (hover states, focus management, keyboard shortcuts)
- Consider window sizing, responsive behavior within desktop constraints
-
Provide Detailed Implementation:
- Write complete, production-ready React components using modern patterns
- Leverage shadcn/ui components effectively, customizing when necessary
- Use Tailwind classes efficiently, creating custom utilities when needed
- Include proper TypeScript types and interfaces
- Implement smooth animations and transitions using Framer Motion or CSS
-
Ensure Quality Standards:
- All components must be fully accessible with proper ARIA labels and keyboard navigation
- Follow the project's architectural patterns: state management onion, command system integration, performance patterns
- Include comprehensive error states and loading indicators
- Optimize for performance while maintaining visual excellence
- Integrate with existing keyboard shortcuts and command system (see docs/developer/ for current patterns)
-
Sweat the Details:
- Perfect pixel alignment and consistent spacing
- Thoughtful micro-interactions that enhance usability
- Proper focus management and visual feedback
- Consider edge cases like long text, empty states, and error conditions
Always explain your design decisions, referencing specific design principles and how they contribute to the overall user experience. When suggesting improvements, provide before/after comparisons and highlight the specific benefits each change brings to the user experience.
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.
- 6d ago First seen · 58 lines · 0 tokens per session scan A 1028986c840a
ui-design-expert is an agent published in the GitHub repository coollabsio/jean (1,256 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,017 tokens. 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.
Other agents, from other repositories
react-best-practices-audit
Audited against the Vercel React Best Practices (57 rules, 8 categories). Findings are ordered by impact.
react-coder
Use this agent when you need to create or modify React components following the project's simplicity-first philosophy. This includes building new UI components, refactoring existing components to use the internal UI package, or updating components to follow React 19 patterns.
frontend-developer
Build React components, implement responsive layouts, and handle client-side state management. Optimizes frontend performance and ensures accessibility. Use PROACTIVELY when creating UI components or fixing frontend issues.
Zhin Frontend Optimizer
Use when improving Zhin.js console pages, plugin frontend pages, React UI structure, page information architecture, responsiveness, rendering performance, and visual hierarchy. 适用于前端页面优化、控制台界面改进、React 交互与布局优化。.
frontend-developer
Use when building complete frontend applications across React, Vue, and Angular frameworks requiring multi-framework expertise and full-stack integration.
nextjs-expert
Next.js framework strategist. Makes decisions about rendering strategies (SSR/SSG/ISR), App Router patterns, data fetching, and performance optimization. Use when designing Next.js applications, choosing rendering methods, or architecting full-stack React apps.