ux-retro

Runs a retrospective on the last design run and proposes edits to the nadav-design skill.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/Nadav011/nadavai-claude --skill ux-retro-nadav011
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-retro
Source: https://github.com/Nadav011/nadavai-claude/tree/main/plugins/nadavai/skills/ux-retro
Command: npx skills add https://github.com/Nadav011/nadavai-claude --skill ux-retro-nadav011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After completing a UI/UX design run, it is hard to know what the design skill missed or how its instructions should improve. This Skill closes the feedback loop by running a structured retrospective on the last run and turning findings into approved edits to the nadav-design skill. ## Core Features & Use Cases - Retro Mode Shortcut: Acts as a direct entry point to the retro mode of the nadav-design skill, always using the same plugin and version. - Step-by-Step Review: Follows the retro section of nadav-design one step at a time, with evidence after every step and a stop on failure. - Approval-Gated Changes: Stops for user approval before applying any edit to the skill, with Hebrew chat throughout. - Use Case: After shipping a screen with the UI loop, type /ux-retro to review what the skill missed and approve concrete improvements to its instructions. ## Quick Start Type /ux-retro to review the last design run and approve improvements to the nadav-design skill.

Frequently Asked Questions about ux-retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a retrospective on my UI design workflow?

Type /ux-retro or ask what the design skill missed. The skill invokes the retro mode of nadav-design, which walks through the last run step by step with evidence and proposes improvements.

How do I improve a Claude Code skill after using it?

Use the retro mode of the skill itself. ux-retro loads nadav-design's retro section, reviews the last run, and suggests concrete edits to the skill's instructions, which you approve before anything is applied.

Does ux-retro change the skill without my approval?

No. The skill explicitly stops for approval before applying any edit. It presents findings and proposed changes first, and nothing is modified until you confirm.

What happens if the nadav-design skill cannot be loaded?

The skill falls back to reading the nadav-design SKILL.md file directly from the plugin directory and follows its Hard rules and retro section verbatim. It never looks for the master skill anywhere else.

When should I use ux-retro versus editing the skill manually?

Use ux-retro when you want a structured, evidence-based review of an actual run rather than ad-hoc edits. Manual editing suits cases where you already know exactly what to change without reviewing run evidence.