> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pensiv.so/llms.txt
> Use this file to discover all available pages before exploring further.

# 8.5 How to think about the command palette

> Difference from menus, when it becomes central, design intent

The command palette\
is not meant to replace menus.\
Menus and the command palette\
use **different ways** to get to things.

***

## Menus vs. command palette

* **Menus**\
  → You follow structure to find a feature
* **Command palette**\
  → You type what you want to do first

Menus answer “where is it?”\
The command palette answers “what do I want to do?”

***

## When does the command palette become central?

As you get used to Pensiv, this often changes:

* You think of **what you want to do** before where it is
* **Speed** matters more than moving around the UI
* With more files, **typing** beats browsing

From that point on,\
the command palette is not a side tool —\
it’s your **main way to move and act**.

***

## Design intent

The command palette\
is not a “learning” feature.

It’s built so that\
**the more you work, the more you use it**.

The idea is: don’t memorize structure —\
**type the action**.

***

## Summary

Using Pensiv efficiently\
is not about memorizing the menu structure.

When you know what you want to do,\
**open `Ctrl + K` first**.

The command palette\
is the shortest path from intent to action.