mockup-iteration

Generate versioned mockup artifacts and decision logs for UI iterations.

1|1|Updated Oct 8, 2025
One-click install
npx skills add https://github.com/gvarela/prompts --skill mockup-iteration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mockup-iteration
Source: https://github.com/gvarela/prompts/tree/main/claude-code/skills/mockup-iteration
Command: npx skills add https://github.com/gvarela/prompts --skill mockup-iteration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UI design projects often lose track of feedback and changes across iterations. This Skill enforces a structured process to capture keeps, removes, changes, and versioned mockups, preserving an auditable decision log.

Core Features & Use Cases

  • Versioned mockups: Maintain mockups and artifacts per iteration (mockup.md, mockup.html) in a traceable history.
  • Decision logging: Record KEEP/REMOVE/CHANGE decisions in mockup-log.md for each version.
  • Visual validation readiness: Prepare artifacts and notes to support Playwright-based visual checks and handoffs.
  • Use Case: During design critiques, collect feedback, create v00N+1 with all changes, and clearly communicate decisions to stakeholders.

Quick Start

Start a new mockup iteration with a directory, capture feedback as KEEP/REMOVE/CHANGE, then prompt to create the next version. To view the current mockup, say "show mockup". To review the log, say "show log".

Frequently Asked Questions about mockup-iteration

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

FAQPage Schema
How do I track UI mockup changes and feedback across multiple iterations?

UI mockup iteration tracking works by enforcing structured feedback capture and generating versioned artifacts like mockup.md and mockup.html. It maintains a traceable mockup-log.md decision log to keep design changes coherent across reviews.

What is the best way to keep a decision log for design reviews and handoffs?

Keeping a decision log for design reviews involves recording KEEP, REMOVE, and CHANGE actions for each version in a dedicated mockup-log.md file. This creates an auditable history that clearly communicates design rationale to stakeholders during handoffs.

How do I start a new versioned mockup iteration session?

To start a new mockup iteration, create a directory for the version, capture incoming feedback as KEEP, REMOVE, or CHANGE, and then prompt to create the next version. This generates synced mockup.md, mockup.html, and decisions artifacts.

Does this UI mockup iteration workflow support Playwright visual validation?

Yes, this UI mockup iteration workflow supports Playwright visual validation by preparing versioned artifacts and notes. These generated files are synced specifically to facilitate Playwright-based visual checks and seamless design handoffs.

Can I use this approach to manage design feedback for multiple stakeholders?

You can use this structured feedback approach to manage design critiques from multiple stakeholders by consolidating all input into KEEP, REMOVE, and CHANGE decisions. It ensures every version update and design choice is coherent and auditable.