01 — The problem
Architecture, security, testing and standards — so the code your agent generates is production-grade, not just plausible.
Without the toolkit
class LoginVC: UIViewController {
UserDefaults.standard.set(
token, forKey: "token")
// 400 more lines
}Massive View Controller · token in plaintext · no tests
With the toolkit
final class LoginViewModel {
let auth: AuthUseCase
func submit() async throws {
try await auth.login()
}
}OAuth2 + PKCE · Keychain · MVVM · typed errors · tests
02 — The team
Specialist roles organised into four tiers that hand off to each other. Higher tiers set constraints lower tiers must respect.
Sets the constraints every lower tier respects.
Builds inside the boundaries Strategy drew.
Finds what Implementation missed.
Nothing merges or ships without this tier.
03 — Install
The everyday workflow needs zero file paths.
cd your-project
git clone https://github.com/sokpichdev/mobile-engineering-agents.git .mobile-agents
echo ".mobile-agents/" >> .gitignoreecho "@.mobile-agents/CLAUDE.md" > CLAUDE.md
echo "@.mobile-agents/.cursorrules" > .cursorrules
echo "@.mobile-agents/.windsurfrules" > .windsurfrules> Build a Profile screen that loads /me and stores
the auth token securely. On its first reply of every session the agent confirms it loaded: Mobile Engineering Agents — loaded ✓
04 — What's inside
05 — Compatibility