[new feature idea] Tips based on usage behavior

This is a great project! I'm curious if you would be open to a PR for tips based the stats collected from Sniffly?

For example, [in your LinkedIn post](https://www.linkedin.com/posts/chiphuyen_i-open-sourced-sniffly-httpslnkdingeek3hgn-activity-7351296214056775681-0hO6?utm_source=share&utm_medium=member_desktop&rcm=ACoAAABAcOoBdLM9XMTCQOxL_H12EVPJ81TGh4I), you mention:

> The biggest type of errors Claude Code made is Content Not Found (20 - 30%). It tries to find files or functions that don't exist.

💡 Claude is having trouble finding some files and functions. Consider providing guidance of file locations in a `CLAUDE.md` file. View the most common not found errors.

Review Sniffly's existing usage-statistics and error-analysis dashboard, then read the linked LinkedIn example for context. Clarify which behavior signals produce tips, what content they show, and what the “View the most common not found errors” link should open; completion requires an agreed scope and user-facing flow.

Written by the indexing model from the issue text.