Cc Hindsight — Development skill for Claude Code

cc-hindsight

**The prompt you'd write if you knew then what you know now.**

[](https://www.npmjs.com/package/cc-hindsight) [](https://github.com/adityaarunsinghal/cc-hindsight/actions/workflows/ci.yml) [](https://nodejs.org) [](LICENSE) [](#privacy--trust)

npx cc-hindsight

cc-hindsight mines your coding-agent session history (Claude Code, kiro-cli) into two things you can use tomorrow morning:

1. A oneshot prompt library. For each real task you've done, the realistic ideal first prompt: everything you knew and wanted at t=0 but didn't say, written in your own voice.
2. A distilled preference set. The things you keep re-telling your agent ("diagnose before acting", "pin the versions", "be terse"), surfaced as a paste-ready CLAUDE.md block so every future session starts aligned.

The t=0 problem

You get better results the more context you front-load into your first prompt, yet we underspecify at t=0 and spend the session steering: correcting course, restating preferences, answering questions the agent shouldn't have had to ask.

And the cost repeats every session. Your working preferences are stable facts about how you like to work, yet you re-derive and re-type them project after project instead of stating them once, upfront, where every future session reads them from the first message.

All the