agentleFS
iamvicliuiamvicliu/AgentHub/AGENTS.md

AgentHub

AGENTS.md80 starsChanged 4 months agoMITView on GitHub

Always read DESIGN.md before making any visual or UI decisions. All font choices, colors, spacing, layout, and aesthetic direction are defined there. Do not deviate without explicit user approval. Key rules at a glance: In QA mode, flag any code that doesn't match DESIGN.md. Do not run E2E tests during local development unless the user explicitly asks; they are too slow.

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

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always read DESIGN.md before making any visual or UI decisions.

    line 3
  2. Distinctive:

    All font choices, colors, spacing, layout, and aesthetic direction are defined there.

    line 4
  3. Distinctive:

    Do not deviate without explicit user approval.

    line 5
  4. Distinctive:

    Do not run E2E tests during local development unless the user explicitly asks.

    line 22

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

Design System

Always read DESIGN.md before making any visual or UI decisions. All font choices, colors, spacing, layout, and aesthetic direction are defined there. Do not deviate without explicit user approval.

Key rules at a glance:

  • Public web is content-first: show real Sessions and authors before feature explanations
  • Share creates a Link-only URL; Publish is the separate, explicit Public action
  • Public metadata is author-attributed (@handle · published 2h ago), never first-person
  • Warm amber accent #C85A00 (light) / #F07020 (dark) — never blue or purple
  • Warm near-black #141410 for dark mode — never pure #000 or cold #0A0A0A
  • Geist Sans for UI chrome; Geist Mono for Session records, commands, URLs, and paths
  • Session pages separate interpretive Summary from machine-derived evidence
  • Visibility and continuation lineage must remain explicit trust signals
  • Emoji are placeholder icons only — production UI uses Lucide React SVGs
  • "via ACP · local" remains mandatory wherever local AI synthesis appears

In QA mode, flag any code that doesn't match DESIGN.md.

Do not run E2E tests during local development unless the user explicitly asks; they are too slow.

Download now (ZIP)

  • 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 28,693 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.

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.