agentleFS
ElasticKnown publisherelastic/elastic-ramen/AGENTS.md

elastic-ramen

AGENTS.md19 starsChanged 8 months agoMITView on GitHub

Prefer single word names for variables and functions. Only use multiple words if necessary. THIS RULE IS MANDATORY FOR AGENT WRITTEN CODE. Reduce total variable count by inlining when a value is only used once. Avoid unnecessary destructuring. Use dot notation to preserve context. Prefer const over let. Use ternaries or early returns instead of reassignment. Avoid else statements. Prefer early returns. Use snake_case for field names so column names don't need to be redefined as strings.

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

19 rules. About 0 are common, 13 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    ALWAYS USE PARALLEL TOOLS WHEN APPLICABLE.

    line 3
  2. Distinctive:

    Prefer automation: execute requested actions without confirmation unless blocked by missing info or safety/irreversibility.

    line 6
  3. Distinctive:

    Keep things in one function unless composable or reusable

    line 12
  4. Very specific:

    Avoid try/catch where possible

    line 13
  5. Very specific:

    Avoid using the any type

    line 14
  6. Distinctive:

    Prefer single word variable names where possible

    line 15
  7. Very specific:

    Use Bun APIs when possible, like Bun.file()

    line 16
  8. Distinctive:

    Prefer functional array methods (flatMap, filter, map) over for loops.

    line 18
  9. Distinctive:

    Prefer single word names for variables and functions.

    line 22
  10. Distinctive:

    Use single word names by default for new locals, params, and helper functions.

    line 28
  11. Distinctive:

    Do not introduce new camelCase compounds when a short single-word alternative is clear.

    line 30
  12. Distinctive:

    Before finishing edits, review touched lines and shorten newly introduced identifiers where possible.

    line 31
  13. Distinctive:

    Avoid unnecessary destructuring.

    line 58
  14. Very specific:

    Prefer const over let. Use ternaries or early returns instead of reassignment.

    line 71
  15. Very specific:

    Avoid else statements. Prefer early returns.

    line 85
  16. Distinctive:

    Use snake_case for field names so column names don't need to be redefined as strings.

    line 103
  17. Distinctive:

    Avoid mocks as much as possible

    line 123
  18. Distinctive:

    Test actual implementation, do not duplicate logic into tests

    line 124
  19. Very specific:

    Always run bun typecheck from package directories (e.g., packages/opencode), never tsc directly.

    line 129

≈ “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
  • To regenerate the JavaScript SDK, run ./packages/sdk/js/script/build.ts.
  • To rebuild the opencode package, run bun run script/build.ts from packages/opencode. This requires full network access (required_permissions: ["full_network"]).
  • ALWAYS USE PARALLEL TOOLS WHEN APPLICABLE.
  • The default branch in this repo is dev.
  • Local main ref may not exist; use dev or origin/dev for diffs.
  • Prefer automation: execute requested actions without confirmation unless blocked by missing info or safety/irreversibility.

Style Guide

General Principles

  • Keep things in one function unless composable or reusable
  • Avoid try/catch where possible
  • Avoid using the any type
  • Prefer single word variable names where possible
  • Use Bun APIs when possible, like Bun.file()
  • Rely on type inference when possible; avoid explicit type annotations or interfaces unless necessary for exports or clarity
  • Prefer functional array methods (flatMap, filter, map) over for loops; use type guards on filter to maintain type inference downstream

Naming

Prefer single word names for variables and functions. Only use multiple words if necessary.

Naming Enforcement (Read This)

THIS RULE IS MANDATORY FOR AGENT WRITTEN CODE.

  • Use single word names by default for new locals, params, and helper functions.
  • Multi-word names are allowed only when a single word would be unclear or ambiguous.
  • Do not introduce new camelCase compounds when a short single-word alternative is clear.
  • Before finishing edits, review touched lines and shorten newly introduced identifiers where possible.
  • Good short names to prefer: pid, cfg, err, opts, dir, root, child, state, timeout.
  • Examples to avoid unless truly required: inputPID, existingClient, connectTimeout, workerPath.
// Good
const foo = 1
function journal(dir: string) {}

// Bad
const fooBar = 1
function prepareJournal(dir: string) {}

Reduce total variable count by inlining when a value is only used once.

// Good
const journal = await Bun.file(path.join(dir, "journal.json")).json()

// Bad
const journalPath = path.join(dir, "journal.json")
const journal = await Bun.file(journalPath).json()

Destructuring

Avoid unnecessary destructuring. Use dot notation to preserve context.

// Good
obj.a
obj.b

// Bad
const { a, b } = obj

Variables

Prefer const over let. Use ternaries or early returns instead of reassignment.

// Good
const foo = condition ? 1 : 2

// Bad
let foo
if (condition) foo = 1
else foo = 2

Control Flow

Avoid else statements. Prefer early returns.

// Good
function foo() {
  if (condition) return 1
  return 2
}

// Bad
function foo() {
  if (condition) return 1
  else return 2
}

Schema Definitions (Drizzle)

Use snake_case for field names so column names don't need to be redefined as strings.

// Good
const table = sqliteTable("session", {
  id: text().primaryKey(),
  project_id: text().notNull(),
  created_at: integer().notNull(),
})

// Bad
const table = sqliteTable("session", {
  id: text("id").primaryKey(),
  projectID: text("project_id").notNull(),
  createdAt: integer("created_at").notNull(),
})

Testing

  • Avoid mocks as much as possible
  • Test actual implementation, do not duplicate logic into tests
  • Tests cannot run from repo root (guard: do-not-run-tests-from-root); run from package dirs like packages/opencode.

Type Checking

  • Always run bun typecheck from package directories (e.g., packages/opencode), never tsc directly.

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.