Source profileQuality 78/100

dpearson2699/swift-ios-skills/skills/swift-formatstyle/SKILL.md

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, using SwiftUI Text(_:format:), correcting availability, or testing user-facing formatted output across locales.

Source repository stars
933
Declared platforms
0
Static risk flags
0
Last source update
2026-07-15
Source checked
2026-07-28

Decision brief

What it does—and where it fits

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…

Best for

  • Use when replacing legacy Formatter subclasses, designing reusable format APIs, using SwiftUI Text(_:format:), correcting availability, or testing user-facing formatted output across locales.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/dpearson2699/swift-ios-skills --skill "skills/swift-formatstyle"
Safe inspection promptEditorial

Inspect the Agent Skill "swift-formatstyle" from https://github.com/dpearson2699/swift-ios-skills/blob/90c9573272531337962fbb3505036d61ed23389a/skills/swift-formatstyle/SKILL.md at commit 90c9573272531337962fbb3505036d61ed23389a. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    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 representat…

    Identify the value's semantic type and whether output is display-only or must round-trip through parsing.Select the narrowest built-in style and keep the user's current locale unless a wire format explicitly requires another locale.Render the exact UI with representative locales such as enUS, deDE, arSA, and jaJP.
  2. 02

    Review Checklist

    [ ] Semantic value type and display-versus-parse requirement identified

    [ ] Semantic value type and display-versus-parse requirement identified[ ] Built-in FormatStyle used where it can express the convention[ ] Availability gated beside iOS 16+ and iOS 18+ APIs
  3. 03

    Quick Reference

    Review the “Quick Reference” section in the pinned source before continuing.

    Review and apply the “Quick Reference” source section.
  4. 04

    Selection and Availability

    Prefer FormatStyle over legacy NumberFormatter, DateFormatter, DateComponentsFormatter, and manual interpolation for new iOS 15+ code.

    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.
  5. 05

    Parsing

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

    Use the matching parseable style when users edit or import formatted values:The fixed locale above is appropriate only because the input contract is explicitly enUS. For normal UI input, use the user's locale and test round trips with representative decimal separators, currency placement, calen…

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score78/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars933SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
dpearson2699/swift-ios-skills
Skill path
skills/swift-formatstyle/SKILL.md
Commit
90c9573272531337962fbb3505036d61ed23389a
License
NOASSERTION
Collected
2026-07-28
Default branch
main
View the original SKILL.md

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

  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 when implementation needs concrete modifiers, date intervals, relative dates, duration patterns, measurements, names, lists, byte counts, or URL component controls.

Quick Reference

ValueDefault styleImportant constraint
Int, Double.numberConfigure 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.percentConfirm whether the input is a fraction (0.85) or whole percent (85).
Date.dateTime, .relative, .intervalRelative 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.urlRequires 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

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

MistakeFix
Manual formatting or legacy formatter allocation in view codeUse the matching FormatStyle and Text(_:format:).
Hardcoded currency symbol or localePass an ISO currency code and inherit the user locale unless the contract says otherwise.
Binary floating-point for exact decimal inputUse Decimal.FormatStyle and its matching parse strategy.
Assuming URL.formatted() preserves every componentOpt in to .port(.always), .query(.always), or .fragment(.always) only when those components should display.
Relative date output embedded in a larger sentenceKeep it standalone or localize the complete sentence.
Clock-style duration used for proseUse .units(allowed:width:) for labeled output.
Measurement conversion left implicitSelect a usage: appropriate to the UI.
One-locale spot checkRun the same exact-screen fixture across representative locales and fix/rerun failures.

Review Checklist

  • Semantic value type and display-versus-parse requirement identified
  • Built-in FormatStyle used where it can express the convention
  • Availability gated beside iOS 16+ and iOS 18+ APIs
  • Currency uses an ISO 4217 code; exact decimal values use Decimal
  • User locale inherited unless a protocol explicitly fixes it
  • Relative date text stands alone or the full sentence is localized
  • URL components and measurement usage: are deliberate
  • SwiftUI uses Text(_:format:) for formatted values
  • Exact rendered UI and parse round trips pass the representative-locale matrix

References

Alternatives

Compare before choosing