agentleFS
Sign inStart free
jmarek41jmarek41/surf-guide/AGENTS.md

surf-guide

AGENTS.md0 starsChanged 4 months agoMITView on GitHub

This repository provides a community surf knowledge base plus local-only rider data. - data/ is private and gitignored. Rider profiles, exact bases, board history, recommendations, raw session logs, and personal calibration belong there. - locations/ is public. Only sourced spot facts and anonymized, generalized calibration belong there. - Never move information from data/ into locations/ automatically. Propose the generalized lesson and ask the user before preparing a public change. - Never reveal secrets, unpublished breaks, private shop/seller messages, rental bookings,…

  • 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 repository6 other files it gives its agents.

The file

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

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

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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
  1. Very specific:

    Never move information from data/ into locations/ automatically.

    line 12
  2. Common:

    Never reveal secrets, unpublished breaks, private shop/seller messages, rental bookings, exact accommodation addresses, or personally …

    line 14
  3. Distinctive:

    Do not silently filter good surf because of crowd, localism, danger, distance, or skill.

    line 26
  4. Distinctive:

    Treat raw session observations as ground truth for that surfer's local calibration, not as universal truth.

    line 29
  5. Very specific:

    Follow method/calibration-promotion.md when a private observation may help other surfers.

    line 31
  6. Distinctive:

    Do not commit or push unless the user explicitly requests it.

    line 45

≈ “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.

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

Surf Guide — agent context

This repository provides a community surf knowledge base plus local-only rider data.

Privacy boundary

  • data/ is private and gitignored. Rider profiles, exact bases, board history, recommendations, raw session logs, and personal calibration belong there.
  • locations/ is public. Only sourced spot facts and anonymized, generalized calibration belong there.
  • Never move information from data/ into locations/ automatically. Propose the generalized lesson and ask the user before preparing a public change.
  • Never reveal secrets, unpublished breaks, private shop/seller messages, rental bookings, exact accommodation addresses, or personally identifying session details.

Quality rules

  • For factual spot, board, availability, or forecast claims, prefer two independent sources. If that is not available, label the claim single-source or unverified; never fill a field by guessing.
  • Distinguish public research, model output, inference, and first-hand observation.
  • A forecast is advisory. Surface uncertainty, hazards, and source disagreement.
  • Do not silently filter good surf because of crowd, localism, danger, distance, or skill. Rank surf quality, then clearly annotate those considerations unless the rider profile defines a hard exclusion.
  • Treat raw session observations as ground truth for that surfer's local calibration, not as universal truth.
  • Follow method/calibration-promotion.md when a private observation may help other surfers. Keep the raw evidence private, maintain contributor counts, and require explicit user approval before editing a public calibration.

Repository map

  • .agents/skills/ — portable Agent Skills workflows.
  • method/ — shared forecasting and board-selection methods.
  • scan/ — public short-trip destination catalog.
  • locations/ — contributed public location packs.
  • templates/ — schemas for local and public data.
  • scripts/ — offline validation and the optional flight-pricing helper.
  • data/ — ignored local state created by the skills.

Do not commit or push unless the user explicitly requests it.

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.

Check your setup, free