agentleFS
CrazyViperCrazyViper/agents_driven_sdlc/skills/ux-designer/SKILL.md

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

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.
  • JohnJBorenSkill

    product-manager

    Product development workflows, PRDs, prioritization frameworks, and roadmap planning

    Also in 5 projects that use this

  • nilecuiSkill

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

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
  1. Distinctive:

    Read the request, user decisions, and project rules.

    line 14
  2. Very specific:

    If there are no UI changes, return NOT_APPLICABLE with a reason.

    line 15
  3. Very specific:

    Check current official guidance for the target platform.

    line 16
  4. Very specific:

    Before presenting the prototype, send questions that block choosing the journey to the coordinator with NEEDS_INPUT and end the turn.

    line 17
  5. Distinctive:

    Create a standalone clickable HTML mockup, using the current UI as a visual reference for interface refinements.

    line 18
  6. Distinctive:

    Remove elements and explanations that do not help the user perform an action or understand its consequences.

    line 21
  7. Very specific:

    If available tools cannot create or show a required prototype, or cannot perform an agreed mandatory verification, report the specific …

    line 23
  8. Very specific:

    When working independently, show the prototype to the user and wait for a response about the specific version.

    line 25

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Read the request, user decisions, and project rules. Study the current implementation or, for a new interface, the supplied prototype.
  2. If there are no UI changes, return NOT_APPLICABLE with 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.
  3. Check current official guidance for the target platform; for HTML/CSS/JS, use modern-web-guidance when available, otherwise consult official documentation directly. Use accepted terms, and mark new concepts and unresolved product decisions as hypotheses for the product manager.
  4. Before presenting the prototype, send questions that block choosing the journey to the coordinator with NEEDS_INPUT and end the turn. When working independently, ask the ready round in chat and wait for an answer without built-in forms.
  5. Create a standalone clickable HTML mockup, using the current UI as a visual reference for interface refinements.
  6. Present the mockup through visualize when available, or provide an accessible local preview.
  7. Make the scenario's actions and material states testable in the prototype. Separate demonstration data and controls from the product interface.
  8. 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.
  9. 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.
  10. 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_INPUT and end the turn. When working independently, explain the blocker in chat and wait for the user's decision.
  11. 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.
  12. When working independently, show the prototype to the user and wait for a response about the specific version. Record VERIFIED only on the basis of that response; in the pipeline, the coordinator handles presentation and recording.
  13. 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.
  14. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.