Skip to content
TrustedSkillsbeta
Back to all skills

Ux Specification

Checked
abhsin·vlatest·writing·MIT

Generates detailed UX specifications from user stories, wireframes, or design concepts for clear development guidance.

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 abhsin/designskills --skill ux-specification -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

abhsin

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 abhsin/designskills at 8bcf065b9d.

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

Commit
8bcf065b9d
Manifest
Skill/ux-specification/SKILL.md
Scanned
3 files, 1,036 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 transforms product requirements into detailed UX specifications, providing clear guidance for coding agents to implement a product's look and behavior. It takes user stories, wireframes (optional), design preferences, and existing PRDs as input and generates comprehensive documentation including user flows, screen layouts, interactions, and error handling. The output is formatted in markdown and automatically saved as design/06-ux-spec.md.

When to use it

  • When you have a Product Requirements Document (PRD) but need to translate those requirements into actionable design specifications for developers.
  • To ensure consistent understanding of user flows and screen designs across product, design, and development teams.
  • For projects where clear documentation is crucial for efficient coding agent implementation.
  • When you have existing sketches or wireframes that need to be formalized into detailed UX specifications.

Key capabilities

  • PRD Ingestion: Extracts user stories, features, acceptance criteria, target user characteristics and technical constraints from a PRD.
  • User Flow Mapping: Defines user flows by identifying start points, happy paths, decision points, potential errors, and end states.
  • Screen Definition: Specifies the purpose, components, data displayed, actions available, and states for each screen.
  • Interaction Specification: Details interaction triggers, feedback mechanisms, on-screen changes, and timing.
  • Gap Clarification: Asks targeted questions to resolve ambiguities in requirements or design choices.
  • Automated Output: Saves the generated UX specification as a markdown file (design/06-ux-spec.md).

Example prompts

  • "Generate UX specifications for this PRD: [paste PRD content here]"
  • "Create user flows and screen definitions based on these wireframes: [provide wireframe descriptions or links]"
  • "Develop a detailed UX specification, considering the following design preferences: [list preferences]"

Tips & gotchas

  • The skill requires a Product Requirements Document (PRD) as input. Providing existing sketches or wireframes is optional but can improve the quality of the output.
  • The skill focuses on generating specifications, not complete designs. It assumes some design direction already exists.
  • Be prepared for clarifying questions from the skill to resolve ambiguities in requirements.