agentleFS
maiarowskymaiarowsky/dayhand/AGENTS.md

dayhand

AGENTS.md2 starsChanged 23 days agoApache-2.0View on GitHub

Dayhand (formerly Helm). This repository is public: everything committed here is published. Publishing to npm or Homebrew, merging a release PR or tagging, building or uploading a signed APK, deploying dayhand.dev, touching the waitlist database, changing repository settings or variables. Never bump cli/package.json by hand.

  • Reads credentials
  • 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 32,671 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.

The file

We split this AGENTS.md into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Commit with the GitHub noreply identity already in the git config.

    line 22
  2. Very specific:

    Commit format <type>: <description>.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

AGENTS.md

Dayhand (formerly Helm). This repository is public: everything committed here is published.

Where things are

  • CONTRIBUTING.md: rules for a change, sign-off, commit format, tests each part needs. Read it first.
  • docs/contributing.md: map of the folders. docs/README.md: index of the user docs. docs/architecture.md: backend design.
  • Apps and CLI: android/README.md, macos/README.md, linux/README.md, ios/README.md, cli/README.md. Site: site/STYLE.md. Releases: docs/release.md.

Build and test

  • Backend: cd backend && npm ci --ignore-scripts && npm run typecheck && npm test (starts its own local Convex backend).
  • CLI: backend deps first, then cd cli && npm ci --ignore-scripts && npm test (npm run test:unit: pure tests). After changing a command run npm run build && npm run docs and commit the regenerated files.
  • Android, in android/: ./gradlew :app:testDebugUnitTest :app:lintDebug. macOS, in macos/: swift test. Linux: CMake and ctest, see linux/README.md.
  • Site: scripts/check-site.sh --build.
  • npm packages only through npm ci --ignore-scripts.

Rules

  • Sign off every commit (git commit -s), fix-up commits from review tools included; Signed-off-by matches the author.
  • Commit with the GitHub noreply identity already in the git config; never change it or use a personal email address.
  • Commit format <type>: <description>; types in CONTRIBUTING.md.
  • --json output, error JSON and exit codes are a contract: change them only with the contract tests and schema in the same PR.
  • Docs describe only what is in main; anything unreleased is "coming soon", with no command.
  • Nothing private: no keys, tokens, .env, server addresses, account ids or real tasks. Screenshots use sample data only.

Only on the maintainer's explicit word

Publishing to npm or Homebrew, merging a release PR or tagging, building or uploading a signed APK, deploying dayhand.dev, touching the waitlist database, changing repository settings or variables. Never bump cli/package.json by hand.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.