azents / swift
AGENTS.md16 starsChanged 25 days agoMITView on GitHub
Swift code follows the repository's language-first layout: Read .claude/rules/conventions.md and .claude/rules/swift-conventions.md before editing Swift sources. Read applicable convention bodies; do not copy these rules into individual app instructions. Git-tracked text and comments follow the repository's English language rule. All application commands run from the repository root: ci runs bootstrap, format check, lint, generated project, simulator tests, and unsigned builds in that order. The same entry point is used in GitHub Actions. Formatting uses the selected Xcode's swift-format; lint uses checksummed…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/conventions/AGENTS.mdAGENTS.md
- python/AGENTS.mdAGENTS.md
- typescript/AGENTS.mdAGENTS.md
- .claude/conventions/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- python/CLAUDE.mdCLAUDE.md
- swift/CLAUDE.mdCLAUDE.md
- typescript/CLAUDE.mdCLAUDE.md
- add-conventionSkill
- ci-optimizationSkill
- code-reviewSkill
- convention-auditSkill
- create-prSkill
- dependabot-alertsSkill
- e2e-debuggingSkill
- frontend-designSkill
- github-markdown-bodiesSkill
- living-spec-auditSkill
- openapi-client-genSkill
- python-dependency-managementSkill
- python-dependency-tree-analysisSkill
- python-dependency-updateSkill
- python-quality-checkSkill
- ship-featureSkill
- ship-prSkill
- skill-creatorSkill
- spec-reviewSkill
- stacked-prsSkill
- technical-feature-designSkill
- typescript-dependency-tree-analysisSkill
- typescript-dependency-updateSkill
- typescript-quality-checkSkill
- ui-visual-reviewSkill
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 15
All application commands run from the repository root:
≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md 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.
Files
Swift Workspace
Swift code follows the repository's language-first layout:
apps/azents-ios/: native iOS application and its UI tests.- Future reusable Swift libraries belong under
libs/when actually needed.
Read .claude/rules/conventions.md and
.claude/rules/swift-conventions.md before editing Swift sources. Read applicable
convention bodies; do not copy these rules into individual app instructions.
Git-tracked text and comments follow the repository's English language rule.
Quality and Build
All application commands run from the repository root:
bash swift/scripts/ios.sh bootstrap
bash swift/scripts/ios.sh format
bash swift/scripts/ios.sh format-check
bash swift/scripts/ios.sh lint
bash swift/scripts/ios.sh test
bash swift/scripts/ios.sh buildci runs bootstrap, format check, lint, generated project, simulator tests, and
unsigned builds in that order. The same entry point is used in GitHub Actions.
Formatting uses the selected Xcode's swift-format; lint uses checksummed
SwiftLint. The compiler uses Swift 6 isolation checks and treats warnings as
errors. Do not weaken these checks to make a build pass.
These commands require macOS and the exact Xcode in toolchain.sh. A Linux Agent
must use the GitHub macOS CI job for real SwiftUI compilation and simulator
tests; do not report Linux structural checks as an iOS build.
Project and Tests
project.yml is the Xcode project input. XcodeGen is bootstrapped at a fixed
version and checksum; generated .xcodeproj directories are ignored. Do not add
a parallel hand-maintained project. The application currently has no Swift
package dependencies or server connection.
UI tests launch the real app and wait for observable UI state. Use XCTest expectations/element waits, not fixed sleeps. Deterministic unit tests should be added when domain logic exists; do not manufacture a domain layer for static Hello World text.
Artifacts and Security
CI publishes simulator .app and unsigned device .xcarchive ZIPs, a source
manifest, logs, and test results. These are build evidence, not iPhone-installable
IPAs. This stage has no Apple account, signing key, provisioning profile,
TestFlight, or store submission. Do not add those to solve an unsigned-build
failure. Never give fork PR jobs signing/upload secrets.
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
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.

