agentleFS
Sign inStart free
tznctznc/treq/AGENTS.md

treq

AGENTS.md5 starsChanged 19 days agoApache-2.0View on GitHub

Treq is a Tauri v2 Stacking Agent Development Environment (ADE) built on Jujutsu (jj). The whole desktop app is Rust in src-tauri/: GPUI draws every window (src-tauri/src/gpui_shell/), and there is no webview frontend. web/ is the website and supabase/ the hosted services; test/ holds the Supabase-side unit tests. Area guides (read the one for the area you are changing): - src-tauri/AGENTS.md — backend architecture, Rust tests, benchmarks All Rust work must follow TDD. Never write implementation code before the test…

  • Deletes or force-pushes

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. treq-dev/treq★ 5100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

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

The file

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

9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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 npm (not pnpm) for all JS commands

    line 10
  2. Very specific:

    Keep commands/*.rs thin: no business logic there — delegate to core/

    line 11
  3. Very specific:

    Prefer jj-lib or gix over subprocess calls.

    line 12
  4. Distinctive:

    All Rust work must follow TDD.

    line 18
  5. Distinctive:

    Write a failing test that captures the desired behaviour

    line 20
  6. Distinctive:

    Run it — confirm the new test fails (and only the new test)

    line 21
  7. Distinctive:

    Write the minimum code to make it pass

    line 22
  8. Distinctive:

    Run tests — confirm all pass

    line 23
  9. Distinctive:

    Never write implementation code before the test exists.

    line 26

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

Treq Agent Guide

Treq is a Tauri v2 Stacking Agent Development Environment (ADE) built on Jujutsu (jj). The whole desktop app is Rust in src-tauri/: GPUI draws every window (src-tauri/src/gpui_shell/), and there is no webview frontend. web/ is the website and supabase/ the hosted services; test/ holds the Supabase-side unit tests.

Area guides (read the one for the area you are changing):

  • src-tauri/AGENTS.md — backend architecture, Rust tests, benchmarks

Workflow Rules

  • Use npm (not pnpm) for all JS commands
  • Keep commands/*.rs thin: no business logic there — delegate to core/
  • Prefer jj-lib or gix over subprocess calls; never shell out to jj or git from Rust
  • jj.rs functions that accept a workspace path must validate the path exists and return an empty/default value on missing path rather than propagating an IO error
  • GitHub MCP tools: pass minimal_output: true unless you need full fields, and paginate lists 5–10 at a time

TDD (Required)

All Rust work must follow TDD.

  1. Write a failing test that captures the desired behaviour
  2. Run it — confirm the new test fails (and only the new test)
  3. Write the minimum code to make it pass
  4. Run tests — confirm all pass
  5. Refactor while keeping tests green

Never write implementation code before the test exists. For a bug, reproduce it in a test first. Do not add tests for styling-only changes (spacing, color); check those in the running app.

Work typeTest location
Rust core function#[cfg(test)] in the same .rs file, or src-tauri/tests/
GPUI screen or window behaviourthe tests.rs next to it in src-tauri/src/gpui_shell/
Supabase Edge Function logictest/*.test.ts (npm test)
Performance-critical pathsrc-tauri/benches/

Running Tests

cargo test --manifest-path src-tauri/Cargo.toml
npm test                                     # Supabase-side unit tests

Disk space

Rust's incremental cache (target/debug/incremental) grows by gigabytes per build and fills small disks such as cloud sessions. When a build fails with "no space left on device" or df shows the disk nearly full, delete it: rm -rf target/debug/incremental (cargo rebuilds it; the next build is slower). Setting CARGO_INCREMENTAL=0 avoids writing it at all, as CI does. Share one CARGO_TARGET_DIR across git worktrees instead of building each into its own target/.

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