JWW Swift Style

The primary rule: generate code that looks as though it belongs beside the code being changed. The nearest surrounding Swift source and the applicable AGENTS.md are the final authority. Everything below is the default only where the surrounding code is silent — chiefly new top-level files.

Inputs and Output

• Take as inputs the target Swift file or diff, a nearby comparable source file, and every applicable AGENTS.md.
• Produce a minimal Swift edit or style review that matches those local conventions. State the validation performed when making an edit.

Before Writing

1. Read the target file and a nearby comparable file. Read each applicable nested AGENTS.md.
2. Preserve existing structure, import ordering, access-control style, and all MARK and section dividers. Do not perform unrelated formatting or style cleanup.
3. Select APIs appropriate to the target platform and module. Keep shared code compatible with every platform the module supports unless narrow platform conditionals are required.

Source Layout

• Use four-space indentation and blank lines to group declarations and logical steps.
• Add sections to substantial types only when the repository already uses the divider style shown below. Match the neighboring files exactly: some use only the // MARK: line, others follow it with the box comment. Keep existing section names and ordering when extending a type.