footer

Files (1)

• SKILL.md

SKILL.md (first lines)

# Pi Footer — natural-language management

The status bar is the `@victorhg/pi-footer` powerdev footer. The user talks
about it in plain words; you translate to the actions below. Prefer the
`/footer` and `/vibe` slash commands over hand-editing JSON — they
validate input, persist to `~/.pi/agent/settings.json` (global) or
`.pi/settings.json` (project), and re-render immediately.

## Vocabulary mapping

| User says | Do this |
|---|---|
| "remove the hallmark / hide the badge / get rid of X from the footer" | `/footer disable <id>` |
| "bring back X / show X again" | `/footer enable <id>` |
| "make the footer minimal / compact / fuller / nerdy / ascii" | `/footer preset <default\|minimal\|compact\|full\|nerd\|ascii>` |
| "move the footer above/below the editor" | `/footer placement <above\|below\|footer\|toggle>` |
| "turn off the footer / use the built-in footer" | `/footer toggle` |
| "change the separator style" | `/footer separator <style>` |
| "what's the footer doing / is anything misconfigured" | `/footer status` |
| "what can the footer do / how do I use the footer" | `/footer help` |
| "what's shown in the footer / which extensions are in the footer" | `/footer list` |
| "color the model pink / recolor the footer" | `/footer theme <semantic> <theme-token\|#hex>` — e.g. `/footer theme model #ff5500` |
| "reset footer colors" | `/footer theme reset [<semantic>]` |
| "working vibes / themed loading messages" | `/vibe <star trek\|pirate\|noir\|zen\|cowboy\|cyberpunk>` · `/vibe off` · `/vibe color <token\|#hex\|rainbow>` · `/vibe list` |

## What the ids are

**Registry items** (from the other `@victorhg/pi-*` packages — disable by
their key): `hallmark`, `code-quality`, `web-quality`, `sec-quality`,
`auto-compact`, `token-saver`, `research`.

**Built-in segments** (disable by id): `model`, `thinking`, `shell_mode`,
`path`, `git`, `queue`, `subagents`, `token_in`, `token_out`,
`token_total`, `cache_read`, `cache_write`, `cost`, `context_pct`,
`context_total`, `time_spent`, `time`, `session`, `hostname`,
`extension_statuses`.

**Custom items**: any extension status key promoted via
`footer.customItems` — disable with `custom:<id>` or the bare id.

## Changing what shows (layout)

To reorder or move items between rows (left / right / secondary), edit
`footer.layout` in settings.json:

```json
{
  "footer": {
    "layout": {
      "left": ["model", "path", "git"],
      "right": ["context_pct", "cost"],
      "secondary": []
    }
  }
}
```

Registry items can also be placed in `layout` by their key. Then tell the
user what you changed and that it applies on the next render.

## Rules

1. **Commands first.** If a `/footer` or `/vibe` subcommand covers the
   request, run it and report the notification result. Do not rewrite the
   settings file by hand when a command exists.
2. **One action at a time.** Multiple changes = multiple commands, each
   reported.
3. **No config guesses.** If the user names something that is neither a
   built-in segment nor a known registry key (ask `footerRegistry` state
   via `/footer status` when unsure), say so and list what exists instead
   of inventing an id.
4. **Verification.** After changing, confirm with `/footer status` and
   tell the user what changed. A change that needs a session restart is
   called out explicitly (placement applies immediately since v2; nothing
   needs a restart).
5. **This instance vs. everywhere.** "this instance" / "this project" =
   project settings (`.pi/settings.json`, project-local); "always" /
   "globally" = the agent settings file (`~/.pi/agent/settings.json`). The
   slash commands persist to the agent settings file by default — for
   project-only changes, edit `.pi/settings.json` directly and note it.

From victorhg/pi-dev, MIT.

More from victorhg/pi-dev