Invert visual hierarchy in Bash permission prompts

Problem

When a Bash command triggers a permission prompt, the raw shell command dominates the visual space while the human-readable description field is rendered as small grey text underneath. For complex commands (piped, multi-path, chained), the raw command is a wall of text that's hard to parse at a glance.

Current hierarchy:

1. 🔴 Big, prominent: ls -la ~/project/.claude/commands/linear.md ~/project/plugins/fort/skills/linear.md 2>/dev/null && echo "---" && ls -la ...
2. 🔇 Small grey: "Check if Linear skill and calendar files exist"

Users approve based on intent, not shell syntax. The description is what actually helps them decide.

Proposal

Invert the visual weight:

1. Prominent: The description field — this is the human-readable intent
2. Secondary/collapsible: The raw command — available for inspection but not the focus

Something like:

Bash command
  Check if Linear skill and calendar files exist
  ▸ ls -la ~/project/...  (click to expand)
  
  Do you want to proceed?

Context

The description field already exists and is well-supported — agents/models are encouraged to write clear descriptions. But the UI buries it, making the approval flow harder than it needs to be for power users running complex commands.

🤖 Generated with Claude Code