Skip to content
TrustedSkillsbeta
Back to all skills

Ui Ux Guidelines

Checked
jgamaraalv·vlatest·frontend·MIT

Helps with UI components, UX design, guidelines as part of agent workflows workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add jgamaraalv/ts-dev-kit --skill ui-ux-guidelines -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jgamaraalv

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned jgamaraalv/ts-dev-kit at d4a6870312.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
d4a6870312
Manifest
skills/ui-ux-guidelines/SKILL.md
Scanned
5 files, 412 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides access to established UI/UX guidelines. It can be used to ensure designs adhere to best practices and accessibility standards. The skill aims to improve user experience by offering structured recommendations for interface design elements.

When to use it

  • Generating initial design concepts for a new application or feature.
  • Reviewing existing designs to identify potential usability issues.
  • Ensuring compliance with accessibility guidelines (e.g., WCAG).
  • Creating consistent user interfaces across multiple platforms.
  • Troubleshooting user feedback related to interface confusion or difficulty.

Key capabilities

  • Access to UI/UX best practices.
  • Guidance on design principles and patterns.
  • Accessibility recommendations.
  • Interface element guidelines.

Example prompts

  • "What are the recommended color contrast ratios for accessibility?"
  • "Give me some examples of effective navigation patterns."
  • "How should I structure a form to maximize usability?"
  • “Provide UI/UX guidelines for designing buttons.”

Tips & gotchas

The skill's effectiveness depends on providing clear context about the design problem. Vague prompts may yield generic responses; be specific about the platform, target audience, and desired outcome.