agentleFS
Sign inStart free
GiammeGiamme/linear-spanks/skills/extras/tech-swift/SKILL.md

tech-swift

Skill1 starsChanged 28 days agoMITView on GitHub

Technology skill loaded when developing iOS/macOS apps in Swift.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When working with Swift, write safe, expressive, and performant code:

    line 11
  2. Very specific:

    Optionals: Avoid force-unwrapping (!).

    line 13
  3. Very specific:

    Value Types: Use struct by default for models and state.

    line 14
  4. Very specific:

    Concurrency: Use the modern async/await and Task APIs for concurrency instead of legacy Grand Central Dispatch (GCD) closures where …

    line 15
  5. Distinctive:

    Protocol-Oriented: Prefer Protocols and Protocol Extensions for sharing behavior rather than deep class inheritance hierarchies.

    line 16
  6. Very specific:

    SwiftUI State: When using SwiftUI, explicitly differentiate between @State (local), @Binding (passed), and @EnvironmentObject (global).

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Swift Best Practices

Apply this skill after inspecting repository conventions and supported versions. Treat its rules as defaults unless they protect a concrete safety property; preserve an established project pattern when it conflicts, and record the reason in the implementation plan.

When working with Swift, write safe, expressive, and performant code:

  1. Optionals: Avoid force-unwrapping (!). Use if let or guard let to safely unwrap optionals. Prefer guard for early exits to avoid deep nesting.
  2. Value Types: Use struct by default for models and state. Only use class when you explicitly need reference semantics, inheritance, or Objective-C interoperability.
  3. Concurrency: Use the modern async/await and Task APIs for concurrency instead of legacy Grand Central Dispatch (GCD) closures where possible.
  4. Protocol-Oriented: Prefer Protocols and Protocol Extensions for sharing behavior rather than deep class inheritance hierarchies.
  5. SwiftUI State: When using SwiftUI, explicitly differentiate between @State (local), @Binding (passed), and @EnvironmentObject (global). Do not over-couple views to global state.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free