Seven prompts that analyse your Claude Code usage habits ship with no entry point.
Prompts for project areas, friction, suggestions and more exist as data with nothing invoking them.
What's wrong with this entry?
Seven prompts that analyse how you have been using Claude Code ship as plain data: project areas, interaction style, what works, friction analysis, suggestions, on the horizon and a fun ending. Each allows 8192 tokens and demands a strict JSON reply. The suggestions prompt describes MCP servers, custom skills, hooks, headless mode and task agents, and asks the model to prioritise CLAUDE.md additions you have repeated across sessions.
- The list splices in an empty array before the closing prompt, which is what a conditionally compiled section looks like when it is switched off.
- Nothing in this group shows what surfaces these prompts.
Include 3 opportunities. Think BIG - autonomous workflows, parallel agents, iterating against tests.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.238
Preloading a skill no longer does the built-in command's real work
Both mention insight
-
v2.1.221
Session state moves onto a pluggable storage backend
Both mention usage
-
v2.1.235
Usage breakdown now attributes usage to subagents
Both mention usage