UX RULER

UX RULER is an open source UX process for humans and agents. It turns a mission or product idea into a conversational discovery flow: simple questions, focused research, real usage signals when available, clear findings, product decisions, metrics, UX evaluation, and compact repo files.

The installable skill lives in uxruler/.

What It Helps With

• Start a new digital product from mission and market context before jumping into screens.
• Help define the mission in empty repos or blank project starts instead of only asking for context.
• Ask for the missing context in plain language before generating a product map.
• Research and verify market size, audience reachability, alternatives, and user-need assumptions when sources are available.
• Inspect repo-connected usage data, analytics, logs, issues, feedback, and support signals available to the agent before asking the user for missing evidence.
• Present what it learned and what to do next before creating files.
• After changing product files, explain what changed, what decision it supports, what is now measurable, what is still missing, and 2 to 3 concrete next options.
• Create a compact ROADMAP.md as soon as a mission or product direction is decided, so the next moves stay visible.
• Audit an existing product or feature against real users, needs, infrastructure, rollout, and measurable value.
• Create compact agent-readable product files inside a repository.
• Keep UX decisions connected to evidence, metrics, and feedback loops.
• Evaluate product quality through four UX dimensions: usefulness, ergonomics, attractiveness, and identity.

Process

UX RULER uses this sequence:

conversation -> mission -> audience/market -> user -> need -> research -> infrastructure -> product -> value -> evaluation

Decision and measurement are cross-cutting. At every stage, the skill asks plain questions:

• What do we assume?
• What usage data or evidence do we have?
• What are we trying to decide?
• How will we know we were right?

Product Context In This Repo

This repository also uses UX RULER on itself. Start with:

• AGENTS.md for agent instructions and update expectations.
• PRODUCT.md for the compact product thesis, audience, user need, value, assumptions, risks, metrics, and UX test.
• ROADMAP.md for the compact now/next/later sequence once the product direction is decided.

The full artifact blueprint lives in uxruler/references/repo-artifact-blueprint.md, but this repo intentionally keeps product memory in PRODUCT.md and next-move sequencing in ROADMAP.md until a specific decision needs more structure.

Install In Codex

Use Codex's skill installer with the public skill folder:

Use $skill-installer to install this skill:
https://github.com/making-mike/uxruler/tree/main/uxruler

Then restart Codex to pick up new skills.

After installation, start with:

Use $uxruler as an open source UX process for humans and agents. Use simple language. Ask me only for missing context first, then inspect any real usage or repo-connected data available to the agent, research and verify the market, audience, alternatives, and user need, and present clear findings, recommendations, metrics, and any compact repo file. Once we decide the mission or product direction, create or update compact PRODUCT.md and ROADMAP.md. If you change product files, explain what changed, what decision it supports, what is now measurable, what is still missing, and 2 to 3 concrete next options.

For an empty repo or blank project start, use:

Use $uxruler on this empty repo. Use simple language. Help me define the project mission first: inspect what little context is available, offer 2 to 3 draft product directions, ask me to choose or refine one, then turn the chosen direction into audience, user need, first metric, compact PRODUCT.md, and compact ROADMAP.md when ready.

Install In Claude Code

Install as a personal Claude Code skill:

REPO="https://github.com/making-mike/uxruler.git"
TMP_DIR="$(mktemp -d)"
git clone --depth 1 "$REPO" "$TMP_DIR/uxruler"
mkdir -p ~/.claude/skills
rm -rf ~/.claude/skills/uxruler
cp -R "$TMP_DIR/uxruler/uxruler" ~/.claude/skills/
rm -rf "$TMP_DIR"

Restart Claude Code after installing.

Install Per Project

For a project-local skill that can be committed with a product repo:

REPO="https://github.com/making-mike/uxruler.git"
TMP_DIR="$(mktemp -d)"
git clone --depth 1 "$REPO" "$TMP_DIR/uxruler"
mkdir -p .claude/skills
rm -rf .claude/skills/uxruler
cp -R "$TMP_DIR/uxruler/uxruler" .claude/skills/
rm -rf "$TMP_DIR"

git add .claude/skills/uxruler

Repository Layout

.
├── uxruler/
│   ├── SKILL.md
│   ├── agents/openai.yaml
│   └── references/
│       ├── artifact-templates.md
│       └── repo-artifact-blueprint.md
├── AGENTS.md
├── PRODUCT.md
├── ROADMAP.md
├── index.html
├── .github/
├── README.md
├── LICENSE
├── CONTRIBUTING.md
├── CODE_OF_CONDUCT.md
├── SUPPORT.md
└── SECURITY.md

Contributing

Contributions are welcome. Start with CONTRIBUTING.md and keep changes focused: improve the skill workflow, clarify templates, fix installation docs, or add examples that make the product workflow easier to use.

License

MIT. See LICENSE.