ios-developer-agents
CLAUDE.md30 starsChanged 11 months agoMITView on GitHub
This repository contains AI agent prompts for iOS development workflows. These agents help validate, audit, and improve iOS applications. Use when: Preparing to submit to App Store Connect Use when: Before release, after adding authentication, or during security reviews Use when: Building UI, before releases, or when improving accessibility Use the slash commands to invoke agents: Source prompts are in agents/[name]/[name].md: - agents/app-store-validator/app-store-validator.md - agents/security-auditor/security-auditor.md - agents/accessibility-validator/accessibility-validator.md When using these agents on your iOS project, provide context about: - Core…
In this repository6 other files it gives its agents.
The file
We split this CLAUDE.md into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
Use when: Before release, after adding authentication, or during security reviews
- Distinctive: line 24
Use the slash commands to invoke agents:
- Distinctive: line 39
When using these agents on your iOS project, provide context about:
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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
iOS Developer Agents
This repository contains AI agent prompts for iOS development workflows. These agents help validate, audit, and improve iOS applications.
Available Agents
App Store Validator
Pre-validates iOS apps against Apple's App Store Review Guidelines before submission. Catches rejection-worthy issues early.
Use when: Preparing to submit to App Store Connect
Security Auditor
Comprehensive security audit against OWASP Mobile Top 10 2024. Detects vulnerabilities, hardcoded secrets, and insecure configurations.
Use when: Before release, after adding authentication, or during security reviews
Accessibility Validator
Audits apps for accessibility compliance with Apple HIG, WCAG 2.2, VoiceOver, and Dynamic Type standards.
Use when: Building UI, before releases, or when improving accessibility
Usage with Claude Code
Use the slash commands to invoke agents:
/validate-appstore- Run App Store validation on the current project/audit-security- Run security audit on the current project/audit-accessibility- Run accessibility audit on the current project
Agent Files
Source prompts are in agents/[name]/[name].md:
agents/app-store-validator/app-store-validator.mdagents/security-auditor/security-auditor.mdagents/accessibility-validator/accessibility-validator.md
For iOS Projects Using These Agents
When using these agents on your iOS project, provide context about:
- Core app functionality
- Authentication methods
- Third-party SDKs used
- Sensitive data handled
- Compliance requirements (HIPAA, PCI-DSS, etc.)
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.