mockup-iteration

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".