multi-content-type-examples-custom-commands
How to author custom commands for the multi-content-type-examples CLI using the co-generated SDK.
适合你,如果需为 multi-content-type-examples CLI 添加自定义命令
npx oh-my-skill add fern-api/fern/multi-content-type-examples-custom-commandscurl -fsSL https://oh-my-skill.com/install.sh | bash -s -- fern-api/fern/multi-content-type-examples-custom-commandsnpx oh-my-skill verify fern-api/fern/multi-content-type-examples-custom-commands怎么用
商店整理自技能原文 · 版本 aeafcf1 · 表述以原文为准Claude 会指导你为 multi-content-type-examples CLI 编写自定义命令,包括编辑 custom.rs、使用 SDK 客户端、构建和测试。
当你询问如何为 multi-content-type-examples CLI 创建或修改自定义命令时,Claude 会提供步骤。
技能原文 SKILL.md
Custom Commands for multi-content-type-examples
Overview
The multi-content-type-examples CLI supports user-authored custom commands that are compiled into the binary alongside the auto-generated API commands. Custom commands get a fully-wired SDK client that inherits the CLI's auth, retries, TLS, base URL, and global headers — zero configuration required.
Architecture
cli/multi-content-type-examples/custom.rs ← Your command handlers (protected by .fernignore) cli/multi-content-type-examples/sdk.rs ← Generated bridge: client() + block_on() cli/multi-content-type-examples/main.rs ← Generated entrypoint (calls custom::register) multi-content-type-examples-sdk/ ← Co-generated typed SDK crate multi-content-type-examples-types/ ← Co-generated typed model crate
Adding a Custom Command
1. Edit cli/multi-content-type-examples/custom.rs
This file is protected by .fernignore — fern generate will never overwrite it. Register commands in the register() function:
use multi_content_type_examples_sdk::api::*;
pub fn register(app: CliApp) -> CliApp {
let app = app.command(
clap::Command::new("clients-create")
.about("Create client")
,
|matches, ctx| {
let client = super::sdk::client(ctx);
let result = super::sdk::block_on(
client.clients.clients_create(),
)?;
println!("{}", serde_json::to_string_pretty(&result).unwrap());
Ok(())
},
);
app
}
Then build and test:
cargo build multi-content-type-examples clients-create
2. Available SDK Clients
The super::sdk::client(ctx) call returns a multi_content_type_examples_sdk::api::Client with the following sub-clients:
| Field | Type | Description | |-------|------|-------------| | client.clients | multi_content_type_examples_sdk::api::ClientsClient | clients operations |
3. Key Patterns
Get the SDK client (execution-sharing, fully authenticated):
let client = super::sdk::client(ctx);
Run an async SDK call from a sync handler:
let result = super::sdk::block_on(
client.some_resource.some_method(args),
)?;
Use typed models for request/response serialization:
use multi_content_type_examples_sdk::api::*;
Regeneration Safety
| File | Regenerated? | Notes | |------|-------------|-------| | cli/multi-content-type-examples/custom.rs | No | Protected by .fernignore | | cli/multi-content-type-examples/sdk.rs | Yes | Bridges AppContext → SDK client | | cli/multi-content-type-examples/main.rs | Yes | Calls custom::register(app) | | multi-content-type-examples-sdk/ | Yes | Co-generated typed SDK crate | | multi-content-type-examples-types/ | Yes | Co-generated typed models |
After running fern generate, your custom.rs is preserved. All generated code (SDK, types, glue, main.rs) is updated to match the latest API spec. If the SDK surface changes (renamed methods, new sub-clients), update your custom.rs to match.
Build & Test
# Build the CLI (includes custom commands) cargo build # Run your custom command multi-content-type-examples <your-command> [args] # Run with verbose output for debugging RUST_LOG=debug multi-content-type-examples <your-command> [args]