What is create-ux-design?

A guided process for planning user experience, meaning how people move through and use a product. It helps create UX specifications through visual exploration and decisions with a product stakeholder.

Use it to plan screens, interaction patterns, and product behavior before implementation. It is intended for collaborative UX specification work with user control at each step.

It gives UX planning a structured sequence instead of leaving design decisions scattered across a conversation. Each step keeps its own instructions and records progress in the working document.

How salazarsebas/Cougr configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to salazarsebas/Cougr. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/salazarsebas/Cougr/main/.claude/skills/create-ux-design/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/salazarsebas/Cougr

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/salazarsebas/cougr/create-ux-design/github.svg)](https://agentmods.dev/skills/salazarsebas/cougr/create-ux-design)

Your own site

<a href="https://agentmods.dev/skills/salazarsebas/cougr/create-ux-design"><img src="https://agentmods.dev/badge/skills/salazarsebas/cougr/create-ux-design/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/salazarsebas/cougr/create-ux-design"><img src="https://agentmods.dev/badge/skills/salazarsebas/cougr/create-ux-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 701 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00037	$0.00701
Opus 5.5	$0.00015	$0.00280
Sonnet 5.5	$0.00007	$0.00140
Haiku 4.5	$0.00004	$0.00070

Measured today against content hash b5078f43067c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-ux-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/create-ux-design/SKILL.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create UX Design Workflow

Goal: Create comprehensive UX design specifications through collaborative visual exploration and informed decision-making where you act as a UX facilitator working with a product stakeholder.

Conventions

Bare paths (e.g. steps/step-01-init.md) resolve from the skill root.
{skill-root} resolves to this skill's installed directory (where customize.toml lives).
{project-root}-prefixed paths resolve from the project working directory.
{skill-name} resolves to the skill directory's basename.

WORKFLOW ARCHITECTURE

This uses micro-file architecture for disciplined execution:

Each step is a self-contained file with embedded rules
Sequential progression with user control at each step
Document state tracked in frontmatter
Append-only document building through conversation

On Activation

Step 1: Resolve the Workflow Block

Run: python3 {project-root}/.stellar-build/scripts/resolve_customization.py --skill {skill-root} --key workflow

If the script fails, resolve the workflow block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:

{skill-root}/customize.toml - defaults
{project-root}/.stellar-build/custom/{skill-name}.toml - team overrides
{project-root}/.stellar-build/custom/{skill-name}.user.toml - personal overrides

Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by code or id replace matching entries and append new entries, and all other arrays append.

Step 2: Execute Prepend Steps

Execute each entry in {workflow.activation_steps_prepend} in order before proceeding.

Step 3: Load Persistent Facts

Treat every entry in {workflow.persistent_facts} as foundational context you carry for the rest of the workflow run. Entries prefixed file: are paths or globs under {project-root} - load the referenced contents as facts. All other entries are facts verbatim.

Read the full file on GitHub · 76 lines

Files

What ships with it

17 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

today First seen · 76 lines · 37 tokens per session scan A b5078f43067c

Subscribe to this mod's changes

create-ux-design is a skill published in the GitHub repository salazarsebas/Cougr (53 stars, last pushed 17d ago), licensed MIT. It adds 37 tokens to every session and 701 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-07.

Design and UX blockchain-gaming ecs game-engine on-chain-games soroban

create-ux-design next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
create-ux-designsalazarsebas/Cougr	Skill	53	17d ago	MIT	A	37	Claude Code
frontend-designrylsherdamz-rgb/stellar-forge	Skill	17	5d ago	MIT	A	51	Claude Code
use-widget-assetSummerEngine/summer-engine-agent	Skill	59	1mo ago	MIT	A	99	Claude Code
ui-basicsSummerEngine/summer-engine-agent	Skill	59	1mo ago	MIT	A	88	Claude Code
pixi-vn-uiDRincs-Productions/pixi-vn	Skill	155	yesterday	LGPL-2.1	A	121	Claude Code, Codex
llmginelordbasilaiassistant-sudo/llmgine	Skill	1	1mo ago	MIT	B	78	Claude Code, Codex
design-taste-frontendrylsherdamz-rgb/stellar-forge	Skill	17	5d ago	MIT	A	61	Claude Code

Cougr: Skill for Claude Code