agentleFS
Sign inStart free
talesofaitalesofai/cohub/AGENTS.md

cohub

AGENTS.md571 starsChanged 3 months agoApache-2.0View on GitHub

Before committing, remove redundant or unnecessary comments and unit tests to keep changes concise. Add Cohub Session: https://cohub.live/spaces/${COHUBSPACEID}/sessions/${COHUBSESSIONID} as a footer, if the environment variables are set. See scripts/changelog/README.md for details.

  • Commits and pushes

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

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Default data loading strategy: prefer local data for interaction, silently fetch related server data to refresh cache and UI, minimize …

    line 8
  2. Distinctive:

    Before committing, remove redundant or unnecessary comments and unit tests to keep changes concise.

    line 14
  3. Very specific:

    Add Cohub Session: https://cohub.live/spaces/${COHUB_SPACE_ID}/sessions/${COHUB_SESSION_ID} as a footer, if the environment variables are …

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 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
  1. Data is paramount — never compromise data safety or integrity
  2. For interaction and UI analysis or changes, study and apply the design skills
  3. Deliver features end-to-end: server, SDK, CLI, and web (desktop and mobile)
  4. First-screen experience is critical — prioritize local data caching
  5. Stay elegant and concise, keep overall consistency; prefer extra refactoring over leaving things messy
  6. Performance matters everywhere: DB, server, and frontend
  7. IndexedDB data always comes from reliable server data
  8. Default data loading strategy: prefer local data for interaction, silently fetch related server data to refresh cache and UI, minimize layout-disrupting loading states, and avoid render thrashing or layout jumps
  9. Care about multi-client sync experience; design elegant and efficient real-time events
  10. Web UI copy uses the existing i18n/Paraglide messages and renders exactly one locale at a time. CLI output, logs, server/API/SDK errors, tests, and developer tooling use concise English only; localized product documentation and locale files are the exceptions.

Git commit

Before committing, remove redundant or unnecessary comments and unit tests to keep changes concise.

Add Cohub Session: https://cohub.live/spaces/${COHUB_SPACE_ID}/sessions/${COHUB_SESSION_ID} as a footer, if the environment variables are set.

Release Workflow

# 1. Publish npm packages: merge the "Version Packages" PR opened by CI

# 2. Generate changelog and create project tag
pnpm changelog:release v1.99.0

# 3. Push
git push && git push origin v1.99.0

See scripts/changelog/README.md for details.

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.

Reviews can't be read right now.

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.

Check your setup, free