app

Local-first trade for farms and co-ops
git clone https://radroots.dev/git/app.git
Log | Files | Refs | README | LICENSE

AGENTS.md (2395B)

      1 # Rad Roots Application - Agent Specification
      2 
      3 ## 1. Scope and hierarchy
      4 
      5 - This file applies to the full repository.
      6 - Keep this file concise, durable, and repository-specific.
      7 - If a closer directory-level `AGENTS.md` is added later, it overrides this file for that subtree.
      8 
      9 ## 2. Repository identity
     10 
     11 - This repository is the standalone Rad Roots application repository.
     12 - Treat it as a public open-source repository with a direct GPUI-native application focus.
     13 - Preserve the repository's top-level identity files and keep the root easy to understand without mount-path context.
     14 
     15 ## 3. Change discipline
     16 
     17 - Prefer the smallest coherent change that fully addresses the request.
     18 - Do not mix unrelated cleanup or speculative refactors into the same change.
     19 - Remove obsolete code and scaffolding when they are clearly replaced.
     20 
     21 ## 4. Before editing
     22 
     23 Before making substantial changes:
     24 
     25 - Read this file, `README.md`, and `CONTRIBUTING.md`.
     26 - Inspect `git status --short` before broad edits, refactors, or file removals.
     27 - Read the current implementation before changing behavior.
     28 - Use checked-in commands and docs as the source of truth.
     29 
     30 ## 5. Validation and command surface
     31 
     32 - Run validation from the repository root.
     33 - Prefer the narrowest relevant validation first.
     34 - Use documented commands before inventing new ones.
     35 - Current canonical commands are:
     36   - `cargo metadata --format-version 1 --no-deps`
     37   - `cargo check -p radroots_app`
     38   - `cargo test`
     39   - `cargo run -p radroots_app`
     40   - `./scripts/check.sh`
     41   - `./scripts/run.sh`
     42 
     43 ## 6. Repository structure
     44 
     45 - Keep the repository root as the package root.
     46 - Keep the structure minimal until a durable new boundary is required.
     47 - Do not reintroduce deprecated egui-era scaffolding.
     48 
     49 ## 7. Rust engineering rules
     50 
     51 - Use Rust `1.92.0`, edition `2024`, and safe Rust only.
     52 - Keep state, data flow, and side effects explicit.
     53 - Avoid hidden panics in non-test code.
     54 - Keep code readable and direct.
     55 
     56 ## 8. Commit and handoff rules
     57 
     58 - Format commits as `<scope>: <imperative summary>`.
     59 - Use lowercase scopes.
     60 - Keep handoff summaries clear and standalone.
     61 - In handoff, state what changed, what validation ran, and any remaining risks or assumptions.
     62 
     63 ## 9. Definition of done
     64 
     65 - The requested change is implemented.
     66 - Obsolete scaffolding is removed when clearly replaced.
     67 - Relevant validation ran, or a concrete blocker is reported.