designer-upgrade

designer-upgrade is a command for Claude Code from ShaheerKhawaja/ProductionOS. It costs 43 tokens per session (964 once invoked), scanned A, original, MIT.

A multi-step user-interface and user-experience redesign workflow that audits an existing design and produces interactive HTML mockups for review.

In plain words
What is it for?
It is for auditing usability, defining a design system, creating interactive mockups, collecting browser-based annotations, and planning fixes by priority.
Why use it?
It turns design problems and user feedback into a documented redesign process with a prioritized implementation plan.

Command for Claude Code

Written for Claude Code: arguments in frontmatter.

Part of the productionos plugin — 4 skills, 41 commands, 11 agents shipped together

Good fit It is for auditing usability, defining a design system, creating interactive mockups, collecting browser-based annotations, and planning fixes by priority.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/shaheerkhawaja/productionos/designer-upgrade
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/ShaheerKhawaja/ProductionOS

Made for: Claude Code.

Or install productionos, the plugin that ships this one along with the rest of its 4 skills, 41 commands, 11 agents.

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.

agentmods badge for designer-upgrade

README.md
[![agentmods](https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/designer-upgrade/github.svg)](https://agentmods.dev/commands/shaheerkhawaja/productionos/designer-upgrade)
Your own site
<a href="https://agentmods.dev/commands/shaheerkhawaja/productionos/designer-upgrade"><img src="https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/designer-upgrade/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.

agentmods 80×15 button for designer-upgrade

Your own site · 80×15
<a href="https://agentmods.dev/commands/shaheerkhawaja/productionos/designer-upgrade"><img src="https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/designer-upgrade.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 964 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.00964
Opus 5 $0.00022 $0.00482
Sonnet 5 $0.00009 $0.00193
Haiku 4.5 $0.00004 $0.00096

Measured 11d ago against content hash 0418495a9611, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

designer-upgrade 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 11d ago.

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/commands/designer-upgrade.md · 100 lines

How it starts

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

/designer-upgrade — Interactive UI/UX Redesign Pipeline

You are the designer-upgrade orchestrator. You run a 5-phase design transformation pipeline that produces interactive HTML mockups with annotation capabilities.

This is one of ProductionOS's 4 primary commands. It can be invoked standalone or as part of /omni-plan-nth and /auto-swarm-nth.

Step 0: Preamble

Before executing, run the shared ProductionOS preamble (templates/PREAMBLE.md).

Then initialize the designer-upgrade output directory:

mkdir -p .productionos/designer-upgrade/{audit,mockups,self-eval}

Execution

Read agents/designer-upgrade.md and execute its full 5-phase protocol:

  1. Phase 1: Design Audit — Dispatch 5 parallel auditors (ux-auditor, design-system-architect, frontend-designer, comparative-analyzer, performance-profiler)
  2. Phase 2: Design System — Create comprehensive token system + component inventory
  3. Phase 3: HTML Mockups — Generate interactive mockups with annotation overlay
  4. Phase 4: Interactive Review — Launch local server, user annotates in browser
  5. Phase 5: Implementation Plan — Priority-ordered fix plan from audit + user feedback

Self-Eval Integration (mandatory)

After each phase, run templates/SELF-EVAL-PROTOCOL.md:

  • Phase 1 self-eval: Are audit findings evidence-based? Score >= 8.0 to proceed.
  • Phase 2 self-eval: Is the design system complete and consistent? Score >= 8.0 to proceed.
  • Phase 3 self-eval: Are mockups interactive, responsive, and annotatable? Score >= 8.0 to proceed.
  • Phase 5 self-eval: Is the implementation plan specific and prioritized? Score >= 8.0 to declare success.

Quality Loop Integration

Dispatch quality-loop-controller to monitor the entire pipeline:

  • Self-check all agent outputs before deep eval
  • Trigger heal loops for scores < 8.0
  • Track quality progression across phases
  • Extract patterns for cross-session learning

Output

All artifacts written to .productionos/designer-upgrade/:

.productionos/designer-upgrade/
├── audit/
│   ├── agent-1-ux-auditor.md
│   ├── agent-2-design-system.md
│   ├── agent-3-frontend-designer.md
│   ├── agent-4-competitors.md
│   └── agent-5-performance.md
├── AUDIT-SYNTHESIS.md
├── DESIGN-SYSTEM.md
├── tokens.css
├── COMPONENT-INVENTORY.md
├── PATTERN-LIBRARY.md
├── mockups/
│   ├── index.html
│   ├── {view-name}.html (per view)
│   └── annotations.json (user feedback)
├── IMPLEMENTATION-PLAN.md
├── self-eval/
│   └── {timestamp}-{phase}.md
└── CONVERGENCE-LOG.md

Read the full file on GitHub · 100 lines

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.

  1. 11d ago First seen · 100 lines · 43 tokens per session scan A 0418495a9611

Subscribe to this mod's changes

designer-upgrade is a command published in the GitHub repository ShaheerKhawaja/ProductionOS (8 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 964 once invoked, about $0.0002 per session on Opus 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-08-31.