iphone-duo-skills
AGENTS.md4 starsChanged 2 months agoMITView on GitHub
This repository publishes portable Agent Skills for adapting iPhone apps to iPhone Duo. These notes are for agents and people editing the skills, not for apps that install them.
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,700 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 repository8 other files it gives its agents.
- iphone-duo-cameraSkill
- iphone-duo-designSkill
- iphone-duo-developmentSkill
- iphone-duo-layoutSkill
- iphone-duo-readinessSkill
- iphone-duo-scenesSkill
- iphone-duo-testingSkill
- iphone-duo-toolbarsSkill
The file
We split this AGENTS.md into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 5
Read CONTRIBUTING.md and SOURCES.md before editing a skill.
- Very specific: line 6
Keep one canonical copy of each skill under skills/.
- Distinctive: line 7
Keep every skill folder self-contained: links from a skill may only point inside that folder.
- Very specific: line 10
Keep agents/openai.yaml optional.
- Very specific: line 11
Run scripts/validate.py and the unit tests for any change, scripts/smoke_agents.py for packaging changes, and scripts/check-sdk.sh on a Mac …
- Distinctive: line 12
Do not describe an installer smoke check as an end-to-end agent test, or a type-check as runtime evidence.
≈ “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
Working on this repository
This repository publishes portable Agent Skills for adapting iPhone apps to iPhone Duo. These notes are for agents and people editing the skills, not for apps that install them.
- Read CONTRIBUTING.md and SOURCES.md before editing a skill.
- Keep one canonical copy of each skill under
skills/. Do not fork instructions per agent. - Keep every skill folder self-contained: links from a skill may only point inside that folder. Refer to sibling skills by name, not by relative path.
iphone-duo-developmentis the entry point. When you add, rename, or remove a skill, update its routing table, the README catalog, and the changelog.- Tie every API claim to an Apple source link and a check date. Label session-only statements, repository recommendations, and field observations as such.
- Keep
agents/openai.yamloptional; the core instructions must work without it. - Run
scripts/validate.pyand the unit tests for any change,scripts/smoke_agents.pyfor packaging changes, andscripts/check-sdk.shon a Mac with Xcode 27.1 or later when you change a probe-covered API. - Do not describe an installer smoke check as an end-to-end agent test, or a type-check as runtime evidence.
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.