iterative-design-assistant

Track design decisions in a session-local JSON log during iterative revisions.

5|4|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/takusaotome/claude-skills-library --skill iterative-design-assistant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iterative-design-assistant
Source: https://github.com/takusaotome/claude-skills-library/tree/main/skills/iterative-design-assistant
Command: npx skills add https://github.com/takusaotome/claude-skills-library --skill iterative-design-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you consistently apply prior design choices across multiple revision cycles without forcing you to restate the same styling decisions each time.

Core Features & Use Cases

  • Design decision log per document/session: Track what changed, when, and why so later references are grounded in history.
  • Contextual lookup and resolution: Interpret vague follow-ups like “same style as before” (including Japanese phrases like 前回も色で良いんだけど) by finding the most relevant prior decision.
  • Reapplication and traceability: Reapply a previous decision to a new target element while recording provenance for auditability and review.

Quick Start

Initialize a new design session for your deck by running python3 scripts/design_log.py init --document "presentation.pptx" --session-name "Q4 Sales Deck Revisions".

Frequently Asked Questions about iterative-design-assistant

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

FAQPage Schema
How do I keep presentation styling consistent across multiple revision sessions?

You can keep styling consistent across revisions by using a session-local JSON log to record design decisions. This tracks color and typography changes, enabling later follow-up requests to automatically reuse earlier styling choices without restating them.

How does contextual resolution interpret vague follow-ups like same style as before?

Contextual resolution uses category detection and recency scoring to find the most relevant prior decision in the JSON log. This mechanism matches vague phrases like same style as before to the correct historical color or typography entry.

Can I track color tokens and typography changes across multiple document revisions?

Yes, you can track color tokens and typography changes across multiple document revisions. The design decision log records what changed, when, and why, ensuring styling modifications are traceable and available for contextual lookup during later sessions.

Do I need any external dependencies to run the iterative design assistant?

No external dependencies are required to run the design log. It operates entirely using local scripts and references, requiring only Python to initialize the session-local JSON log and manage your design history.

What is the best way to reapply a previous design decision to a new element?

The best way to reapply a previous design decision to a new element is using the apply command. This process records provenance for auditability, ensuring you can trace the new element's styling back to the original historical decision.

When should I generate a history report for my design decisions?

You should generate a history report when you need to audit styling consistency or review the revision timeline. The report aggregates JSON log entries, providing a clear overview of color, typography, and layout changes made during the session.