plant-store-custom-commands
How to author custom commands for the plant-store CLI using the co-generated SDK.
适合你,如果你需要为 plant-store 添加自定义 CLI 命令。
npx oh-my-skill add fern-api/fern/plant-store-custom-commandscurl -fsSL https://oh-my-skill.com/install.sh | bash -s -- fern-api/fern/plant-store-custom-commandsnpx oh-my-skill verify fern-api/fern/plant-store-custom-commands怎么用
商店整理自技能原文 · 版本 aeafcf1 · 表述以原文为准Claude 能教你如何在 plant-store CLI 中添加自定义指令,包括注册命令、使用 SDK 客户端、处理认证等。
当你询问如何为 plant-store CLI 编写自定义命令或提及“plant-store”“自定义命令”等关键词时。
技能原文 SKILL.md
Custom Commands for plant-store
Overview
The plant-store 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/plant-store/custom.rs ← Your command handlers (protected by .fernignore) cli/plant-store/sdk.rs ← Generated bridge: client() + block_on() cli/plant-store/main.rs ← Generated entrypoint (calls custom::register) plant-store-sdk/ ← Co-generated typed SDK crate plant-store-types/ ← Co-generated typed model crate
Adding a Custom Command
1. Edit cli/plant-store/custom.rs
This file is protected by .fernignore — fern generate will never overwrite it. Register commands in the register() function:
use plant_store_sdk::api::*;
pub fn register(app: CliApp) -> CliApp {
let app = app.command(
clap::Command::new("get")
.about("Get a plant by ID")
.arg(clap::Arg::new("plantId").required(true))
,
|matches, ctx| {
let plant_id = matches.get_one::<String>("plantId").unwrap();
let client = super::sdk::client(ctx);
let result = super::sdk::block_on(
client.plants.get(plant_id),
)?;
println!("{}", serde_json::to_string_pretty(&result).unwrap());
Ok(())
},
);
app
}
Then build and test:
cargo build plant-store get <plantId>
2. Available SDK Clients
The super::sdk::client(ctx) call returns a plant_store_sdk::api::Client with the following sub-clients:
| Field | Type | Description | |-------|------|-------------| | client.identity | plant_store_sdk::api::IdentityClient | identity operations | | client.plants | plant_store_sdk::api::PlantsClient | plants 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 plant_store_sdk::api::*;
4. Authentication
Custom commands automatically inherit the CLI's authentication. The following auth schemes are configured:
- CustomAuth (oauth-client-credentials): env
PLANT_STORE_CLIENT_ID,PLANT_STORE_CLIENT_SECRET
No manual auth wiring is needed in custom command handlers.
Regeneration Safety
| File | Regenerated? | Notes | |------|-------------|-------| | cli/plant-store/custom.rs | No | Protected by .fernignore | | cli/plant-store/sdk.rs | Yes | Bridges AppContext → SDK client | | cli/plant-store/main.rs | Yes | Calls custom::register(app) | | plant-store-sdk/ | Yes | Co-generated typed SDK crate | | plant-store-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 plant-store <your-command> [args] # Run with verbose output for debugging RUST_LOG=debug plant-store <your-command> [args]