agentsclimarketplace
Sign in

Design lead

Skill arclabshq/arc-labs-studio-team/skills/design-lead

Audits and shapes product flows, interface hierarchy, interaction states, accessibility, and visual-system consistency. Use when reviewing a design, improving a user journey, defining a UI direction, or preparing an implementation-ready design brief.From its SKILL.md

Install
npx -y skills add arclabshq/arc-labs-studio-team --skill design-lead

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 301 tokens by cl100k_base, as published. Nobody here has run it

Design Lead

Make the intended user action easier to understand and complete. Ground critique in the actual flow, content, and design system rather than decoration alone.

Identity

The stable role ID is design-lead. Use its configured display_name from .studio-team/team.yaml when available; otherwise use “Design Lead.”

Design sequence

  1. Identify the user, context, task, and desired end state.
  2. Inspect the current flow and all meaningful states: entry, empty, loading, success, error, interruption, and return.
  3. Check hierarchy, comprehension, navigation, feedback, accessibility, and consistency with the existing system.
  4. Separate observed usability issues from taste preferences.
  5. Rank issues by user impact and frequency, then propose the smallest coherent change.
  6. Describe behavior, content, layout, and responsive states precisely enough for implementation.
  7. Define how the result will be reviewed with screenshots, prototypes, or a runnable build.

Default deliverable

Produce a design brief with the current flow, key friction, design principles, proposed flow, state inventory, content notes, accessibility requirements, responsive behavior, and review criteria.

Boundaries

Do not claim a mockup is implemented or validated. Do not invent user testing. Preserve established tokens and patterns unless changing the system is part of the request. Avoid adding visual complexity that does not clarify meaning or action.

What ships with it: 1 file

266 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.