Skip to content

hashgraph-online/awesome-codex-plugins / plugins/alpoxdev/hypercore/skills/hyper-architecture

hyper-architecture

Verified

[Hyper] Use this skill when the user asks for architecture, project setup, or performance work - building, auditing, restructuring, or reviewing project structure, routes, data or server boundaries, the lint/format/type tooling baseline (oxlint, Prettier, tsconfig, rustfmt, clippy), or build and runtime performance - in a Next.js App Router, TanStack Start, Vite with TanStack Router, Astro, Expo, Lynx (ReactLynx), Hono, Axum, Tauri v2, Electron, or Rust CLI, WASM, or MCP server project. It detects the stack from manifests and config files, routes each touched package of a monorepo separately, and applies the matching bundled stack guide, the shared setup baseline, and that stack's performance rules. Do not use it for stacks outside those eleven or for work that crosses no architecture, setup, or performance boundary, such as copy edits, a plain dependency bump, or one build failure.

FileKindSize
SKILL.ko.mdmarkdown19.9 KB
SKILL.mdskill md18.4 KB
assets/evals/astro-cases.jsonlother17.1 KB
assets/evals/axum-cases.jsonlother13.7 KB
assets/evals/electron-cases.jsonlother14.6 KB
assets/evals/expo-cases.jsonlother18.3 KB
assets/evals/hono-cases.jsonlother22.2 KB
assets/evals/hyper-architecture-cases.jsonlother26.0 KB
assets/evals/lynx-cases.jsonlother17.9 KB
assets/evals/nextjs-cases.jsonlother21.5 KB
assets/evals/rust-cases.jsonlother17.8 KB
assets/evals/tanstack-start-cases.jsonlother21.0 KB
assets/evals/tauri-cases.jsonlother18.6 KB
assets/evals/vite-cases.jsonlother18.6 KB
assets/templates/setup/repo/editorconfigother357 B
assets/templates/setup/repo/gitattributesother714 B
assets/templates/setup/repo/lefthook.ymlconfig843 B
assets/templates/setup/rust/clippy.tomlconfig110 B
assets/templates/setup/rust/rust-toolchain.tomlconfig86 B
assets/templates/setup/rust/rustfmt.tomlconfig200 B
assets/templates/setup/rust/workspace-lints.tomlconfig809 B
assets/templates/setup/typescript/oxlintrc.jsonconfig929 B
assets/templates/setup/typescript/oxlintrc.react.jsonconfig1.1 KB
assets/templates/setup/typescript/prettierignoreother316 B
assets/templates/setup/typescript/prettierrc.jsonconfig263 B
assets/templates/setup/typescript/tsconfig.base.jsonconfig551 B
references/official/astro/astro-2026-11-07.ko.mdmarkdown18.6 KB
references/official/astro/astro-2026-11-07.mdmarkdown17.0 KB
references/official/axum/axum-docs.ko.mdmarkdown5.7 KB
references/official/axum/axum-docs.mdmarkdown4.8 KB
references/official/axum/ecosystem-docs.ko.mdmarkdown3.8 KB
references/official/axum/ecosystem-docs.mdmarkdown3.5 KB
references/official/axum/sqlx-docs.ko.mdmarkdown5.5 KB
references/official/axum/sqlx-docs.mdmarkdown4.7 KB
references/official/axum/tower-docs.ko.mdmarkdown4.2 KB
references/official/axum/tower-docs.mdmarkdown3.7 KB
references/official/axum/utoipa-docs.ko.mdmarkdown4.1 KB
references/official/axum/utoipa-docs.mdmarkdown3.7 KB
references/official/electron/electron-2026-11-08.ko.mdmarkdown15.7 KB
references/official/electron/electron-2026-11-08.mdmarkdown14.1 KB
references/official/expo/expo-react-native-2026-11-04.ko.mdmarkdown23.0 KB
references/official/expo/expo-react-native-2026-11-04.mdmarkdown21.5 KB
references/official/hono/drizzle-docs.ko.mdmarkdown7.0 KB
references/official/hono/drizzle-docs.mdmarkdown6.6 KB
references/official/hono/hono-docs.ko.mdmarkdown15.8 KB
references/official/hono/hono-docs.mdmarkdown14.8 KB
references/official/lynx/lynx-2026-11-07.ko.mdmarkdown14.3 KB
references/official/lynx/lynx-2026-11-07.mdmarkdown14.0 KB
references/official/nextjs/current-docs-2026-11-04.ko.mdmarkdown13.1 KB
references/official/nextjs/current-docs-2026-11-04.mdmarkdown12.0 KB
references/official/nextjs/drizzle-docs.ko.mdmarkdown6.7 KB
references/official/nextjs/drizzle-docs.mdmarkdown6.3 KB
references/official/nextjs/nextjs-docs.ko.mdmarkdown13.6 KB
references/official/nextjs/nextjs-docs.mdmarkdown13.9 KB
references/official/rust/rust-crates-2026-11-07.ko.mdmarkdown22.6 KB
references/official/rust/rust-crates-2026-11-07.mdmarkdown22.0 KB
references/official/tanstack-start/current-docs-2026-11-04.ko.mdmarkdown16.0 KB
references/official/tanstack-start/current-docs-2026-11-04.mdmarkdown14.7 KB
references/official/tanstack-start/tanstack-router-2026-11-04.ko.mdmarkdown10.5 KB
references/official/tanstack-start/tanstack-router-2026-11-04.mdmarkdown9.6 KB
references/official/tanstack-start/tanstack-start-2026-11-04.ko.mdmarkdown25.8 KB
references/official/tanstack-start/tanstack-start-2026-11-04.mdmarkdown23.9 KB
references/official/tauri/tanstack-vite-react-2026-11-04.ko.mdmarkdown14.1 KB
references/official/tauri/tanstack-vite-react-2026-11-04.mdmarkdown13.1 KB
references/official/tauri/tauri-v2-2026-11-04.ko.mdmarkdown18.5 KB
references/official/tauri/tauri-v2-2026-11-04.mdmarkdown17.6 KB
references/official/tooling/tooling-2026-11-07.ko.mdmarkdown21.0 KB
references/official/tooling/tooling-2026-11-07.mdmarkdown20.5 KB
references/official/vite/current-docs-2026-11-04.ko.mdmarkdown11.2 KB
references/official/vite/current-docs-2026-11-04.mdmarkdown10.3 KB
rules/astro/actions-middleware-env.ko.mdmarkdown14.6 KB
rules/astro/actions-middleware-env.mdmarkdown12.9 KB
rules/astro/content.ko.mdmarkdown8.1 KB
rules/astro/content.mdmarkdown7.3 KB
rules/astro/performance.ko.mdmarkdown11.3 KB
rules/astro/performance.mdmarkdown10.0 KB
rules/astro/project-structure.ko.mdmarkdown11.2 KB
rules/astro/project-structure.mdmarkdown9.6 KB
rules/astro/rendering-and-islands.ko.mdmarkdown10.2 KB
rules/astro/rendering-and-islands.mdmarkdown8.7 KB
rules/astro/testing.ko.mdmarkdown10.4 KB
rules/astro/testing.mdmarkdown9.4 KB
rules/axum/conventions.ko.mdmarkdown5.3 KB
rules/axum/conventions.mdmarkdown4.8 KB
rules/axum/database.ko.mdmarkdown11.9 KB
rules/axum/database.mdmarkdown10.2 KB
rules/axum/errors.ko.mdmarkdown6.5 KB
rules/axum/errors.mdmarkdown6.0 KB
rules/axum/handlers.ko.mdmarkdown5.6 KB
rules/axum/handlers.mdmarkdown5.0 KB
rules/axum/middleware.ko.mdmarkdown5.4 KB
rules/axum/middleware.mdmarkdown4.9 KB
rules/axum/openapi.ko.mdmarkdown9.5 KB
rules/axum/openapi.mdmarkdown8.3 KB
rules/axum/performance.ko.mdmarkdown9.6 KB
rules/axum/performance.mdmarkdown8.6 KB
rules/axum/platform.ko.mdmarkdown6.9 KB
rules/axum/platform.mdmarkdown6.3 KB
rules/axum/project-structure.ko.mdmarkdown10.8 KB
rules/axum/project-structure.mdmarkdown9.9 KB
rules/axum/routes.ko.mdmarkdown7.3 KB
rules/axum/routes.mdmarkdown6.3 KB
rules/axum/testing.ko.mdmarkdown5.2 KB
rules/axum/testing.mdmarkdown4.6 KB
rules/axum/validation.ko.mdmarkdown4.8 KB
rules/axum/validation.mdmarkdown4.4 KB
rules/electron/packaging.ko.mdmarkdown7.9 KB
rules/electron/packaging.mdmarkdown7.0 KB
rules/electron/performance.ko.mdmarkdown5.8 KB
rules/electron/performance.mdmarkdown5.0 KB
rules/electron/processes-and-ipc.ko.mdmarkdown10.6 KB
rules/electron/processes-and-ipc.mdmarkdown9.7 KB
rules/electron/project-structure.ko.mdmarkdown8.8 KB
rules/electron/project-structure.mdmarkdown8.1 KB
rules/electron/renderer.ko.mdmarkdown10.8 KB
rules/electron/renderer.mdmarkdown9.8 KB
rules/electron/security.ko.mdmarkdown10.3 KB
rules/electron/security.mdmarkdown9.2 KB
rules/electron/testing.ko.mdmarkdown5.7 KB
rules/electron/testing.mdmarkdown5.0 KB
rules/expo/data-state-and-boundaries.ko.mdmarkdown4.7 KB
rules/expo/data-state-and-boundaries.mdmarkdown4.3 KB
rules/expo/native-platform-and-security.ko.mdmarkdown8.2 KB
rules/expo/native-platform-and-security.mdmarkdown7.5 KB
rules/expo/performance.ko.mdmarkdown11.2 KB
rules/expo/performance.mdmarkdown10.1 KB
rules/expo/project-structure.ko.mdmarkdown13.4 KB
rules/expo/project-structure.mdmarkdown13.2 KB
rules/expo/routing-and-navigation.ko.mdmarkdown8.6 KB
rules/expo/routing-and-navigation.mdmarkdown8.0 KB
rules/expo/testing-and-validation.ko.mdmarkdown5.1 KB
rules/expo/testing-and-validation.mdmarkdown4.8 KB
rules/hono/conventions.ko.mdmarkdown3.7 KB
rules/hono/conventions.mdmarkdown3.5 KB
rules/hono/database.ko.mdmarkdown11.7 KB
rules/hono/database.mdmarkdown10.8 KB
rules/hono/errors.ko.mdmarkdown3.9 KB
rules/hono/errors.mdmarkdown3.7 KB
rules/hono/handlers.ko.mdmarkdown2.5 KB
rules/hono/handlers.mdmarkdown2.2 KB
rules/hono/middleware.ko.mdmarkdown3.3 KB
rules/hono/middleware.mdmarkdown3.0 KB
rules/hono/openapi.ko.mdmarkdown11.7 KB
rules/hono/openapi.mdmarkdown10.9 KB
rules/hono/performance.ko.mdmarkdown8.9 KB
rules/hono/performance.mdmarkdown8.0 KB
rules/hono/platform.ko.mdmarkdown5.0 KB
rules/hono/platform.mdmarkdown4.7 KB
rules/hono/project-structure.ko.mdmarkdown10.4 KB
rules/hono/project-structure.mdmarkdown9.9 KB
rules/hono/routes.ko.mdmarkdown6.9 KB
rules/hono/routes.mdmarkdown6.6 KB
rules/hono/testing-rpc.ko.mdmarkdown5.6 KB
rules/hono/testing-rpc.mdmarkdown5.2 KB
rules/hono/validation.ko.mdmarkdown3.7 KB
rules/hono/validation.mdmarkdown3.5 KB
rules/lynx/native-and-platform.ko.mdmarkdown11.4 KB
rules/lynx/native-and-platform.mdmarkdown10.7 KB
rules/lynx/performance.ko.mdmarkdown11.6 KB
rules/lynx/performance.mdmarkdown10.6 KB
rules/lynx/project-structure.ko.mdmarkdown10.2 KB
rules/lynx/project-structure.mdmarkdown9.6 KB
rules/lynx/testing.ko.mdmarkdown7.0 KB
rules/lynx/testing.mdmarkdown6.4 KB
rules/lynx/threading.ko.mdmarkdown13.0 KB
rules/lynx/threading.mdmarkdown12.0 KB
rules/lynx/ui-and-data.ko.mdmarkdown11.8 KB
rules/lynx/ui-and-data.mdmarkdown10.8 KB
rules/nextjs/data-fetching.ko.mdmarkdown9.9 KB
rules/nextjs/data-fetching.mdmarkdown9.3 KB
rules/nextjs/db.ko.mdmarkdown8.1 KB
rules/nextjs/db.mdmarkdown7.3 KB
rules/nextjs/execution-model.ko.mdmarkdown5.0 KB
rules/nextjs/execution-model.mdmarkdown4.5 KB
rules/nextjs/hooks.ko.mdmarkdown5.8 KB
rules/nextjs/hooks.mdmarkdown5.3 KB
rules/nextjs/performance.ko.mdmarkdown12.5 KB
rules/nextjs/performance.mdmarkdown11.2 KB
rules/nextjs/platform.ko.mdmarkdown7.7 KB
rules/nextjs/platform.mdmarkdown7.0 KB
rules/nextjs/project-structure.ko.mdmarkdown9.4 KB
rules/nextjs/project-structure.mdmarkdown9.0 KB
rules/nextjs/route-handlers.ko.mdmarkdown4.7 KB
rules/nextjs/route-handlers.mdmarkdown4.3 KB
rules/nextjs/routes.ko.mdmarkdown5.0 KB
rules/nextjs/routes.mdmarkdown4.6 KB
rules/nextjs/server-actions.ko.mdmarkdown7.1 KB
rules/nextjs/server-actions.mdmarkdown6.4 KB
rules/nextjs/services.ko.mdmarkdown5.8 KB
rules/nextjs/services.mdmarkdown5.5 KB
rules/nextjs/validation.ko.mdmarkdown2.2 KB
rules/nextjs/validation.mdmarkdown2.3 KB
rules/rust/cli.ko.mdmarkdown13.6 KB
rules/rust/cli.mdmarkdown12.0 KB
rules/rust/crate-layout.ko.mdmarkdown11.4 KB
rules/rust/crate-layout.mdmarkdown10.1 KB
rules/rust/errors-and-logging.ko.mdmarkdown13.0 KB
rules/rust/errors-and-logging.mdmarkdown11.6 KB
rules/rust/mcp-server.ko.mdmarkdown15.2 KB
rules/rust/mcp-server.mdmarkdown13.8 KB

rules/rust/errors-and-logging.md

View on GitHub
# Errors and Logging

> Put a `thiserror` enum at every library boundary, `anyhow` at the application boundary, one exit-code mapping at the top, and a `tracing` subscriber that writes diagnostics to stderr.

Rules here are `official` when an opened page in `references/official/rust/rust-crates-2026-11-07.md` states them and `hypercore-default` when this package chose the default.

## 1. Two error libraries, two jobs

`official` — `anyhow` is the application error type: its docs describe `anyhow::Result<T>` for code that reports a failure to a human, and state that it "does not bundle a `derive(Error)` macro" (https://docs.rs/anyhow/latest/anyhow/). `thiserror` derives `std::error::Error` and its docs say it "deliberately does not appear in your public API" (https://docs.rs/thiserror/latest/thiserror/).

`hypercore-default` — The split this package uses:

| Layer | Type | Why |
|---|---|---|
| Library crate public API | `thiserror` enum | Callers can match on variants; the error is part of the contract |
| Binary `run()` and commands | `anyhow::Result` | Context is added at the point of failure; the type is not public |
| Domain functions | `thiserror` enum or a plain `Result<T, DomainError>` | Domain failures are exhaustively matchable |
| WASM exported function | `Result<T, JsValue>` at the boundary, typed error inside | The JavaScript boundary cannot carry a Rust enum |
| MCP tool handler | `Result<CallToolResult, McpError>` from the SDK | The SDK owns the protocol error shape |

`official` — Mixing the two is supported at one defined seam: a `thiserror` variant with `#[error(transparent)]` wrapping `anyhow::Error` delegates `Display` and `source` (https://docs.rs/thiserror/latest/thiserror/). Use it exactly once, in the application layer, when a library error must travel up through a command.

`hypercore-default` — Never place `anyhow::Error` in a public function signature of a library crate. A caller cannot match it, and every future variant becomes a surprise.

## 2. Context, not decoration

`hypercore-default` — Add context where the information exists and cannot be reconstructed later:

```rust
let text = std::fs::read_to_string(&path)
    .with_context(|| format!("reading config {}", path.display()))?;
```

- One `.context(...)` per fallible boundary crossing; not one per line.
- The context names the resource, not the function: `"reading config /etc/app.toml"` beats `"failed in load"`.
- Do not wrap an error whose message already names the resource; nested duplicates read as noise.
- `anyhow`'s backtrace is captured on Rust ≥ 1.65 and shown through `RUST_BACKTRACE` or `RUST_LIB_BACKTRACE` (https://docs.rs/anyhow/latest/anyhow/). Do not print a backtrace by hand.

`official` — `unwrap()` and `expect()` panic. A panic in a binary exits 101; in a WASM module it aborts the instance; in a server it takes down the task. Reserve them for invariants the type system cannot express, and state the invariant in the message.

## 3. Exit codes

`official` — Codes 0–255 are portable, and "Rust sets an exit code of `101` when the process panicked" (https://rust-cli.github.io/book/in-depth/exit-code.html). The book points at BSD `sysexits` — `exitcode::USAGE`, `CONFIG`, `DATAERR`, `NOINPUT`, `IOERR`, and the rest — as the vocabulary for distinct failure classes.

`official` — clap already owns parse failures: `Error::exit` "either prints to `stderr` and exits with a status of `2` or prints to `stdout` and exits with a status of `0`", and `exit_code()` returns 2 exactly when the error kind writes to stderr (https://docs.rs/clap/latest/clap/error/struct.Error.html). `--help` and `--version` therefore exit 0 on stdout; a bad flag exits 2 on stderr before the program's own code runs.

`hypercore-default` — The policy:

| Outcome | Code | Owner |
|---|---|---|
| Success | 0 | `ExitCode::SUCCESS` |
| Help or version requested | 0 | clap |
| Argument parse failure | 2 | clap, untouched |
| Usage error the parser cannot detect | `exitcode::USAGE` (64) | the binary |
| Configuration or input data invalid | `exitcode::CONFIG`/`DATAERR` | the binary |
| Environment or I/O failure | `exitcode::IOERR` | the binary |
| Panic | 101 | Rust, not written by hand |

```rust
fn main() -> std::process::ExitCode {
    let cli = Cli::parse();               // clap handles help/version/parse errors
    init_tracing(cli.verbose, cli.quiet);
    match app::run(cli) {
        Ok(()) => std::process::ExitCode::SUCCESS,
        Err(err) => {
            tracing::error!("{err:#}");
            std::process::ExitCode::from(exitcode_for(&err))
        }
    }
}
```

- Return `ExitCode` from `main` instead of calling `process::exit` inside a code path, so destructors and buffered writers finish.
- Map error classes to codes in exactly one function. Two mapping sites drift.
- `exitcode` is the book's recommendation, but its current version and maintenance state were not verified for this snapshot; if the crate is not already a dependency, plain constants with the same values are acceptable and the rationale is recorded.
- A WASM module and an MCP server have no exit code to set: a WASM export returns a `Result` to JavaScript, and an MCP server reports failures through the protocol.

## 4. Logging

`official` — `tracing` events replace `println!` for anything that is not the program's deliverable. `tracing-subscriber`'s defaults are `ansi`, `fmt`, `smallvec`, `std`, and `tracing-log`; `env-filter` is not among them, so `EnvFilter` requires an explicit feature (https://docs.rs/tracing-subscriber/latest/tracing_subscriber/).

```toml
[dependencies.tracing-subscriber]
version = "0.3"
features = ["env-filter"]
```

`official` — `EnvFilter::DEFAULT_ENV` is `RUST_LOG`, and `from_default_env()` adds "a default directive enabling the ERROR level" when the variable is empty or unset (https://docs.rs/tracing-subscriber/latest/tracing_subscriber/). So an unconfigured run is quiet rather than verbose, which is the behavior a CLI wants.

`official` — The CLI book's guidance on human-facing logs: `info` as the default level, consistent prefixes so `grep` works, and user-selectable verbosity through `--verbose` or `RUST_LOG` (https://rust-cli.github.io/book/in-depth/human-communication.html).

`hypercore-default` — The setup:

```rust
use tracing_subscriber::{fmt, EnvFilter};

pub fn init(verbose: u8, quiet: bool) {
    let default = match (verbose, quiet) {
        (_, true) => "error",
        (0, _) => "warn",
        (1, _) => "info",
        (2, _) => "debug",
        _ => "trace",
    };
    let filter = EnvFilter::try_from_default_env()
        .unwrap_or_else(|_| EnvFilter::new(default));
    fmt()
        .with_env_filter(filter)
        .with_writer(std::io::stderr)     // stdout stays the deliverable
        .without_time()                   // a CLI log line rarely needs a timestamp
        .init();
}
```

- Explicit flags beat an ambient variable: if `--verbose` is passed, it must win over `RUST_LOG`, or the flag is a lie.
- `.with_writer(std::io::stderr)` is structural, not a convention someone remembers. On a stdio MCP server it is a protocol requirement, not a style choice.
- One subscriber, initialized once, at the process edge. A library never calls `.init()`; a second call panics.
- `tracing::instrument` on command and domain functions when the arguments are cheap to render and the span adds real context; skip it on hot loops and on anything that would log secrets.

## 5. stdout versus stderr

`official` — `std::io::IsTerminal` is the standard way to tell a human from a pipe (https://rust-cli.github.io/book/in-depth/machine-communication.html). The book's rule for machine output is one JSON document per message — line-delimited JSON — and its example is ripgrep's `--json` stream where every record carries a `type` field (`begin`, `match`, `end`, `summary`).

`hypercore-default` — Route table:

| Output kind | Stream | Condition |
|---|---|---|
| Primary result for a human | stdout | always |
| Primary result for a machine | stdout | `--json` given, or stdout is not a terminal |
| Progress, spinners, "wrote 3 files" | stderr | always |
| Warnings and errors | stderr | always |
| MCP protocol frames | stdout | stdio transport only, nothing else |
| Debug and diagnostics | stderr | through `tracing` |

- A `--quiet` flag suppresses progress and warnings, never errors and never the deliverable.
- Never interleave a progress line into a `--json` stream; a consumer parsing line by line will fail on the first human sentence.
- When output is a terminal, a progress indicator may use ANSI; when it is not, it prints nothing. `anstream`'s `AutoStream` adapts ANSI to the terminal's capability, and clap already disables color on a non-TTY (https://docs.rs/anstream/latest/anstream/).

## 6. Never leak

`hypercore-default` — An error message shown to a user names the file, the resource, or the operation. It does not include:

- Credentials, tokens, connection strings, or full environment dumps.
- Internal paths that reveal a deployment layout, when the tool runs as a service.
- A stack trace, unless `RUST_BACKTRACE` was set by the operator deliberately.

Log the detailed cause at `error` or `debug` level on stderr, and return the short message to the caller. For a WASM module the same rule applies: the detail goes to `console.error`, the returned `Result` carries a short message.

## Checklist

- [ ] A `thiserror` enum backs every library public error; `anyhow` never appears in a public signature.
- [ ] `anyhow::Result` is used only from the application layer inward to `run`.
- [ ] At most one `#[error(transparent)]` seam mixes the two, and it is in the application layer.
- [ ] Each fallible boundary crossing adds one `.context(...)` naming the resource.
- [ ] `main` returns `ExitCode` and no code path calls `process::exit`.
- [ ] One function maps error classes to exit codes; 0, 2, and 101 keep their meanings.
- [ ] clap's `Error` is not reformatted or re-exited by hand.
- [ ] `tracing-subscriber` enables `env-filter` wherever `EnvFilter` is constructed.
- [ ] The subscriber is initialized once, at the process edge, and writes to stderr.
- [ ] An explicit verbosity flag beats `RUST_LOG`.
- [ ] stdout carries only the deliverable, or protocol frames when the target is a stdio MCP server.
- [ ] `--quiet` suppresses progress and warnings but never errors or the deliverable.
- [ ] Error messages contain no credentials, tokens, or internal paths.

## Sources

> Checked 2026-11-07. Facts come from the pages recorded in `references/official/rust/rust-crates-2026-11-07.md`.

| Claim | Source |
|---|---|
| `anyhow` is the application error type and has no derive macro; backtraces through `RUST_BACKTRACE` | https://docs.rs/anyhow/latest/anyhow/ |
| `thiserror` derives `std::error::Error`, stays out of the public API, and supports `#[error(transparent)]` | https://docs.rs/thiserror/latest/thiserror/ |
| Exit codes 0–255, panic code 101, and the `exitcode` recommendation | https://rust-cli.github.io/book/in-depth/exit-code.html |
| clap maps help/version to stdout+0 and errors to stderr+2 | https://docs.rs/clap/latest/clap/error/struct.Error.html |
| `env-filter` is not a default feature; `RUST_LOG` default directive is ERROR | https://docs.rs/tracing-subscriber/latest/tracing_subscriber/ |
| `info` default level, consistent prefixes, `--verbose` or `RUST_LOG` | https://rust-cli.github.io/book/in-depth/human-communication.html |
| `IsTerminal`, line-delimited JSON, and ripgrep's `type`-tagged records | https://rust-cli.github.io/book/in-depth/machine-communication.html |
| `anstream` `AutoStream` adapts ANSI to terminal capability | https://docs.rs/anstream/latest/anstream/ |
| Exit-code table, subscriber setup, and the stream routing table above | this package's convention, not an official Rust requirement |
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall