mobile-design
AGENTS.md7 starsChanged 4 days agoMITView on GitHub
Published as an Agent Skill; the canonical content is SKILL.md plus references/. Distributed from GitHub main via npx skills add RubenGlez/mobile-design; there is no build or deploy pipeline. To ship: bump metadata.version in SKILL.md, prepend the matching entry to CHANGELOG.md, commit, then create and push an annotated tag vX.Y.Z on main. The tag is the release reference point; installers pull the current main tree. Licensed MIT. Managed by doctier — do not edit between the markers. Read these for project…
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 repository2 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- mobile-designSkill
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 14
Read these for project context:
≈ “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
mobile-design — agent notes
Published as an Agent Skill; the canonical content is SKILL.md plus references/.
Release
Distributed from GitHub main via npx skills add RubenGlez/mobile-design; there is no build or deploy pipeline. To ship: bump metadata.version in SKILL.md, prepend the matching entry to CHANGELOG.md, commit, then create and push an annotated tag vX.Y.Z on main. The tag is the release reference point; installers pull the current main tree. Licensed MIT.
<!-- doctier:begin -->Project context
Managed by doctier — do not edit between the markers.
Read these for project context:
.rubstack/qa/adversarial-audit-2026-07-03.md
<!-- doctier:end -->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.