Skip to content

Make row activation consistent and surface prune in the shell - #1615

Open
nickprotop wants to merge 2 commits into
managedcode:mainfrom
nickprotop:tui-ux-consistency
Open

nickprotop wants to merge 2 commits into
managedcode:mainfrom
nickprotop:tui-ux-consistency

Conversation

@nickprotop

Copy link
Copy Markdown
Contributor

Enter and double-click open details on every page, including the project scan, which installed to disk instead.

Add Prune stale to the project toolbar, so auto-managed skills whose signal disappeared can be reconciled without leaving the shell.

Mark auto-install candidates in the project scan, the subset install --auto actually writes.

Group the skills browser by collection and lane instead of repeating both on every row.

Upgrade SharpConsoleUI to 2.10.5, with the AngleSharp and Spectre.Console bumps its package requires.

Enter and double-click open details on every page, including the project
scan, which installed to disk instead.

Add Prune stale to the project toolbar, so auto-managed skills whose signal
disappeared can be reconciled without leaving the shell.

Mark auto-install candidates in the project scan, the subset install --auto
actually writes.

Group the skills browser by collection and lane instead of repeating both on
every row.

Upgrade SharpConsoleUI to 2.10.5, with the AngleSharp and Spectre.Console
bumps its package requires.
Undim the grouping rows in the catalog trees: with real tree guides the
indentation already says "this is a level", so the grey only cost legibility.

Drop the main window's frame. It is maximised and never dragged, so the
border only cost two columns and two rows.

Give the dialogs room and a surface: content inset from the frame, code
blocks and quotes coloured for the dialog rather than for a black terminal,
buttons on their own raised background, and a footer row that reads as a
toolbar instead of text at the edge.

Right-align the dialog buttons through a grid, the way cxagent's
DialogLook.Footer does: a star column beside the toolbar absorbs the width.
Toolbar alignment cannot do it, because the dock layout that places the
toolbar ignores it.

Make the quit dialog solid. Eight rows, half of them frame and buttons,
leaves a vertical gradient too little height to read as one.

Merge About into Home. The two answered the same question from different
ends, and a user reading "target .claude/skills" had to leave the page to
learn where the catalog came from. Home now carries the paths, the keys and
the version, and the rail loses an entry that fit in no section.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant