skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
filipgutica/filip-stack52 installs

interface-design

Design, build, review, or check user interfaces and flows, covering hierarchy, interaction, states, interface copy, and accessibility. Uses UX laws, public standards, and the design system. Use when shaping or reshaping a UI or UX direction, critiquing a screen or flow, or checking a running UI before it ships.

How do I install this agent skill?

npx skills add https://github.com/filipgutica/filip-stack --skill interface-design
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill provides a framework for designing and auditing user interfaces based on UX laws and accessibility standards. It includes Node.js scripts to automate UI checks using Playwright. No malicious code or exfiltration patterns were detected.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

Interface Design

Judge every choice by whether the primary user completes their task: they find what they need, act, recover from errors, and can tell it worked. The look comes from the owning design system: the repository's own, else the design-system plugin's design language when that plugin is installed. Use its tokens and components. With neither, use no house style and say once that the design-system plugin is missing. This skill owns hierarchy, interaction, states, interface copy, and accessibility.

Ground the work

  1. Name the primary user, their task, the context, and the constraints. State a bounded assumption where evidence is missing.
  2. Find the owning design system and read it before you design or judge the look. Keep its palette, type, and layout concepts; a new brief does not earn a new visual identity.
  3. Cover the whole path: loading, empty, error, and success states; keyboard and touch; 320px for reflow, 375px, and desktop widths; light and dark themes where supported; reduced motion.

Routes

  • Design or build. Read references/laws.md and references/craft.md. Pick only the laws and craft rules that change this design.
  • Review. Read references/standards.md and answer each question that applies to the screens in scope. Read laws.md when a finding needs a law to explain it.
  • Check. Run the repository's own accessibility, lint, and visual checks on the running UI. Then run this skill's scripts as references/checks.md describes, at the widths and themes above. Name each check that could not run; an unrun check is not a pass.

Resolve conflicts

In this order: user safety and accessibility; the user's intent and evidence; the owning design system and domain conventions; then laws and craft rules. When two rules pull apart, name the tradeoff.

Guardrails

  • A law or standard guides a decision; it does not prove that a design works. Do not invent user research.
  • No dark patterns: fake urgency, forced progress, concealed choices, or confirmshaming.
  • Color is never the only signal. Keep contrast, visible focus, target size, reduced motion, and assistive-technology semantics at or above the thresholds in standards.md.
  • Simpler must still keep the controls, information, consent, and recovery paths people need.
  • Taste beyond the owning design system is a judgment call. Report it separately from findings that a rule or standard supports.

Output

  • Design or build: the hierarchy and flow, the few laws and craft rules that shaped them, the edge states, and the riskiest assumption to test. After building, review your own screenshots at both widths and themes before you report.
  • Review: findings ranked by user impact. Each names the element or region (quoted text, selector, or screenshot area), the question or rule it fails, the change to make, and how to verify the change helped. Do not produce an unranked checklist.
  • Check: each check's command, result, and the widths and themes it covered, then what remains unchecked.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/filipgutica/filip-stack/interface-design">View interface-design on skillZs</a>