ios-components

Create reusable SwiftUI components from design tokens and templates.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/nguyennamkkb/ios-spec-driven --skill ios-components
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-components
Source: https://github.com/nguyennamkkb/ios-spec-driven/tree/main/src/ios_spec_driven_installer/templates/.claude/skills/ios-components
Command: npx skills add https://github.com/nguyennamkkb/ios-spec-driven --skill ios-components

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers avoid duplicating UI work by enabling rapid creation of reusable SwiftUI components across screens and features.

Core Features & Use Cases

  • Reusable SwiftUI components: buttons, cards, inputs, modals, and more, designed for consistency.
  • Design-to-code workflow: translates design tokens and styles into composable SwiftUI views.
  • Quick start templates and usage patterns for common UI patterns.

Quick Start

Use the ios-components skill to locate, reuse, and assemble SwiftUI components from existing design assets and code templates.

Frequently Asked Questions about ios-components

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

FAQPage Schema
How do I create reusable SwiftUI UI components fast across multiple screens?

To create reusable SwiftUI UI components fast, use local templates, style tokens, and component catalogs to assemble buttons, cards, inputs, and modals for consistent design-to-code reuse workflows.

What is the best way to translate design tokens into composable SwiftUI views?

Translating design tokens into composable SwiftUI views involves applying a structured approach with local templates and style tokens, converting design assets into reusable code components.

Can I use this approach to build iOS component catalogs for mobile development?

Yes, you can build iOS component catalogs for mobile development by enforcing a structured approach using style tokens and templates to produce consistent UI elements across features.

How do I stop duplicating UI work when building iOS app features?

Stop duplicating UI work by enabling rapid creation of reusable SwiftUI components across screens, using quick start templates and usage patterns for common UI elements.

Does this component reuse workflow require external dependencies?

No, this component reuse workflow requires no external dependencies, relying entirely on local templates and style tokens within your iOS project to generate SwiftUI views.