slopwake
AGENTS.md0 starsChanged 10 days agoMITView on GitHub
- Require macOS 26+ and Xcode 26+. - Run make release-check for docs-only changes. Run make verify for product, build, installer, release, or CI changes before handoff. - Edit project.yml; Slopwake.xcodeproj is generated. - A push to main releases by commit type, per the rules in .releaserc.json. Pick the type for the release it should cause. - If a release stops after its draft exists, fix the failing step and resume with gh workflow run ci.yml --ref main -f "release_version=$(sed…
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 repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- spm-build-analysisSkill
- swift-concurrencySkill
- swift-testing-expertSkill
- swiftui-expert-skillSkill
- xcode-build-benchmarkSkill
- xcode-build-fixerSkill
- xcode-build-orchestratorSkill
- xcode-compilation-analyzerSkill
- xcode-project-analyzerSkill
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 1 is common, 2 are distinctive, and 2 are very specific to this project.
≈1
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Run make release-check for docs-only changes.
- Very specific: line 12
If a release stops after its draft exists, fix the failing step and resume with gh workflow run ci.yml --ref main -f "release_version=$(sed …
- Distinctive: line 14
Never publish a draft by hand or reuse a tag with different bytes.
- Common: line 21
Keep signing and notarization credentials outside the repository.
- Distinctive: line 23
Keep the README banner on uinaf.dev, not in the repository.
≈ “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
Agent guidance
Start
- Require macOS 26+ and Xcode 26+.
- Run
make release-checkfor docs-only changes. Runmake verifyfor product, build, installer, release, or CI changes before handoff. - Edit
project.yml;Slopwake.xcodeprojis generated. - A push to
mainreleases by commit type, per the rules in.releaserc.json. Pick the type for the release it should cause. - If a release stops after its draft exists, fix the failing step and resume
with
gh workflow run ci.yml --ref main -f "release_version=$(sed -n '1p' VERSION)". Never publish a draft by hand or reuse a tag with different bytes.
Boundaries
- Policy and child-process contracts live in
Sources/SlopwakeCore/. - AppKit, SwiftUI, IOKit, Service Management, and
UserDefaultscode lives inSlopwakeApp/. - Keep signing and notarization credentials outside the repository; use them only at the release command boundary.
- Keep the README banner on uinaf.dev, not in the repository.
Tests/pins detection, wake policy, child-process, and persistence behavior. Change a test only when that contract changes on purpose.
Repository skills
- Swift concurrency: tasks, actor isolation, Sendable, callback-to-async.
- SwiftUI: views, state, layout, accessibility.
- Swift testing: test architecture and async test failures; keep the existing test framework.
- Xcode build optimization: build timing; keep
project.ymlas the project source.
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.