Axum is a Rust workable choice for mobile app. GreatCTO auto-detects both — adds the mobile-app archetype overlay, wires mobile-app-specific gates, and runs 34 specialist agents around your existing Axum workflow.
GreatCTO reads your Cargo.toml and detects axum + mobile-app archetype from signals: imports, file structure, env vars, README hints.
Attaches the mobile-app archetype overlay: IAP receipt validation, App Store / Play Store policy, push token security, privacy nutrition labels. Override if your specifics differ; the defaults are sensible for Axum-style projects.
qa-engineer runs cargo clippy / cargo test / cargo-tarpaulin; security-officer audits unsafe blocks + dependency tree; performance-engineer reviews allocator patterns.
Bugs you've hit before in other Axum projects (connection-pool exhaustion, ORM N+1 queries, retry storms) — the agent's Step 0 includes the prior detection order. MTTR drops 94 % on second occurrence (methodology).
$ cd my-axum-app && npx great-cto init ✓ scanning manifests… found manifest ✓ stack: axum (Rust) ✓ archetype: mobile-app ⚠ archetype + stack combo is unusual — review overlay manually ✓ 34 agents ready $ /start "add in-app purchase verification" ▸ architect drafting ARCH-mobile-app.md… ▸ pm decomposing into beads tasks… ⚐ gate:plan — your approval needed
Approve → 3 senior-devs run in parallel worktrees → 5 reviewers fan out in parallel → gate:ship → deploy. One real run walked stage-by-stage: /proof.
Axum (Rust) is not a typical fit for mobile app. The archetype overlay still attaches, but you may want to override defaults more aggressively. Check the mobile-app archetype page for the typical stack list and decide if your case is the right tool / right archetype.
No black-box "AI does it all" loop. GreatCTO is a deterministic state machine — 8 stages, 22 nodes, 2 human gates. Every node maps to a real agent on GitHub. Inspect the state machine →
$ npx great-cto init
Free, MIT, runs locally. Works in Claude Code, Cursor, OpenAI Codex CLI, Aider, and Continue.