How this command is triggered — by the user, by Claude, or both
Slash command
/projects:listThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# List Projects List all projects from the registry at `~/.claude/projects.json`. ## Instructions 1. Read `~/.claude/projects.json` 2. Display projects sorted by `last_worked` (most recent first) 3. Show: name, path, last worked date ## Output Format ## Registry Format
List all projects from the registry at ~/.claude/projects.json.
~/.claude/projects.jsonlast_worked (most recent first)name path last_worked
---- ---- -----------
myproject /home/user/projects/myproject 2026-01-31
another /home/user/another 2026-01-30
{
"projects": {
"name": {
"path": "/absolute/path",
"last_worked": "YYYY-MM-DD"
}
}
}
npx claudepluginhub cyberswat/claude-plugin-projects/projectsLists registered projects from ~/.claude/homunculus/projects.json with name, id, root, remote, personal/inherited instinct counts, observation events, last seen timestamps, and global totals.
/projectsLists registered projects from ~/.claude/homunculus/projects.json with name, ID, root, remote, personal/inherited instinct counts, observation events, last seen timestamp. Shows global instinct total.
/projectsDisplays summaries of projects for all clients or a specified client, including name, status, goals, requirements, technical context, and progress from markdown files.
/listLists installed and generated CLI-Anything tools, scanning packages and directories. Supports --path for directory, --depth for recursion, --json for output format.
/listLists beads issues with filters for status, priority, type, assignee, labels, title, dates, and more. Outputs table, JSON, digraph, or DOT formats.
/listLists all configured Hookify rules from .claude/hookify.*.local.md files in a summary table with name, enabled status, event, pattern, file path, plus message previews and management footer.