10 files changed, 45 insertions, 33 deletions
diff --git a/docs/pages/11-resource-system.md b/docs/pages/11-resource-system.md
index bc2197f..9491212 100644
--- a/docs/pages/11-resource-system.md
+++ b/docs/pages/11-resource-system.md
@@ -57,7 +57,7 @@ Use `&mut T` to inject a mutable resource:
 #[chain]
 fn handle_visit(_args: EntryVisit, counter: &mut ResVisitCount) -> Next {
     counter.0 += 1;
-    ResultDone::default()
+    ResultDone::default().into()
 }
  
 #[renderer]
diff --git a/docs/pages/3-define-a-chain.md b/docs/pages/3-define-a-chain.md
index c6d3f8e..450522b 100644
--- a/docs/pages/3-define-a-chain.md
+++ b/docs/pages/3-define-a-chain.md
@@ -24,7 +24,7 @@ fn handle_greet(args: EntryGreet) -> Next {
     // args contains the remaining params after matching user input
     let name = args.inner.first().cloned().unwrap_or_else(|| "World".to_string());
     // Wrap the result into Next, telling the dispatcher where to go next
-    ResultName::new(name)
+    ResultName::new(name).into()
 }
 ```
  
@@ -48,7 +48,7 @@ You've probably guessed it — `pack!(ResultName = String)` defines a type that
 ```rust
 // pack!(ResultName = String) generates code roughly like this
  
-#[derive(Groupped)]
+#[derive(Grouped)]
 pub struct ResultName {
     pub inner: String,
 }
@@ -88,7 +88,7 @@ fn handle_greet(args: EntryGreet) -> Next {
         .cloned()
         .unwrap_or_else(|| "World".to_string());
  
-    ResultName::new(name)
+    ResultName::new(name).into()
 }
 ```
  
@@ -112,7 +112,7 @@ fn handle_greet(args: EntryGreet) -> Next {
         .first()
         .cloned()
         .unwrap_or_else(|| "World".to_string());
-    ResultName::new(name)
+    ResultName::new(name).into()
 }
  
 fn main() {
diff --git a/docs/pages/4-render-result.md b/docs/pages/4-render-result.md
index b1365b8..ca1e563 100644
--- a/docs/pages/4-render-result.md
+++ b/docs/pages/4-render-result.md
@@ -51,7 +51,7 @@ fn handle_greet(args: EntryGreet) -> Next {
         .first()
         .cloned()
         .unwrap_or_else(|| "World".to_string());
-    ResultName::new(name)
+    ResultName::new(name).into()
 }
  
 // 4. Output results with a Renderer
diff --git a/docs/pages/5-multiple-commands.md b/docs/pages/5-multiple-commands.md
index a56f7b0..d9a335a 100644
--- a/docs/pages/5-multiple-commands.md
+++ b/docs/pages/5-multiple-commands.md
@@ -20,13 +20,13 @@ pack!(ResultSum = i32);
 #[chain]
 fn handle_greet(args: EntryGreet) -> Next {
     let name = args.inner.first().cloned().unwrap_or_else(|| "World".to_string());
-    ResultGreeting::new(name)
+    ResultGreeting::new(name).into()
 }
  
 #[chain]
 fn handle_add(args: EntryAdd) -> Next {
     let sum: i32 = args.inner.iter().filter_map(|s| s.parse::<i32>().ok()).sum();
-    ResultSum::new(sum)
+    ResultSum::new(sum).into()
 }
  
 #[renderer]
@@ -70,9 +70,9 @@ Notice `with_dispatchers`? When you need to register multiple dispatchers, just
 @@@dispatcher!("add", CMDAdd => EntryAdd);
 @@@pack!(ResultGreeting = String);
 @@@pack!(ResultSum = i32);
-@@@#[chain] fn handle_greet(_args: EntryGreet) -> Next { ResultGreeting::new("ok".into()) }
+@@@#[chain] fn handle_greet(_args: EntryGreet) -> Next { ResultGreeting::new("ok".into()).into() }
 @@@#[renderer] fn render_greet(_greeting: ResultGreeting) -> RenderResult { RenderResult::new() }
-@@@#[chain] fn handle_add(_args: EntryAdd) -> Next { ResultSum::new(0) }
+@@@#[chain] fn handle_add(_args: EntryAdd) -> Next { ResultSum::new(0).into() }
 @@@#[renderer] fn render_sum(_sum: ResultSum) -> RenderResult { RenderResult::new() }
 fn main() {
     let mut program = ThisProgram::new();
diff --git a/docs/pages/6-argument-parse-picker.md b/docs/pages/6-argument-parse-picker.md
index c80c25c..398cd3c 100644
--- a/docs/pages/6-argument-parse-picker.md
+++ b/docs/pages/6-argument-parse-picker.md
@@ -32,7 +32,7 @@ Now let's look at `Picker` in action:
 #[chain]
 fn handle_greet_entry(prev: EntryGreet) -> Next {
     let name = prev.pick_or((), "World").unpack();
-    ResultName::new(name)
+    ResultName::new(name).into()
 }
 ```
  
@@ -47,7 +47,7 @@ Breaking down the example above:
 @@@#[chain]
 @@@fn handle_greet_entry(prev: EntryGreet) -> Next {
 let name = prev.pick_or((), "World").unpack();
-@@@ResultName::new(name)
+@@@ResultName::new(name).into()
 @@@}
 ```
  
@@ -82,7 +82,7 @@ If your program needs to parse flag args (e.g., `greet --name Alice`), do this:
 #[chain]
 fn handle_greet_entry(prev: EntryGreet) -> Next {
     let name = prev.pick_or(["--name", "-n"], "World").unpack();
-    ResultName::new(name)
+    ResultName::new(name).into()
 }
 ```
  
@@ -124,7 +124,7 @@ fn handle_test_entry(prev: EntryTest) -> Next {
         .pick::<u32>(["--id", "-I"])
         .unpack();
  
-    ResultInfo::new((name, age, id))
+    ResultInfo::new((name, age, id)).into()
 }
 ```
  
@@ -224,7 +224,7 @@ fn handle_greet_entry(prev: EntryGreet) -> Next {
         })
         .unpack();
  
-    ResultName::new(name)
+    ResultName::new(name).into()
 }
 ```
  
@@ -345,7 +345,7 @@ impl Pickable for Address {
 #[chain]
 fn handle_connect_entry(prev: EntryConnect) -> Next {
     let address: Address = prev.pick("--addr").unpack();
-    ResultConnected::new(address)
+    ResultConnected::new(address).into()
 }
  
 #[renderer]
@@ -387,7 +387,7 @@ impl PickableEnum for Fruits {}
 #[chain]
 fn handle_eat_entry(prev: EntryEat) -> Next {
     let fruit: Fruits = prev.pick("--fruit").unpack();
-    ResultFruit::new(fruit)
+    ResultFruit::new(fruit).into()
 }
  
 #[renderer]
diff --git a/docs/pages/7-argument-parse-clap.md b/docs/pages/7-argument-parse-clap.md
index b11e00e..86fce35 100644
--- a/docs/pages/7-argument-parse-clap.md
+++ b/docs/pages/7-argument-parse-clap.md
@@ -25,7 +25,7 @@ Add `#[dispatcher_clap]` on a `clap::Parser` struct to auto-generate a Dispatche
 // Dependencies:
 // clap = "4"
 @@@ use mingling::macros::dispatcher_clap;
-#[derive(Default, clap::Parser, Groupped)]
+#[derive(Default, clap::Parser, Grouped)]
 #[dispatcher_clap("greet", CMDGreet, help = true, error = ErrorGreetParsed)]
 pub struct EntryGreet {
     #[clap(default_value = "World")]
@@ -64,7 +64,7 @@ If you need `--help` support, register `BasicProgramSetup` in main and set the c
 // clap = "4"
 @@@use mingling::setup::BasicProgramSetup;
 @@@use mingling::macros::dispatcher_clap;
-@@@#[derive(Default, clap::Parser, Groupped)]
+@@@#[derive(Default, clap::Parser, Grouped)]
 @@@#[dispatcher_clap("greet", CMDGreet)]
 @@@pub struct EntryGreet {
 @@@    name: String,
diff --git a/docs/pages/advanced/2-structural-renderer.md b/docs/pages/advanced/2-structural-renderer.md
index f31f758..910b197 100644
--- a/docs/pages/advanced/2-structural-renderer.md
+++ b/docs/pages/advanced/2-structural-renderer.md
@@ -37,7 +37,7 @@ pack_structural!(ResultInfo = (String, i32));
 fn handle_render(args: EntryRender) -> Next {
     let name = args.inner.first().cloned().unwrap_or_default();
     let age = args.inner.get(1).and_then(|s| s.parse().ok()).unwrap_or(0);
-    ResultInfo::new((name, age))
+    ResultInfo::new((name, age)).into()
 }
  
 #[renderer]
@@ -62,7 +62,7 @@ When the user passes `--json`, the framework automatically serializes the render
 
 ## Customizing Output Structure
 
-The default output from `pack_structural!` includes an `inner` field. For full control over the output structure, define the type manually with `#[derive(StructuralData, Serialize, Groupped)]`:
+The default output from `pack_structural!` includes an `inner` field. For full control over the output structure, define the type manually with `#[derive(StructuralData, Serialize, Grouped)]`:
 
 ```rust
 // Features: ["structural_renderer"]
@@ -74,7 +74,7 @@ The default output from `pack_structural!` includes an `inner` field. For full c
 @@@use serde::Serialize;
 @@@dispatcher!("render", CMDRender => EntryRender);
  
-#[derive(Serialize, StructuralData, Groupped)]
+#[derive(Serialize, StructuralData, Grouped)]
 struct Info {
     name: String,
     age: i32,
diff --git a/docs/pages/concepts/3-any-output.md b/docs/pages/concepts/3-any-output.md
index f780377..f02805f 100644
--- a/docs/pages/concepts/3-any-output.md
+++ b/docs/pages/concepts/3-any-output.md
@@ -20,7 +20,7 @@ AnyOutput<G>
  
 Here `G` is the program enum generated by `gen_program!()` (i.e., `ThisProgram` as you know it).
 
-Each type annotated with `pack!` or `#[derive(Groupped)]` is assigned to one variant of this enum.
+Each type annotated with `pack!` or `#[derive(Grouped)]` is assigned to one variant of this enum.
 
 ## ChainProcess: Data + Routing
 
@@ -38,17 +38,17 @@ This is why a Chain function returns `ChainProcess` instead of raw data—it bun
 
 The dispatcher reads `NextProcess` to decide whether to continue the loop or exit to rendering.
 
-## Groupped: Who Is Who
+## Grouped: Who Is Who
 
-How does the dispatcher know whether an `AnyOutput` holds a `ResultName` or an `ErrorUserBlocked`? The answer is the `Groupped` trait:
+How does the dispatcher know whether an `AnyOutput` holds a `ResultName` or an `ErrorUserBlocked`? The answer is the `Grouped` trait:
 
 ```
-trait Groupped<G> {
+trait Grouped<G> {
     fn member_id() -> G;
 }
 ```
  
-When you use `pack!(ResultName = String)`, the macro automatically implements `Groupped` for `ResultName`, and `member_id()` returns the corresponding enum variant. The dispatcher looks at `member_id` and finds the matching Chain or Renderer.
+When you use `pack!(ResultName = String)`, the macro automatically implements `Grouped` for `ResultName`, and `member_id()` returns the corresponding enum variant. The dispatcher looks at `member_id` and finds the matching Chain or Renderer.
 
 `to_chain()` and `to_render()` are essentially convenience methods on `AnyOutput` that construct `ChainProcess::Ok(any, Chain)` and `ChainProcess::Ok(any, Renderer)` respectively.
 
diff --git a/docs/pages/other/features.md b/docs/pages/other/features.md
index 813ccdd..7994d4c 100644
--- a/docs/pages/other/features.md
+++ b/docs/pages/other/features.md
@@ -24,7 +24,7 @@ pack!(StateFoo = ());
  
 #[chain]
 async fn handle_state_foo(foo: StateFoo) -> Next {
-    StateFoo::new(())
+    StateFoo::new(()).into()
 }
 ```
  
@@ -160,7 +160,7 @@ use mingling::macros::entry;
 pack!(EntryHello = Vec<String>);
  
 fn main() {
-    let result = handle_hello(entry!("--name", "Bob")).into();
+    let result: Next = handle_hello(entry!("--name", "Bob")).into();
     // ... assertion logic here
 }
  
@@ -171,7 +171,7 @@ fn handle_hello(args: EntryHello) {}
 ### `group!`
 
 Registers an external type as a member of the program group without modifying its definition.
-The type's simple name is used as the enum variant, just like `pack!` or `#[derive(Groupped)]`.
+The type's simple name is used as the enum variant, just like `pack!` or `#[derive(Grouped)]`.
 
 ```rust
 // Features: ["extra_macros"]
@@ -274,12 +274,24 @@ See [example](https://mingling-rs.github.io/mingling/docs/example-viewer.html?na
 
 **Description:**
 
-Enables the parser module, providing text parsing and analysis capabilities.
+Enables the argument parser module, providing argument parsing functionality.
 
-When enabled, you can use `Picker` for zero-cost argument extraction, supporting methods like `pick()` and `pick_or()`.
+When enabled, you can use `Picker` for simple argument extraction, supporting methods like `pick()` and `pick_or()`.
 
 See [example](https://mingling-rs.github.io/mingling/docs/example-viewer.html?name=example-argument-parse)
 
+## Feature `picker`
+
+**Description:**
+
+Introduces the `arg-picker` dependency, providing more advanced argument parsing capabilities for Mingling.
+
+It can coexist with the `parser` and `clap` features, but it is recommended not to enable it alongside the `parser` feature, as their APIs are very similar.
+
+`picker` is an argument parser independent of Mingling and does not rely on the built-in argument extraction API of `mingling_core`.
+
+See [example](https://mingling-rs.github.io/mingling/docs/example-viewer.html?name=example-argument-picker)
+
 ## Feature `repl`
 
 **Description:**
diff --git a/docs/pages/other/naming_rule.md b/docs/pages/other/naming_rule.md
index 2ede61f..089a711 100644
--- a/docs/pages/other/naming_rule.md
+++ b/docs/pages/other/naming_rule.md
@@ -96,7 +96,7 @@ Result + Content
 | `ResultGreetSomeone` | Greeting result   |
 | `ResultFruitList`    | Fruit list result |
 
-Result structs are expected to be consumed by the Renderer, and their internal structure should be designed for rendering aesthetics. Generally use `#[derive(Groupped)]` instead of `pack!()` wrapping for more flexible field control.
+Result structs are expected to be consumed by the Renderer, and their internal structure should be designed for rendering aesthetics. Generally use `#[derive(Grouped)]` instead of `pack!()` wrapping for more flexible field control.
 
 ### Error