meta-wearables-dat-android
Copilot instructions382 starsChanged 23 days agoLicence not identifiedView on GitHub
Full API reference: https://wearables.developer.meta.com/llms.txt?full=true DAT docs MCP: https://mcp.developer.meta.com/wearables Developer docs: https://wearables.developer.meta.com/docs/develop/ The SDK is organized into four public modules: DeviceSession.start() is fire-and-forget and returns Unit; capabilities can only be attached…
We split this copilot-instructions.md into the rules it gives an agent
40 rules. About 0 are common, 15 are distinctive, and 25 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈15
Distinctive · estimate
This author's own choices. Worth a look.
25
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions 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.
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,297 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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/audio-streaming.mdcCursor rule
- .cursor/rules/camera-capture.mdcCursor rule
- .cursor/rules/camera-streaming.mdcCursor rule
- .cursor/rules/dat-conventions.mdcCursor rule
- .cursor/rules/debugging.mdcCursor rule
- .cursor/rules/display-access.mdcCursor rule
- .cursor/rules/getting-started.mdcCursor rule
- .cursor/rules/inputs.mdcCursor rule
- .cursor/rules/mockdevice-testing.mdcCursor rule
- .cursor/rules/motion.mdcCursor rule
- .cursor/rules/permissions-registration.mdcCursor rule
- .cursor/rules/sample-app-guide.mdcCursor rule
- .cursor/rules/session-lifecycle.mdcCursor rule
- .cursor/rules/speech.mdcCursor rule
- .cursor/rules/voice-invocations.mdcCursor rule
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.

