creating-component

creating-component is a skill for Claude Code from SwiftfulThinking/SwiftfulStarterProject. It costs 57 tokens per session (794 once invoked), scanned A, original, MIT.

A procedure for creating reusable SwiftUI interface components. It keeps these components focused on displaying injected data and actions rather than containing business logic.

In plain words
What is it for?
Use it to create reusable views such as cards, cells, modals, image views, or other shared UI pieces in the appropriate Components folder.
Why use it?
It provides a consistent location, naming pattern, preview setup, and separation between shared interface pieces and screen-specific code.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/swiftfulthinking/swiftfulstarterproject/creating-component
Any agent
npx skills add SwiftfulThinking/SwiftfulStarterProject --skill creating-component
Clone the repo
git clone --depth 1 https://github.com/SwiftfulThinking/SwiftfulStarterProject

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for creating-component

README.md
[![agentmods](https://agentmods.dev/badge/skills/swiftfulthinking/swiftfulstarterproject/creating-component.svg)](https://agentmods.dev/skills/swiftfulthinking/swiftfulstarterproject/creating-component)
Your own site
<a href="https://agentmods.dev/skills/swiftfulthinking/swiftfulstarterproject/creating-component"><img src="https://agentmods.dev/badge/skills/swiftfulthinking/swiftfulstarterproject/creating-component.svg" alt="Measured on agentmods" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 794 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00057 $0.00794
Opus 5 $0.00028 $0.00397
Sonnet 5 $0.00011 $0.00159
Haiku 4.5 $0.00006 $0.00079

Measured yesterday against content hash e7e2dcd31592, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

creating-component scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/creating-component/SKILL.md · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Creating Component

Scaffold a reusable SwiftUI component — pure UI with injected data and actions.

Steps

  1. Get the component name from the user (PascalCase, must end in View — e.g., "ProfileCardView", "LoadingSpinnerView", "CustomModalView")
  2. Determine the subfolder (see below)
  3. Create a single file: {ComponentName}View.swift
  4. Add multiple #Preview blocks for different states

Folder Location

Screen-specific components — used by only one screen — go inside that screen's folder:

Core/{ScreenName}/Components/{ScreenName}HeaderView.swift

Generic/reusable components — used across multiple screens — go in the shared Components folder:

Components/Views/StretchyHeaderView.swift
Components/Modals/CustomModalView.swift
Components/Images/ImageLoaderView.swift
Components/ViewModifiers/ButtonViewModifiers.swift
Subfolder Use For
Views/ General reusable views (DEFAULT)
Modals/ Modal/popup overlay components
Images/ Image-related components
ViewModifiers/ ViewModifier structs

If unclear, ask the user whether the component is screen-specific or reusable.

Component Rules

  • No business logic — pure UI rendering only
  • No @State for data — only @State private var for local UI animation state
  • No @Observable objects, no Presenters — components are not VIPER modules
  • All data injected via var properties with default values — not let, so the implicit init has defaults
  • Make as much as possible optional — unwrap in the view body
  • All actions are closures with defaults — e.g., var onTap: () -> Void = { }
  • import SwiftfulUI when using .asButton(), .tappableBackground(), .ifSatisfiesCondition(), or other SwiftfulUI extensions
  • Follow the swiftui-patterns rules for layout, buttons, images, text

Template

import SwiftUI
import SwiftfulUI

struct {ComponentName}View: View {

    var title: String? = nil
    var subtitle: String? = nil
    var onTap: () -> Void = { }

    var body: some View {
        VStack(spacing: 8) {
            if let title {
                Text(title)
                    .font(.headline)
            }

            if let subtitle {
                Text(subtitle)
                    .font(.subheadline)
                    .foregroundStyle(.secondary)
            }
        }
        .asButton(.press) {
            onTap()
        }
    }
}

#Preview("Full Data") {
    {ComponentName}View(
        title: "Title",
        subtitle: "Subtitle",
        onTap: { }
    )
}

#Preview("Title Only") {
    {ComponentName}View(
        title: "Title"
    )
}

#Preview("Empty") {
    {ComponentName}View()
}

Read the full file on GitHub · 109 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 109 lines · 57 tokens per session scan A e7e2dcd31592

Subscribe to this mod's changes

creating-component is a skill published in the GitHub repository SwiftfulThinking/SwiftfulStarterProject (74 stars, last pushed 5mo ago), licensed MIT. It adds 57 tokens to every session and 794 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Related

Other skills, from other repositories

display-glasses-with-jetpack-compose-glimmer

Provides guidelines for developing projected Android XR apps for display glasses using the Jetpack Compose Glimmer UI toolkit. This skill covers foundational Glimmer design principles, workflows for implementing Jetpack Compose Glimmer, and interaction models for the glasses form factor. Use this skill to build an…

android/skills · 91 tokens

expo-design-system

Framework (OSS). Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant/size/state prop conventions, and rules for when to extract a repeated view into a shared component. Use when…

expo/skills · 181 tokens

flutter-build-responsive-layout

Use LayoutBuilder, MediaQuery, or Expanded/Flexible to create a layout that adapts to different screen sizes. Use when you need the UI to look good on both mobile and tablet/desktop form factors.

flutter/agent-plugins · 51 tokens

platform-conventions

Design to iOS and Android conventions — what each OS mandates, where they diverge, and when to unify. Use when shipping native apps. For breakpoint adaptation use responsive-design; for matching competitor patterns use jakobs-law (interaction-design).

Owl-Listener/designer-skills · 55 tokens

field-service-mobile-branding-configure

Derive a Field Service mobile app color scheme from a brand source (URL, hex codes, brand-guide paste, or color description), validate WCAG AA contrast in both light and dark mode, and apply the 14-field scheme to the org-default FieldServiceMobileSettings record. Trigger phrases include 'brand the mobile app', 'apply…

forcedotcom/sf-skills · 135 tokens

app-ui-design

Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.

majiayu000/spellbook · 54 tokens