You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AGENTS.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,6 +109,7 @@ Treat explicit frustration, swearing, sarcasm, repeated rejection, or "don't do
109
109
- 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.
110
110
- In the interactive shell, expose a first-class direct `Skills` browse/install surface for people who want to inspect or pick individual skills without going through `Collections` or `Bundles` first. Collection- and bundle-first flows may stay primary for taxonomy and grouped installs, but direct individual-skill browsing cannot be missing.
111
111
- Keep the public site IA and the interactive shell IA synchronized. If the site exposes a first-class surface such as `Packages`, `Bundles`, `Collections`, `Skills`, `Agents`, or `About`, the CLI must either expose the same surface explicitly or make the intentional difference obvious in the home UI and help copy. Prefer deriving site and CLI primary-navigation labels from one shared repo-owned model instead of maintaining parallel hardcoded lists.
112
+
- The interactive shell home screen must be navigable as a real menu without requiring typed action keys. Do not make `Action key:`-style manual key entry the primary way to leave the home screen; use arrow/enter menu navigation and keep any shortcut hints strictly secondary.
112
113
- 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.
113
114
- 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.
114
115
- 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.
Copy file name to clipboardExpand all lines: docs/cli-rewrite-plan.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -459,6 +459,12 @@ Suggested accents:
459
459
-[x] Reorder and recopy the home/control-center navigation so `Packages`, `Bundles`, `Collections`, `Skills`, and `Agents` stay visibly aligned with the site.
460
460
-[x] Revalidate the new shared IA in a real TTY and in generated GitHub Pages output before release.
461
461
462
+
### Phase 3e — Home menu interaction follow-up
463
+
464
+
-[x] Replace typed `Action key:` home entry with a real arrow/enter menu prompt.
465
+
-[x] Demote shortcut keys from the home control copy so the primary affordance reads like menu navigation instead of manual command entry.
466
+
-[x] Revalidate the new home menu in a real TTY after installing the freshly packed tool locally.
467
+
462
468
### Phase 4 — Remove terminology drift
463
469
464
470
-[x] Replace remaining public `Stack` wording with `Collection` in:
0 commit comments