Skip to content
Mel edited this page Nov 10, 2026 · 1 revision

Browse is the stack's catalog. The prompt line shows where you are, and the search box follows it.

~/skills/file-pr  ›  type to search

Home

~ ›

★ skills        ████████████████████   3
● styles        ███████·············   1
■ systems       ███████·············   1
◆ components    █████████████·······   2
▶ libraries     ███████·············   1
♥ assets        ███████·············   1
▲ templates     ███████·············   1
☻ workers       █████████████·······   2
~ all                                 12

(^_^) stable 6   (o_O) experimental 6   (x_x) deprecated 0
★ custom 12      ☆ imported 0

Each kind row opens that kind. all lists every entry.

The sprite marks the kind: ★ skill, ● style, ■ system, ◆ component, ▶ library, ♥ asset, ▲ template, ☻ worker. A filled sprite means the entry's origin is custom, a hollow one means imported. That is the entry's origin in the stack, not what your project imported.

Kind views

~/skills ›

★ file-pr      (^_^)  2f 219b
★ ponytail     (o_O)  2f 219b

Each row shows the name, the status face, and the file count and size. A not-committed or uncommitted-in-stack marker may follow the name. Components are grouped by library, as components/react, with a member count and default if it is the default library.

All

Every entry, in kind order. Rows show full ids (skills/file-pr).

Search

Type anywhere: the first letter focuses the search box. A search matches substrings of the name, tags, id, summary and targets, across all kinds. Words are matched separately. An entry needs at least one match, and more matches rank it higher. A name match counts most.

~ › pr

★ skills/file-pr       (^_^)  2f 219b
▲ templates/agents-md  (^_^)  4f 451b      ← "project" in the summary

Search runs in the app over the catalog list; it does not call the CLI's search.

Entry page

★ ponytail  (o_O)

Lazy senior dev mode: the smallest change that fully solves the task.

usage    link
size     2 files, 219b
targets  any
tags     ponytail, fixture

files
ponytail/
├─ README.md  109b
└─ stack.json 110b

From top to bottom, the page shows:

  1. Title, status face and the summary.
  2. not committed in the stack: can't import when the entry is not in the stack's HEAD commit.
  3. imported → <path> when this project already imported it.
  4. Details: usage, size, targets, tags, requires, related, cited by and upstream (source URL, ref, license, modified) when present.
  5. The import row, when the entry is committed and not imported yet.
  6. The result of the last import or a refusal.
  7. Up to four image previews.
  8. The file tree, then the open file.

Files and docs

Click a file in the tree, or move to it with the arrows and press Enter. Its body appears under its path:

  • Markdown is rendered. Links to other entries open in the app. External links open in a browser window.
  • Other text files are shown as they are.
  • Images are shown inline.
  • Binary files show their size and binary … — open it from the checkout.

Import

import
[--to                    ]  [import]
  • Leave --to empty and the CLI chooses the place. Skills and styles go to .agents/skills/<name>, with a .claude/skills link. Other entries go to .stack/<id>. Components go to .stack/components/<library>/<name>.

  • Fill --to with a folder inside the project, such as src/components/ui. Absolute paths and paths that leave the project are refused, including through symlinks.

  • An import writes nothing if a target file already exists with different content. The app then shows the files and says so:

    untracked look-alikes, nothing written:
    
    .agents/skills/file-pr/SKILL.md
    .agents/skills/file-pr/helpers.mjs
    

    Move those files, pick another --to, or delete them if they are yours to drop. A file with identical content is not a conflict.

  • An entry that is not in the stack's HEAD commit cannot be imported. Commit it in the stack checkout first.

  • uncommitted-in-stack means the stack's working tree has changes for the entry. Imports read the committed version, not the working tree.

  • Each import is recorded in stack.toml. A successful import lists what landed:

    imported 1 entry
    
    skills/ponytail → vendored/ponytail
    

    Entries pulled in by requires show (required by …). Entries already here show under already here. A .gitignore line shows when the managed block changed.

Keys in Browse

Key Does
↑ ↓ move the cursor over rows: home rows, list rows, file tree
Enter open the cursor row. With a search and no cursor, open the first result
Escape clear the search. Otherwise go up one level: file → entry → kind → home
Space scroll down about 80% of a page, when the search box is empty
letter or digit focus the search box and type into it

Clicking a row or link does the same as moving to it and pressing Enter. j and k are not bound in browse.

See also: Installed, Keyboard Shortcuts, Settings and Storage.

Clone this wiki locally