Report · marked 27 Aug 2026

DioxusLabs/dioxus

Solid foundations, held back in a few specific places.

Rust · 38,894 stars · 1,518 files · branch main

78 /100 A-

Instructions 22/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality and readme as an entry point.Setup 8/16Whether an agent can install the project and get it running without a human. Losing marks on discoverable commands and pinned runtime version.Verification loop 19/22Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on lint and format rules.Context economy 17/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context and repository weight.Navigability 8/10How quickly anything new can orient itself. Losing marks on written documentation.

Higher is better. Accent marks what is costing you most.

Fix these first

Discoverable commands

Declare the handful of commands that matter in package.json scripts, a Makefile, or a justfile. Naming them turns guesswork into a lookup.

Instruction quality

Worth fixing: it never states a build, test, or run command.

Lint and format rules

A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.

The full marking

Every deduction below names the file or setting it came from.

Instructions 22/27 A-

Whether the repo tells an agent how to behave before it starts guessing.

✓Agent instruction file 12/12

AGENTS.md is present, which is the format the most tools read.

✗Instruction quality 8/12

Real instructions, with gaps.

Worth fixing: it never states a build, test, or run command.

3,830 characters, a workable length

uses headings, so an agent can skim it

includes copyable code blocks

✗README as an entry point 2/3

README exists but never explains how to get the thing running.

Give the README an Install and a Usage heading with real commands under each. Agents pattern-match on those headings.

Setup 8/16 C+

Whether an agent can install the project and get it running without a human.

✓Deterministic install 6/6

cargo.lock pins the dependency tree.

Found cargo.lock

✗Discoverable commands 0/6

No declared commands. An agent has to infer how to build and run this from the file tree.

Declare the handful of commands that matter in package.json scripts, a Makefile, or a justfile. Naming them turns guesswork into a lookup.

–Environment config n/a

Not applicable — this reads as a library, with no environment to configure.

✗Pinned runtime version 0/2

No pinned runtime version.

Add a .nvmrc, .python-version, or equivalent so the agent's toolchain matches yours.

✓Reproducible environment 2/2

.devcontainer/devcontainer.json gives a known-good environment.

Verification loop 19/22 A

Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.

✓Tests exist 8/8

242 test files against 945 source files.

e.g. examples/01-app-demos/geolocation-native-plugin/src/ios/plugin/Tests/PluginTests/PluginTests.swift, packages/autofmt/tests/error_handling.rs, packages/autofmt/tests/partials/no_parse.rsx

✓Test command is discoverable 7/7

An agent can find and run `cargo test`.

✓Continuous integration 4/4

2 GitHub Actions workflows define what "passing" means.

✗Lint and format rules 0/3

No linter or formatter config. Style is tribal knowledge, so agent output will drift from yours.

A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.

–Static type checking n/a

Not applicable — the Rust compiler type checks every build.

Context economy 17/20 A

Whether the repo fits in a context window, or fights it.

✓No committed build output 6/6

No generated directories committed.

✓.gitignore hygiene 3/3

.gitignore covers 33 patterns.

✗File sizes fit in context 4/6

2 source files are over 100KB.

A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.

packages/fuzz/src/harness.rs — 135KB

packages/cli/src/serve/runner.rs — 116KB

✗Repository weight 4/5

About 55.5MB checked out, which is comfortable.

Here is your AGENTS.md

Drafted from what is actually in this repository: the install command from your lockfile, the commands you already declare, your real directory layout. Anything marked TODO needs a person. Save it at the root as AGENTS.md.

AGENTS.md — drafted for DioxusLabs/dioxus

# AGENTS.md

Fullstack app framework for web, desktop, and mobile.

## Setup

```
cargo build
```

## Commands

```
cargo test   # run the test suite
```

## Layout

- `packages/` 787 source files
- `examples/` 157 source files

## Conventions

- Tests live alongside the code they cover, following `examples/01-app-demos/geolocation-native-plugin/src/ios/plugin/Tests/PluginTests/PluginTests.swift`.
- CI defines what passing means. See `.github/workflows/main.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

## Gotchas

- `packages/fuzz/src/harness.rs` is 135KB. It will not fit comfortably in context, so read it in parts.

---

Drafted by agentreadme.com from what is in this repository. Everything marked TODO
needs a human. Check it in as AGENTS.md at the root.

Open the raw markdown or curl -o AGENTS.md agentreadme.com/draft/DioxusLabs/dioxus.md

Show the mark

The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.

[![agent ready](https://agentreadme.com/badge/DioxusLabs/dioxus.svg)](https://agentreadme.com/DioxusLabs/dioxus)

Other Rust repositories, marked

ultraworkers/claw-code 71 B+ farion1231/cc-switch 63 B rustdesk/rustdesk 70 B+ openai/codex 82 A- rust-lang/rust 65 B tauri-apps/tauri 64 B

All Rust repositories

Think this mark is wrong?

Every deduction above names the file it came from, so this can be settled by looking. If a check missed something, that is a rule worth fixing.

Open an issue, already filled in