agentleFS
The-40-ThievesThe-40-Thieves/obsidian-tc/AGENTS.md

obsidian-tc

AGENTS.md13 starsChanged 5 days agoApache-2.0View on GitHub

Instructions for AI coding agents working in this repository. Issues live in Linear on the The 13th Letter team (THE- prefix), accessed via the Linear MCP server; pull requests live on GitHub and are a delivery surface, not a request surface. See docs/agents/issue-tracker.md. The five canonical triage roles, each label string equal to its name — needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix. See docs/agents/triage-labels.md. Single-context — one CONTEXT.md and one docs/adr/ at the repo root, covering all four workspaces. See docs/agents/domain.md.

  • Pipes a download into a shell
  • 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 33,315 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 repository4 other files it gives its agents.

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Run these before proposing a change:

    line 37
  2. Very specific:

    Read .entire/agent-guide.md for this repository's workflow, source inspection, and verification guidance.

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 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

AGENTS.md

Instructions for AI coding agents working in this repository.

Agent skills

Issue tracker

Issues live in Linear on the The 13th Letter team (THE- prefix), accessed via the Linear MCP server; pull requests live on GitHub and are a delivery surface, not a request surface. See docs/agents/issue-tracker.md.

Triage labels

The five canonical triage roles, each label string equal to its name — needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix. See docs/agents/triage-labels.md.

Domain docs

Single-context — one CONTEXT.md and one docs/adr/ at the repo root, covering all four workspaces. See docs/agents/domain.md.

Cloud agent environment setup

Cloud agent VMs (Google Jules, Codex cloud and similar) do not preinstall Bun. Install the pinned version first; the pin lives in mise.toml and packageManager in package.json, which must agree (currently 1.4.4):

export BUN_INSTALL="$HOME/.bun"   # some VMs can't write the installer's default location
curl -fsSL https://bun.sh/install | bash -s "bun-v1.4.4"
export PATH="$BUN_INSTALL/bin:$PATH"
bun --version   # must print 1.4.4
bun install --frozen-lockfile

Run these before proposing a change:

bun run lint        # biome only
bun run typecheck   # all four packages plus the bun-smoke project
cd packages/server && bunx vitest run test/<touched-area>.test.ts   # targeted tests, not the full suite

The Rust toolchain and the native addon are needed only when a change touches packages/native; the server falls back to JavaScript implementations without the addon. Build it with bun run build in that package. The Rust version is pinned in packages/native/rust-toolchain.toml.

<!-- entire-agent:begin -->

Read .entire/agent-guide.md for this repository's workflow, source inspection, and verification guidance. @.entire/agent-guide.md

<!-- entire-agent:end -->

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.