aomi

Use when integrating Aomi one-shot agent deploy into a host app or site — a partner platform (launchpad, portal, marketplace) that wants users to spin up a live Aomi agent and chat with it. Covers the `@aomi-labs/deploy` toolkit: mount the server-side BFF route factories (`/bff`), wire the browser client (`/launch`), supply credentials, and build a deploy UI in your own stack against the typed client. The stable product is the client contract, not a UI component — build the UI your product needs.

Run and interpret `./scripts/repowiki` commands for an Aomi repository that contains `repowiki.toml`. Use when the user writes `/repowiki ...`, asks to pass arguments through to the repowiki CLI, wants a repowiki subcommand run with minor typo correction, or wants repowiki output explained in plain language.

Use when the user wants to build, scaffold, or update an Aomi app/plugin from API docs, OpenAPI or Swagger specs, SDK docs, repository examples, endpoint notes, runtime interfaces, or product requirements. Converts specs into Aomi SDK crates with `lib.rs`, `client.rs`, and `tool.rs`, plus tool schemas, preambles, host-interop flows, and validation steps. Prefer real product integrations over docs-only helpers whenever a callable surface exists.

Drive the Aomi CLI to chat with the Aomi agent, inspect sessions, simulate pending wallet requests on a forked chain, and sign queued transactions or EIP-712 payloads with account-abstraction-first execution. MUST NOT fabricate, guess, echo, or log credential values on the skill's own initiative; credential values may pass to the CLI only when the user has explicitly supplied them for a specific setup step they asked for.