agentleFS
Sign inStart free
loganware05loganware05/captains-compass-cursor/.cursor/skills/ios-engineering/SKILL.md

ios-engineering

Skill2 starsChanged 32 days agoMITView on GitHub

Implements Swift/SwiftUI iOS features with Xcode project awareness, simulator testing, and accessibility labels

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer SwiftUI unless the project is UIKit-first.

    line 21
  2. Distinctive:

    Keep networking and persistence behind clear boundaries.

    line 22
  3. Distinctive:

    Add accessibility labels/traits for interactive controls.

    line 24
  4. Distinctive:

    Run the project's unit/UI tests.

    line 26
  5. Distinctive:

    Document setup (Xcode version, schemes, simulators) in TESTING.md.

    line 27
  6. Distinctive:

    Do not commit signing certificates, provisioning profiles, or API keys

    line 31
  7. Distinctive:

    Do not expand into unrelated backend/cloud work unless the approved plan includes it

    line 32
  8. Distinctive:

    Do not disable ATS or security settings "temporarily" without Captain approval

    line 33

≈ “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

iOS Engineering

Use this Skill when

Working on Swift/SwiftUI (or UIKit) apps, Xcode project settings, app lifecycle, networking, persistence, permissions, simulator/device testing, or iOS accessibility.

Inputs

  • Approved IMPLEMENTATION_PLAN.md
  • Existing Xcode project / SPM / CocoaPods conventions
  • Accessibility and privacy expectations from PROJECT_CONTEXT.md

Procedure

  1. Match existing module and navigation patterns.
  2. Prefer SwiftUI unless the project is UIKit-first.
  3. Keep networking and persistence behind clear boundaries.
  4. Request only required permissions; update Info.plist usage strings carefully.
  5. Add accessibility labels/traits for interactive controls.
  6. Validate on simulator (and device when available); capture screenshots under .agent/evidence/.
  7. Run the project's unit/UI tests; do not weaken failing tests.
  8. Document setup (Xcode version, schemes, simulators) in TESTING.md.

Prohibited actions

  • Do not commit signing certificates, provisioning profiles, or API keys
  • Do not expand into unrelated backend/cloud work unless the approved plan includes it
  • Do not disable ATS or security settings "temporarily" without Captain approval

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