v0.9.0What's new
evondevKit

evondevKit · UI skills for Claude Code, Cursor, Codex

See the wireframe first, build the UI once you like it

Lately every screen I asked AI to build came out looking the same. evondevKit is the set of skills I wrote so the AI works like a designer: it reads your codebase, shows 2–3 wireframes with real copy for you to pick, builds the one you like, then measures it at 5 screen widths.

Install evondevKitHow to use it

The same screen before and after the skill cleans it up, then switching between a few built-in looks.

DashboardLive
Phone appBeta

Runs on

  • Claude Code
  • Cursor
  • Codex
  • OpenCode
  • Antigravity
  • ZCode
  • npx
  • bunx

01 / What's in the kit

Dashboards are live, phone apps are in beta, landing pages are in progress

People often ask if it works for the web: yes, dashboards and web apps are what it does best. Install once and you get the whole kit; when a skill is ready, an update brings it in.

Live

Dashboards, web apps

/evon:ui-ux

Comes with 10 dashboard looks to pick from. It builds with whatever your project already uses.

  • dashboard
  • admin
  • table
  • form
  • settings
  • modal
Beta

Phone apps

/evon:ui-ux + “phone app”

An HTML prototype inside a phone frame, every screen clickable, with 9 looks. No React Native or Flutter code yet.

sample prompt

/evon:ui-ux Build a coffee ordering phone app: menu, cart, checkout

In progress

Landing pages

/evon:landing

I'm still building it, not released yet. If you ask evon:ui-ux for a landing page today it still works, but it tells you up front it hasn't been taught that.

  • web app → /evon:ui-ux
  • landing → /evon:landing

02 / How to use

Installed it, now what? One full run, start to finish

  1. 01

    Install the skill

    Open Claude Code in your project folder and paste these 2 commands. On Cursor or Codex, the install steps are at the bottom of the page.

    • /plugin marketplace add evondev/evondevKit
    • /plugin install evon@evondevkit
  2. 02

    Type what you need

    Write it like a message to a designer, with or without /evon:ui-ux in front.

    • /evon:ui-ux Build the order list screen
  3. 03

    Approve the brief

    The skill reads your code and sends a brief: who the users are, what they come to this screen for. If it's right, reply “ok”; if not, fix the part that's off.

    Stop 1

  4. 04

    Pick a wireframe

    The skill sends a localhost link. Open it in your browser, flip between A, B and C, then reply something like “A, drop block 3”.

    Stop 2

  5. 05

    Get the build

    The skill builds straight into your code, measures it at 5 screen widths, then tells you what it fixed and what logic you need to wire up (APIs, form submits…).

claude · ~/shop-admin
  1. 02Build the order list screen: order id,
  2. customer, total, status
  3. Audit: Next 16 · Tailwind v4 · shadcn
  4. 03Brief: users are warehouse staff,
  5. the main job is finding late orders.
  6. Approve the brief and I'll draw 2–3 wireframes.
  7. ok
  8. 04A · Table + compact filters (recommended)
  9. B · List + detail panel
  10. localhost:4173/wireframe.html?v=a
  11. A, drop block 3
  12. 05Built app/orders/page.tsx
  13. 5 widths · 0 Broken issues
  14. You wire up: orders API, Export button

The number on the left matches the step next to it.

03 / Most used

The 3 things people ask evon:ui-ux for most

Work like a designer

The skill writes a brief and shows 2–3 wireframes with real copy. It builds only the one you pick.

Review the UI you have

Give it a localhost link and it opens the page, measures from 375 to 1920px, and sends an issue table. It fixes only after you reply “fix 1, 3”.

#IssueLevel
1Secondary text at 3.2 : 1 on cardsBroken
2Nav wraps at 860–1000pxBroken
3Three corner radii on one card typeOff-system

You reply: fix 1, 2

Phone appsBeta

An HTML prototype inside a phone frame, with clickable screens. Still in beta.

9 more jobs, one sentence each

No commands to memorize: say what you want and the skill takes that route.

  • Analyze the productNew

    Not sure how it should be designed? Ask first; the skill sends a report and touches no code.

    /evon:ui-ux Analyze this e-learning product
  • Just build it, no wireframes

    Skip the wireframes to save tokens; at handover the skill says which layout it chose.

    /evon:ui-ux Just build the notification settings screen
  • Design system first

    Lock in color, type, spacing and 7 base components on one page before any screen.

    /evon:ui-ux Build a design system for a clinic app
  • Smaller than a screen

    Add a dropdown, fix a bug, change a color: the skill just does it.

    /evon:ui-ux Add a status filter dropdown to the orders table
  • Review a flowNew

    Walks the steps like a new user and points out where they get lost.

    /evon:ui-ux Review onboarding up to the first course
  • Rebuild, keep the brand

    Keeps your layout and colors, swaps home-made controls for proper components.

    /evon:ui-ux Rebuild this page and keep the brand
  • Redo in the skill's style

    Switches colors to the skill's set; only your logo and main accent stay.

    /evon:ui-ux Rebuild in the skill's style, drop the old one
  • Add dark mode

    A Light / Dark / System toggle that never flashes white on load.

    /evon:ui-ux Add dark mode with a toggle in the header
  • Clean the code, keep the lookBeta

    Compares screenshots before and after so not a pixel shifts. New, not well tested yet.

    /evon:ui-ux Refactor the /settings CSS to Tailwind

04 / Measured

Measured by a script at 5 widths, issues sorted into 3 levels so you know what to fix first

Check144012801024768375
Text contrast ≥ 4.5 : 1
No sideways scroll
Nav stays on one line
Hover is visible

Add --stress and the skill fills in very long names and billion-scale amounts, then measures again to see if the screen breaks.

Broken
Measurably wrong: low contrast, overflow, wrapping, unclickable. The skill fixes these until none are left.
Off-system
Breaks your own project's conventions, like 3 corner radii on one card type.
Taste
Suggestions from the skill's taste, unchecked by default; fixed only if you want.

05 / How I build skills

Every skill in the kit follows these 3 rules

Concrete, numbered rules

No vague “make it look good”. Every rule has its own code, and many came from bugs I hit while testing.

M13 1px borders instead of shadows

R1 No sideways scroll at 375px

I3 One primary button per area

each rule lives in exactly 1 file

Tested before promised

Anything not tested yet is marked in progress or beta here, never “available”. Numbers are what I actually counted.

70 test prompts

30 components · 22 pages

counted Sep 29, 2026

Follows your project

The skill reads your codebase before writing a line. Existing components, tokens and conventions get reused, not replaced.

Audit: Next 16 · Tailwind v4

shadcn · 14 components

→ built with your Button, Table

06 / Install

Install once for the whole kit, update to get new skills

Claude Code
  1. 01

    Add the marketplace, then install the evon plugin.

    • /plugin marketplace add evondev/evondevKit
    • /plugin install evon@evondevkit
  2. 02

    Invoke the skill with this command, or just write a prompt: it turns on when the prompt is about app UI.

    • /evon:ui-ux
  3. 03

    Pull the latest version when a new release is out.

    • /plugin marketplace update evondevkit

All testing ran on Claude Code. Once installed, see how to use it.

07 / FAQ

Questions people ask

Anything else, open an issue on GitHub and I'll answer there.

Does it work for the web?

Yes, web apps are what it's for: dashboards, admin pages, tables, forms, settings, modals. Phone apps are in beta, and landing pages get their own skill, evon:landing, which I'm still building.

I installed it, now how do I use it?

Open your project in Claude Code and type what you need, like “Build the order list screen”. The skill asks you twice (approve the brief, pick a wireframe) and then builds. Every step is in How to use above.

Is it ready for real work?

Dashboards and web apps are live, after 70 test prompts on real projects. Building new phone apps has passed about 13 test prompts, so it stays in beta. I haven't tested Cursor, Codex, OpenCode, Antigravity and ZCode myself; if you hit a bug, open a GitHub issue with a link or screenshot.

What if I don't like the result?

Taste differs, so the skill can't be perfect. Ask the AI to keep changing it, or edit by hand like any code. Talk to it like you'd give a designer feedback: “bolder headings”, “more breathing room”, “drop block 3”.

Is it free?

Yes, open source under MIT. You only spend tokens in the tool you already use.

What if my project already has a design system?

The skill uses your components and tokens. With shadcn, Radix, MUI, Ant or an in-house kit it uses that, and your brand colors stay unless you say “drop the old style”.

Will later screens keep the look of earlier ones?

Yes. The skill writes what's been decided (look, accent color, layout per screen) to DESIGN.md at the project root. The next session reads it before building, and you can edit it by hand.

Do I need Tailwind?

No, it writes CSS the way your project already does, plain HTML included.

Does it do dark mode?

Yes. Adding dark mode to an existing app was tested on 1 real project, all 7 items: theme toggle, tables, app shell, overlays, forms, charts, sign-in screen. By default it still builds light screens; it does dark mode when you ask.

Try it on your own project today

Once installed, type one prompt and you get a result right away.

Install evondevKit