SwiftUI-Architecture-Agent-Skill
AGENTS.md2 starsChanged 51 days agoMITView on GitHub
This repository is an Agent Skills package for SwiftUI app architecture. Construction: App composes dependencies and owns shared lifetimes. Factories create one Manager, UseCase, or ViewModel per method using supplied dependencies. Start with one factory; split by domain or platform when current complexity warrants it. Runtime: View → ViewModel → UseCase → Manager when those layers are present. Factories never hide feature/application graphs or perform business logic. ViewModels may depend on multiple focused UseCase protocols. ViewModel → ViewModel and UseCase…
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 31,774 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 repositoryOne other file it gives its agents.
- swiftui-architectureSkill
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
Start with skills/swiftui-architecture/SKILL.md for workflows and non-negotiable rules.
- Very specific: line 6
Use skills/swiftui-architecture/references/ for layer details, folder structure, and checklists.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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
Agent instructions
This repository is an Agent Skills package for SwiftUI app architecture.
- Start with
skills/swiftui-architecture/SKILL.mdfor workflows and non-negotiable rules. - Use
skills/swiftui-architecture/references/for layer details, folder structure, and checklists. - Human index:
ARCHITECTURE-CHECKS.md.
Construction: App composes dependencies and owns shared lifetimes. Factories create one Manager, UseCase, or ViewModel per method using supplied dependencies. Start with one factory; split by domain or platform when current complexity warrants it. Runtime: View → ViewModel → UseCase → Manager when those layers are present. Factories never hide feature/application graphs or perform business logic.
ViewModels may depend on multiple focused UseCase protocols. ViewModel → ViewModel and UseCase → UseCase dependencies are forbidden; UseCases call manager protocols directly.
Feature views receive exactly one owning ViewModel. Composition views may assemble independent features using multiple child ViewModels supplied by App. Reusable visual components receive values, bindings, and action closures.
Navigation is a presentation-state exception: feature/composition Views may access scoped navigation, while ViewModels/UseCases may not. Scene/root composition may own local navigation state per stack/window; App defines business-service sharing.
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.