Fixing one component now takes the whole MCP stack
Key Summary
This article shares how Wanted Lab's design system team automated the component modification workflow with Claude Code and MCP to overcome the limits of a small team and improve design system productivity.
Main Points
- Existing problem: Even a simple property change, such as adjusting avatar corner radius, required six steps—checking the current state, research, Figma updates, documentation, Jira ticket creation, and Slack sharing—taking about five days and spending too much time on execution rather than judgment.
- Workflow skill automation (Claude Code + MCP):
- Current-state analysis: Analyze Web, iOS, and Android repositories in parallel through GitHub integration to identify specs and platform inconsistencies
- Market research: Use subagents to research public design systems and extract insights, while designers make the final decisions
- Figma MCP: Automatically handle repetitive work such as layer naming and token application in a working branch
- Documentation updates: Support writing Figma update notes and handoff documents, and propose custom formulas
- Atlassian MCP: Automatically create Jira tickets and platform-specific subtasks
- Slack MCP: Automatically send notification messages with assignee tags
- Effect: The time required to modify a component was significantly reduced from five days to one day, allowing repeated execution work to be delegated while people focused on decision-making and visual review.
