Name: Pretty Output Pattern
Author: aladac

All marauder commands should provide clean visual feedback using Claude Code's native Task system.

Why Pretty Output

Users see a spinner with descriptive text instead of verbose command output
Clean, consistent experience across all commands
Verbose details only shown on error or in final summary
Native Claude Code UI integration

The Pattern

1. Create Task at Start

TaskCreate(
  subject: "Brief action description",
  description: "Detailed context for task tracking",
  activeForm: "Doing the thing..."  // Shown with spinner
)

2. Do Work Silently

Run the actual operations. Output is captured, not streamed.

Operation	activeForm
Store memory	"Storing memory..."
Recall memories	"Searching memories..."
Index code	"Indexing 247 files..."
Save session	"Saving session state..."
TTS speak	"Synthesizing speech..."

Pretty Output Pattern

Why Pretty Output

The Pattern

1. Create Task at Start

2. Do Work Silently

3. Update Status on Completion

Pretty Output Pattern

Why Pretty Output

The Pattern

1. Create Task at Start

2. Do Work Silently

3. Update Status on Completion

4. Show Clean Summary

activeForm Guidelines

Good Examples

Bad Examples

Command Template

Oracle

Blucli

Peekaboo

Add Dock Band

Add Fallback Commands

Add Adaptive Card Form