agentleFS
clarkchenkaiclarkchenkai/travel.skill/AGENTS.md

travel.skill

AGENTS.md0 starsChanged 2 months agoMITView on GitHub

Use the user's language and actual trip constraints. The gallery defaults to English; that does not prescribe every traveler's language or visual style. Read only the skills and references relevant to the task. Their canonical content lives in skills/; discovery files for individual agents only point there. skill/SKILL.md remains a compatible command-oriented entry. npm run new -- <example> · npm run new -- --from <trip> --trip <new-trip> · npm run new -- --blank --trip <trip> · npm run template --…

The file

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

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

  • ≈0

    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. Distinctive:

    Use the user's language and actual trip constraints.

    line 3
  2. Very specific:

    Read only the skills and references relevant to the task.

    line 13
  3. Very specific:

    Keep original materials in input/ or the user's original location.

    line 18
  4. Distinctive:

    Do not invent facts, bookings, eligibility, company policy or current rules.

    line 19
  5. Distinctive:

    Use stable IDs and one source per fact.

    line 20

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

Travel workspace for coding agents

Use the user's language and actual trip constraints. The gallery defaults to English; that does not prescribe every traveler's language or visual style.

Select the relevant skill

  • Planning, bookings, budget, companions, changes and settlement: travel-management.
  • Turning materials into a usable website, integration and delivery: travel-product-studio.
  • Visual direction, comparison and refinement: design-with-ai.
  • Selecting, modifying or creating templates, pages and modules: travel-template-studio.
  • Cross-border requirements, complex travel and evidence-based acceptance: travel-verification.

Read only the skills and references relevant to the task. Their canonical content lives in skills/; discovery files for individual agents only point there. skill/SKILL.md remains a compatible command-oriented entry.

Shared execution rules

  • Existing templates are starting points. Generate the code needed for the user's task; do not force a fixed theme, country, page count or module list.
  • Keep original materials in input/ or the user's original location; never modify or publish them. Store public travel facts separately from private companion files and receipt originals.
  • Do not invent facts, bookings, eligibility, company policy or current rules. User confirmation is evidence of the stated decision; independent verification of details is separate.
  • Use stable IDs and one source per fact. A data change must update its dependent views; personal checks do not prove supplier action or multi-user synchronization.
  • Respect authorization already given. Planning does not itself authorize a purchase, cancellation, message or public deployment. Re-check uncertain external transaction status before retrying.
  • Build and inspect the actual artifact. Run relevant logic tests and browser tasks; distinguish static validity, runtime behavior, publication, target-network access and real adoption.

Commands

npm run new -- <example> · npm run new -- --from <trip> --trip <new-trip> · npm run new -- --blank --trip <trip> · npm run template -- --trip <trip> · npm run dev · npm run validate · npm run gaps · npm run build · npm run check · npm test.

Node.js 20+; the core has no installed dependencies. A trip-local template/ is automatically used by preview/build; declare its additional source files in template/manifest.json. Unknown draft facts should remain unknown until supplied; a blank draft must be completed before a production build passes validation.

Finish with the result, usable entry, actual verification and the shortest next step. Do not claim a rule exists merely because a checklist mentions 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.