design-evolve

Detect web or iOS repositories and route design evolution requests.

1|2|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/joi-fairshare/agentic-workflow --skill design-evolve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-evolve
Source: https://github.com/joi-fairshare/agentic-workflow/tree/main/skills/design-evolve
Command: npx skills add https://github.com/joi-fairshare/agentic-workflow --skill design-evolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Removes the guesswork of deciding whether a design update belongs to web or iOS so the right merge logic runs without manual orchestration.

Core Features & Use Cases

  • Platform detection automation: Scans for iOS or web indicators and decides which specialized design-evolve skill to invoke.
  • Fallback prompts: Asks the user to choose when both or neither platform signs are present, ensuring the workflow stays on track.
  • Use case: Feed it a new reference URL or Swift theme, and it routes the request to merge changes into the appropriate design tokens file.

Quick Start

Ask the workflow to run /design-evolve with your new reference so it detects the platform and merges the updates for you.

Frequently Asked Questions about design-evolve

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

FAQPage Schema
How do I automate design token updates for different platforms in an agentic workflow?

Automating design token updates requires platform detection to route design evolution requests. This Skill inspects repository files to determine if a project is web or iOS, then applies the appropriate merge logic to update existing design tokens without manual orchestration.

How does platform detection work when merging new design references into existing tokens?

Platform detection works by scanning project files for web or iOS specific indicators. When you provide a new reference URL or Swift theme, the system inspects the repository to identify the correct ecosystem and applies the matching merge logic for your design tokens.

What happens if my repository contains both web and iOS project files?

When both web and iOS platform indicators are present in a repository, the workflow pauses and prompts you to manually choose the target platform. This fallback mechanism ensures design updates are routed to the correct tokens file when automatic detection is ambiguous.

Can I route design evolution requests for a Swift theme into iOS design tokens?

Yes, you can route Swift themes into iOS design tokens. By feeding the reference into the workflow, it detects the iOS ecosystem indicators in your project and applies the specialized merge logic to update your existing iOS design tokens accordingly.

What is the best way to merge a new reference URL into web design tokens?

The best way to merge a new reference URL into web design tokens is through automated platform detection. The system scans your repository, identifies the web environment, and routes the design evolution request to apply the correct merge logic for your token files.

Why does my design evolution workflow prompt me to choose a platform manually?

Your workflow prompts for manual platform selection because automatic detection found either conflicting indicators for both web and iOS ecosystems or no recognizable platform signs. This fallback ensures the design token merge logic targets the correct environment when detection is ambiguous.