top of page
3DaysOfSwift-WebApp-80-tiny.png
Start
1
2
3
My Account

CFA Reference: Toolkit Skills

Formal CFA AI Toolkit for iOS Documentation · Reference 8 of 26

The CFA AI Toolkit for iOS contains eight AI skills and one local analysis tool. Each skill is a folder with a SKILL.md that an AI coding assistant reads before it acts.

Definitions

  • CFA App Creation: Create and continue shaping a new iOS product with CFA.
  • CFA Feature Work: Add, change or remove a feature in a CFA app.
  • CFA Architecture Adoption: Move an existing modern app into CFA.
  • Legacy GCD migration: Replace GCD, operation queues and callbacks with CFA and Swift Concurrency (skill folder swift-concurrency-migration).
  • CFA Architecture Review: Inspect architecture and concurrency, including a Concurrency Migration Health Check, without changing the app.
  • CFA Codebase Tidy: Simplify a CFA project after feature work.
  • CFA Unit Tests: Write and audit tests that protect real feature behaviour.
  • Swift Code Quality: Apply Matt's Swift standards to production code, examples and open-source projects.
  • Xcode Project Dashboard: A local tool that scans a Swift Concurrency project and creates an HTML report of task creation, task ownership, source locations, architecture observations and imported test results.

Rules

  1. Start a request with “Using CFA” when the assistant does not reliably find installed skills, or name the skill.
  2. Keep the seven workflows independent: app creation, CFA feature work, architecture adoption, Legacy GCD migration, read-only architecture review, iterative codebase tidying and CFA unit tests.
  3. Use CFA Architecture Review when nothing should change.
  4. Legacy GCD migration preserves product behaviour; it is not a superficial syntax rewrite.
  5. Finish code changes with the change gate in architecture/cfa-change-gate.md.

Decision rules

  • When you are starting a product, use CFA App Creation.
  • When the app is already CFA and you need a new tab or screen, use CFA Feature Work.
  • When the app uses GCD or callbacks, use Legacy GCD migration and upgrade the whole app in one move.
  • When you want evidence before deciding, run CFA Architecture Review and open the Xcode Project Dashboard report.
  • When feature work has left duplication, use CFA Codebase Tidy.
  • When tests are missing or shallow, use CFA Unit Tests.

Example

The repository README suggests prompts such as these:

Prompts from the repository README

Using CFA, create a new iOS app that finds where I parked my car.
Using CFA, migrate this legacy GCD codebase to Swift Concurrency.
Using CFA, now that we added a new feature, tidy up the code.
Using CFA, make sure each exposed feature is unit tested, for all features.
Using CFA, analyse our use of Swift Concurrency: do we have race conditions that could result in unexpected behaviour?

Common mistakes

  • Asking a review skill to fix things. Review is read-only.
  • Combining migration and new features in one request.
  • Treating the Xcode Project Dashboard as a cloud service. It creates a local HTML report.

Links

bottom of page