Repository navigation
kings swift
Gui Reis edited this page Oct 8, 2026
·
4 revisions
Swift and iOS. The rules live in two guides found by named path — SWIFT_STYLE_GUIDE and SWIFT_UNIT_TESTS — in the named-path order: the machine's override is the standard, the project's conventions complement it, the default fills what's left.
Source: plugins/kings-swift.
| Component | Type | What it does |
|---|---|---|
unit-tests |
The order of a unit test task: context, approved scenario map, writing handed to the agent, double check, when to run | |
unit-tests-write |
Writes the doubles and the suite of one unit from the approved map — never touches production code, never runs | |
unit-tests-run |
Runs an assembled test command and reports per test — only when the user asked for a run | |
swift-code-style |
Applies the code style and screen structure while writing Swift |
Note
A unit test task.
flowchart TD
A[Unit under test] --> B[unit-tests skill: read the standard, the reference suite, the production code]
B --> C[Scenario map]
C -->|user approves| D[unit-tests-write agent]
D --> E[Mocks, spies, stubs, suite]
E --> F[Double check in the session]
F -->|user asks to run| G[unit-tests-run agent]
G --> H[Per-test result]
Why three pieces: the writer copies a reviewed reference suite and never decides a scenario; the runner never fixes a failure. The AI can't make a test pass by changing the test.