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/projectsDisplays all Claude Code projects tracked by EverMem, grouped by project directory with session count and last active time. Reads from the local groups.jsonl data file.
/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 all installed and generated CLI-Anything tools with version, status, and path. Supports custom scan directories and JSON output.
/listLists beads project issues with rich filtering by status, priority, type, assignee, labels, title, date ranges, and more. Outputs as table, JSON, or graph formats.
/listLists all configured hookify rules in the project by scanning .claude/hookify.*.local.md files and displaying their frontmatter, status, and message previews in a table.