Skip to content
Mobile
Skill

/swift-formatstyle

Formats and parses locale-aware numbers, decimals, currencies, percentages, dates, durations, measurements, names, lists, byte counts, and URLs with Foundation FormatStyle and ParseableFormatStyle. Use when replacing legacy Formatter subclasses, designing reusable format APIs,

From plugin
swift-ios-skills
1.3k86 skills1 MCP

Claude Code

$ npx -y skills add dpearson2699/swift-ios-skills --skill swift-formatstyle --agent claude-code

SKILL.md

swift-formatstyle.SKILL.md
name: swift-formatstyle
description: "Formats and parses locale-aware numbers, decimals, currencies, percentages, dates, durations, measurements, names, lists, byte counts, and URLs with Foundation FormatStyle and ParseableFormatStyle. Use when replacing legacy Formatter subclasses, designing reusable format APIs, using SwiftUI Text(_:format:), correcting availability, or testing user-facing formatted output across locales."

Swift FormatStyle

Use Foundation's type-safe `FormatStyle` APIs for user-facing display and `ParseableFormatStyle` when the same convention must accept input. Route String Catalogs, plurals, localized copy, bundles, and RTL layout to `ios-localization`; formatting still requires locale review even when no text is translated.

Contents

  • [Workflow](#workflow)
  • [Quick Reference](#quick-reference)
  • [Selection and Availability](#selection-and-availability)
  • [Parsing](#parsing)
  • [SwiftUI Integration](#swiftui-integration)
  • [Custom FormatStyle](#custom-formatstyle)
  • [Common Mistakes](#common-mistakes)
  • [Review Checklist](#review-checklist)
  • [References](#references)

Workflow

1. Identify the value's semantic type and whether output is display-only or must round-trip through parsing. 2. Select the narrowest built-in style and keep the user's current locale unless a wire format explicitly requires another locale. 3. Render the exact UI with representative locales such as `en_US`, `de_DE`, `ar_SA`, and `ja_JP`. 4. Check separators, numbering systems, calendars, currency and unit conventions, text direction, and layout. 5. If output or parsing fails, fix the style or surrounding copy, restore the input fixture, and rerun the same locale matrix.

Load [FormatStyle Recipes](references/formatstyle-recipes.md) when implementation needs concrete modifiers, date intervals, relative dates, duration patterns, measurements, names, lists, byte counts, or URL component controls.

Quick Reference

| Value | Default style | Important constraint | |---|---|---| | `Int`, `Double` | `.number` | Configure precision, rounding, grouping, notation, or sign only as required. | | `Decimal` | `.number`, `.percent`, `.currency(code:)` | Prefer for exact decimal display and parsing. | | Currency | `.currency(code:)` | Pass an ISO 4217 code; never hardcode a symbol. | | Percent | `.percent` | Confirm whether the input is a fraction (`0.85`) or whole percent (`85`). | | `Date` | `.dateTime`, `.relative`, `.interval` | Relative output should usually stand alone, not be embedded in a sentence. | | `Duration` | `.time(pattern:)`, `.units(allowed:width:)` | Requires iOS 16+; choose compact clock output versus labeled units. | | `Measurement` | `.measurement(width:usage:)` | `usage:` controls locale-aware conversion policy. | | `PersonNameComponents` | `.name(style:)` | Do not manually concatenate name parts. | | Collections | `.list(type:width:)` | Let locale rules choose separators and conjunctions. | | Byte count | `.byteCount(style:)` | Choose file, memory, decimal, or binary semantics deliberately. | | `URL` | `.url` | Requires iOS 16+; query, port, and fragment are opt-in display components. |

Selection and Availability

  • Prefer `FormatStyle` over legacy `NumberFormatter`, `DateFormatter`, `DateComponentsFormatter`, and manual interpolation for new iOS 15+ code.
  • `Duration` format styles and `URL.FormatStyle` require iOS 16+.
  • `Date.AnchoredRelativeFormatStyle` requires iOS 18+ and formats relative to a fixed anchor rather than the current moment.
  • Omit `.locale(...)` for normal UI so the style inherits the user's locale. Use a fixed locale only for an explicit protocol or test fixture.
  • Treat relative date output as standalone text unless the entire sentence is localized around it.

Docs: [FormatStyle](https://sosumi.ai/documentation/foundation/formatstyle)

Parsing

Use the matching parseable style when users edit or import formatted values:

let style = Decimal.FormatStyle.Currency(code: "USD")
    .locale(Locale(identifier: "en_US"))

let value = try Decimal("$3,500.63", format: style)
let display = value.formatted(style)

The fixed locale above is appropriate only because the input contract is explicitly `en_US`. For normal UI input, use the user's locale and test round trips with representative decimal separators, currency placement, calendars, and numbering systems.

SwiftUI Integration

Prefer `Text(_:format:)` so SwiftUI owns the formatted value:

Text(price, format: .currency(code: currencyCode))
Text(date, format: .dateTime.month().day().year())
Text(duration, format: .units(allowed: [.minutes, .seconds]))

For every user-facing formatted `Text`, preview or test the exact screen across the locale matrix. Use `Text(.now, style: .timer)`, `Text(.now, style: .relative)`, or `Text(timerInterval:)` for live-updating time displays rather than manually scheduling string refreshes.

Custom FormatStyle

Create a custom style only when built-in composition cannot express the domain convention. `FormatStyle` refines `Codable` and `Hashable`; keep styles as reusable values and add `ParseableFormatStyle` only when input must round-trip.

struct AbbreviatedCountStyle: FormatStyle {
    func format(_ value: Int) -> String {
        switch value {
        case ..<1_000: "\(value)"
        case 1_000..<1_000_000: String(format: "%.1fK", Double(value) / 1_000)
        default: String(format: "%.1fM", Double(value) / 1_000_000)
        }
    }
}

extension FormatStyle where Self == AbbreviatedCountStyle {
    static var abbreviatedCount: Self { .init() }
}

Custom styles still need locale and accessibility review; a compact English suffix may not be suitable for every locale.

Common Mistakes

| Mistake | Fix | |---|---| | Manual formatting or legacy formatter allocation in view code | Use the matching `FormatStyle` and `Text(_:format:)`. | | Hardcoded currency symbol or locale | Pass an ISO currency code and inherit the

Read more
@dpearson2699
Ships withswift-ios-skills

86 agent skills optimized for iOS 26+ development with Swift 6.3 and modern Apple frameworks.

1.3k86 skills1 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
1.3k
Star history of dpearson2699/swift-ios-skills on GitHub, a chart by star-history.com

Other skills on swift-ios-skills.

alarmkit

alarmkit

Implement AlarmKit alarms and countdown timers for iOS and iPadOS with Lock Screen, Dynamic Island, StandBy, and paired Apple…

app-clips

app-clips

Build iOS App Clips with invocation URLs, App Clip Codes, NFC, QR codes, Safari banners, Maps, Messages, target setup, App Store…

More skills from other plugins.

deep-code-review

deep-code-review

In-depth design-focused code review - understands codebase context before evaluating PR changes, posts structured feedback to…

expo1d53k
@expo@expoInstall Skill
modlens

modlens

Plug-in vision for text-only models. Hard rule: when a file path or URL with an image extension (.png, .jpg, .jpeg, .webp, .gif,…

modlens2w4.6k
@liustack@liustackInstall Skill
appllama-app-design-skill

appllama-app-design-sk…

Build native-feeling, benchmark-quality mobile app screens (Expo / React Native). Use when designing or implementing any mobile…

appllama2mo3.9k
@appllama@appllamaInstall Skill

Questions about swift-formatstyle.

Which coding agents can use swift-formatstyle?
swift-formatstyle installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.