design-analyze

Detect web or iOS targets by scanning Package.swift, Xcode projects, and package.json.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures the right design token extractor runs by automatically identifying whether the project is web or iOS, eliminating the guesswork when onboarding new references.

Core Features & Use Cases

  • Platform detection: Searches for Package.swift, Xcode projects, workspaces, and package.json dependencies to classify the repository.
  • Dispatcher logic: Delegates execution to /design-analyze-web or /design-analyze-ios with the original arguments based on detected platforms.
  • Guided prompts: Asks the user which platform to target when the files indicate both or neither, keeping the workflow precise.
  • Use Case: Feed a list of URLs or asset paths, let the skill determine the platform, and have the correct extractor produce design-tokens.json.

Quick Start

Ask the agent to run /design-analyze https://example.com to detect the platform and extract tokens.

Frequently Asked Questions about design-analyze

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

FAQPage Schema
How do I automatically detect whether a project targets web or iOS for design token extraction?

Automatically detect web or iOS platforms for design token extraction by scanning the workspace for Package.swift, Xcode projects, workspaces, and package.json dependencies. The skill classifies the repository and delegates execution to the correct platform-specific extractor.

What happens during design token extraction if a repository contains both web and iOS project files?

When both web and iOS files are detected during design token extraction, the skill prompts the user to choose which platform to target. This guided interaction ensures the correct downstream extractor runs with the original arguments.

How do I extract design tokens from a list of URLs and Swift asset paths without knowing the target platform?

Extract design tokens from URLs and Swift assets by feeding the references to the dispatcher. It scans for Package.swift, Xcode projects, and package.json files to determine the platform, then delegates to the appropriate extractor to produce design-tokens.json.

Do I need to manually specify my environment before extracting design tokens from Xcode workspaces?

No manual environment specification is needed before extracting design tokens from Xcode workspaces. The dispatcher automatically searches for Package.swift, xcworkspace, and package.json dependencies to identify the platform and route the task.

Why does my design token extraction workflow fail to choose the correct platform-specific extractor?

Design token extraction workflows fail to choose the correct extractor when files indicate neither web nor iOS targets. The dispatcher requires identifiable Package.swift, Xcode project, or package.json files, otherwise it prompts the user for platform clarification.

Can I use design-analyze to process both reference URLs and Xcode assets in a single workflow?

Yes, you can process both reference URLs and Xcode assets in a single design token workflow. The skill analyzes the mixed inputs, detects the underlying platform from project files, and delegates to the matching web or iOS extractor.