Skip to main content
Generate a browser SDK module from the controllers of a target module. The command scaffolds a dedicated SDK module, emits one source file per backend module with typed api method stubs and definition metadata, and installs the runtime dependencies the generated files import.

​
Usage

ooneex sdk:create [options]

​
Examples

ooneex sdk:create

ooneex sdk:create --name=storefront --module=app

ooneex sdk:create --name=billing --module=billing

​
Options

OptionDescriptionDefault
--nameSDK module name. Normalized to kebab-case; a trailing Module is stripped.sdk
--moduleTarget module the SDK is generated from. An api target aggregates every backend module and api module; a microservice target exposes only its own controllers.app
--cwdWorking directory the command runs in.Current directory
--silentSuppress spinners and the success message.false
The generated module is marked type: "sdk" in its <name>.yml, is named @<root-package-scope>/<name>, and is kept out of AppModule and SharedModule.

​
AI Skill

This command ships a matching sdk:create skill. It guides generating the SDK module from a target module and then completing the work the generator leaves: replacing the <prefix> placeholder in each endpoint, adding a shared endpoint builder, and filling in the api method bodies. The skill covers HTTP methods via @ooneex/fetcher, server-side streaming and Server-Sent Events via native fetch with a body reader, and WebSocket methods via @ooneex/socket-client, including how to forward bearer tokens on authenticated routes. 
ooneex claude:init