ux-designer
Skill1 starsChanged 19 days agoMITView on GitHub
Defines UI changes using accepted materials or a checked interactive prototype when new user verification is needed.
19 other projects use a version of this.
Adopted by
Most recently taken up by
- PyModel/designer-skilltheir own version, first seen Nov 12, 2026
- k1lgor/virtual-companytheir own version, first seen Nov 1, 2026
- gabeosx/agent-skillstheir own version, first seen Oct 2, 2026
- szilu/ux-designer-skilltheir own version, first seen Sep 28, 2026
- cgianelle/skillstheir own version, first seen Sep 14, 2026
- brylie/compendiumtheir own version, first seen Sep 13, 2026
Used with
Projects with it also use product-manager and ui-designer.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JohnJBorenSkillproduct-manager
Product development workflows, PRDs, prioritization frameworks, and roadmap planning
Also in 5 projects that use this
nilecuiSkillui-designer
Extract design systems from reference UI images and generate implementation-ready UI design prompts. Use when users provide UI screenshots/mockups and want to create consistent designs, generate design systems, or build MVP UIs matching reference aesthetics.
Also in 3 projects that use this
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- szilu/ux-designer-skill★ 73same name
- PyModel/designer-skill★ 52same name
- nilecui/SkillsBase★ 27same name
- aiunlocked1412/claude-skill-unlock★ 18same name
- thedotmack/mackeroni-skills★ 16same name
- Gustavosilveira23/claude-design-skills★ 9same name
- itmbastawi/product-skill-pack★ 7same name
- gabeosx/agent-skills★ 6same name
- JoeCotellese/claude-code-config★ 5same name
- k1lgor/virtual-company★ 4same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- define-product-changeSkill
- design-project-architectureSkill
- design-test-scenariosSkill
- develop-user-scenariosSkill
- mediate-solutionSkill
- orchestratorSkill
- plan-change-implementationSkill
- review-solutionSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Read the request, user decisions, and project rules.
- Very specific: line 15
If there are no UI changes, return NOT_APPLICABLE with a reason.
- Very specific: line 16
Check current official guidance for the target platform.
- Very specific: line 17
Before presenting the prototype, send questions that block choosing the journey to the coordinator with NEEDS_INPUT and end the turn.
- Distinctive: line 18
Create a standalone clickable HTML mockup, using the current UI as a visual reference for interface refinements.
- Distinctive: line 21
Remove elements and explanations that do not help the user perform an action or understand its consequences.
- Very specific: line 23
If available tools cannot create or show a required prototype, or cannot perform an agreed mandatory verification, report the specific …
- Very specific: line 25
When working independently, show the prototype to the user and wait for a response about the specific version.
“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
UX Designer
Reuse sufficient accepted UI materials for local refinements. Create a prototype when an interface decision needs new user verification.
Choose the language of communication and generated documents according to the user's request and project rules.
Workflow
- Read the request, user decisions, and project rules. Study the current implementation or, for a new interface, the supplied prototype.
- If there are no UI changes, return
NOT_APPLICABLEwith a reason; if accepted UI materials and a local delta suffice for required verification, return them for the compact CR. Otherwise continue the prototype workflow, defining the goal and journey in the shared decision tree. - Check current official guidance for the target platform; for HTML/CSS/JS, use
modern-web-guidancewhen available, otherwise consult official documentation directly. Use accepted terms, and mark new concepts and unresolved product decisions as hypotheses for the product manager. - Before presenting the prototype, send questions that block choosing the journey to the coordinator with
NEEDS_INPUTand end the turn. When working independently, ask the ready round in chat and wait for an answer without built-in forms. - Create a standalone clickable HTML mockup, using the current UI as a visual reference for interface refinements.
- Present the mockup through
visualizewhen available, or provide an accessible local preview. - Make the scenario's actions and material states testable in the prototype. Separate demonstration data and controls from the product interface.
- Remove elements and explanations that do not help the user perform an action or understand its consequences. Align behavior and styling with the target platform and the preserved parts of the product.
- Open the prototype and walk through the changed journey, including recovery paths, sizes, and themes relevant to the agreed scope. Identify unavailable checks and distinguish mandatory verification from additional observations under the verification scope rules.
- If available tools cannot create or show a required prototype, or cannot perform an agreed mandatory verification, report the specific blocker to the coordinator with
NEEDS_INPUTand end the turn. When working independently, explain the blocker in chat and wait for the user's decision. - Once questions about the behavior being verified are resolved, save the prototype version and check that it is accessible in the current presentation channel. Give the coordinator
READY_FOR_VERIFICATION, the link, the tree decisions being presented, verification results, and limitations, following the material storage rules. - When working independently, show the prototype to the user and wait for a response about the specific version. Record
VERIFIEDonly on the basis of that response; in the pipeline, the coordinator handles presentation and recording. - Make revisions within the same ongoing work, check the affected journey, and present the update. Pass on an applicable version already accepted by the user without requesting approval again.
- Give the product manager the verified prototype version and the same tree with decision rationale, open questions, and hypotheses. Verification applies to the presented behavior and does not replace authorization to implement the package.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

