b2c-ios-design-system-explore

Analyze iOS DesignSystem modules to inventory components, tokens, and public APIs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/herren-official/product-agents --skill b2c-ios-design-system-explore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: b2c-ios-design-system-explore
Source: https://github.com/herren-official/product-agents/tree/main/skills/b2c-iOS/design-system-explore
Command: npx skills add https://github.com/herren-official/product-agents --skill b2c-ios-design-system-explore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The DesignSystem module is large and fragmented; teams need a quick way to discover components, Foundation tokens, and extensions and understand public APIs for integration.

Core Features & Use Cases

  • Inventory components, tokens, and public APIs within a DesignSystem module.
  • Analyze token mappings and public API surfaces for consistency and reuse.
  • Use Case: A designer needs a quick inventory of all components and tokens before a new feature integration.

Quick Start

Analyze the DesignSystem module to map components, tokens, and APIs.

Frequently Asked Questions about b2c-ios-design-system-explore

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

FAQPage Schema
How do I inventory iOS design system components and tokens?

You can inventory iOS design system components and tokens by analyzing the DesignSystem module to discover components, Foundation tokens, and extensions, then cross-validating findings against DESIGN_SYSTEM.md for a structured inventory.

What is token mapping in an iOS design system?

Token mapping in an iOS design system links Foundation tokens to component public APIs and usage patterns. It captures these mappings to analyze consistency and reuse across the module for engineering and design teams.

How do I map public API surfaces in a design system module?

Mapping public API surfaces involves reading source code and documentation references within the design system module to capture public APIs, token mappings, and usage patterns, producing a structured inventory for downstream tooling integration.

Can I use this to prepare a component inventory before a new feature integration?

Yes, you can generate a component inventory before a new feature integration. It analyzes the DesignSystem module to discover components, Foundation tokens, and extensions, providing a quick reference for designers and engineers.

Does the analysis require a DESIGN_SYSTEM.md file to work?

The analysis cross-validates discovered components, tokens, and public APIs against DESIGN_SYSTEM.md. While it reads source and documentation references, this cross-validation ensures the structured inventory output remains accurate for downstream tooling.

What is the best way to explore design system extensions across iOS modules?

The best way to explore design system extensions across iOS modules is to analyze the Components, Foundation, and Extensions scopes, capturing public APIs and usage patterns to produce a structured inventory for engineering teams.