Skip to content

Commit 6fdc282

Browse files
committed
Redesign interactive CLI page surfaces
1 parent 5eec8bd commit 6fdc282

3 files changed

Lines changed: 662 additions & 641 deletions

File tree

AGENTS.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -109,6 +109,7 @@ Treat explicit frustration, swearing, sarcasm, repeated rejection, or "don't do
109109
- In the interactive shell home screen, keep `Update all skills` visible as a first-class action even when no outdated skills are currently detected. In the zero-outdated case, keep the action callable and return a clear no-op status instead of hiding the entry.
110110
- When replacing the interactive shell home or entry UX, remove the superseded legacy menu flow from the published tool instead of leaving a parallel flat prompt path behind the new control center.
111111
- In the interactive shell, escape Spectre markup syntax in every prompt choice label and prompt-only caption before rendering selection or multi-selection pickers. Keep a regression test that covers labels containing brackets and `.NET` text from bundle or collection surfaces.
112+
- Interactive collection, analysis, bundle, installed, and agent pages must not ship as giant spreadsheet-style matrices. Each page needs an intentional dominant pane plus supporting card-style summaries; use a large table only when it is clearly the best representation for that page instead of the default.
112113
- When CLI UX changes are the point of the task, finish by installing or updating the local `dotnet-skills` tool from the freshly built package in the current environment so the new shell can be verified immediately instead of only existing in git.
113114
- When changing the publishable `dotnet-skills` tool UX or behavior, do not stop at local verification. Also verify the release path end-to-end: the packed tool version, the publish workflow, and the publicly installable package or release artifact must all reflect the new behavior before reporting the work as complete.
114115
- Track per-skill token size as first-class catalog metadata when the user asks for token visibility. Compute it during catalog generation or build, surface it in generated aggregates, and show it in the interactive UI where users inspect or compare skills.

0 commit comments

Comments
 (0)