The Claude repos I actually keep cloned
Seven Claude repos that earn a folder: the job, the leave-it-alone rule, and the one I swapped off the usual list.
Keep-cloned is not starred. Starred is a bookmark I will not open. A clone is a folder I can cd into without a network, grep without a search box, and delete when the job is gone.
This is the set that earns a folder. Seven names. One of them is not on the usual roundup.
The filter
A repo stays cloned if I can finish this sentence: I open this directory for X, and I leave it alone the rest of the time.
That kills most Claude GitHub results. A tutorial I read once is a tab, not a checkout.
What stays cloned
awesome-claude-code. The map. I grep it when I am looking for a skill, a plugin, or a statusline I have not tried. Leave it alone if you already know the three tools you use. I do not run anything from it.
ccusage. Token and cost from the local JSONL. npx ccusage is enough for a report; the clone is for when the numbers look wrong and I want the parser. Leave it alone if you are not looking at spend.
Superpowers. The swap. Plan, failing test, implementation, review. I clone the skills so I can read them. On for a feature. Off for a rename. This is the one that took Claude Engineer's slot.
claude-cookbooks. Official recipes. Clone when I am learning a new API surface. Delete when the recipe is in my own repo.
MCP servers. Reference servers. Clone when I am copying a transport or a tool shape. Leave it alone if I am not writing an MCP this week.
repomix. Packs a repo into one file for a paste box. I use it when the model does not have the filesystem — claude.ai, a one-off chat, a review outside Claude Code. Leave it alone when Claude Code is already in the repo.
Task Master. PRD in, task graph out. Clone when there is a product document to explode. Leave it alone for a single ticket.
What I do not clone
Claude Engineer. December 2024. A CLI that taught Claude to grow its own tools, before Claude Code was the default. I do not keep a 2024 wrapper next to the product that replaced it.
ruflo. It is on every "clone these" list. I ship ClaudeFlow. Same shape of name, different product. I do not keep a colliding checkout on disk.
The order I would use again
Day one: the awesome list, then ccusage if I am paying per token. When the work is a feature: Superpowers. When I am stuck on an API or an MCP: cookbooks or the servers repo, then delete. When the model is a paste box: repomix. When the input is a PRD: Task Master.
Seven is a ceiling. Two is a working setup.
The rest of the system — named agents and workflow files — lives in ClaudeFlow.