Hey HN –
I’m Jason, a backend dev and AI tool builder at Titanium Computing. I’ve been working on a project called Context Forge that solves a pain I kept running into with Claude and AI-powered IDEs: context loss during long sessions.
Claude and other LLMs often “forget” previous instructions mid-session due to compaction. So I built a CLI-based system to structure, version, and re-inject context directly into the coding workflow.
What Context Forge does:
• Scaffolds a CLAUDE.md file to define coding rules, format standards, and AI guardrails
• Creates a /prps folder full of Product Requirements Prompts (PRPs) – combining scoped reasoning, validation steps, and feature history
• Adds a /docs folder for staging narrative documentation and implementation planning
• Works hand-in-hand with Claude Code’s new preCompact hook to re-inject scoped context when compaction happens
Bonus: I built a companion CLI called Claude Hooks Manager to auto-detect Claude context compaction events and reload the right PRPs from the repo.
This setup has been a game-changer for keeping Claude on track through long dev sessions, and it works across:
• Claude Code (CLI)
• Cursor IDE
• Copilot
• n8n and other AI-assisted workflows
Right now it’s just me dogfooding this heavily in my own work, but I’d love to hear what others in the AI + coding space think — especially if you’re building systems that rely on consistent context management.
Hey HN – I’m Jason, a backend dev and AI tool builder at Titanium Computing. I’ve been working on a project called Context Forge that solves a pain I kept running into with Claude and AI-powered IDEs: context loss during long sessions.
Claude and other LLMs often “forget” previous instructions mid-session due to compaction. So I built a CLI-based system to structure, version, and re-inject context directly into the coding workflow.
What Context Forge does: • Scaffolds a CLAUDE.md file to define coding rules, format standards, and AI guardrails • Creates a /prps folder full of Product Requirements Prompts (PRPs) – combining scoped reasoning, validation steps, and feature history • Adds a /docs folder for staging narrative documentation and implementation planning • Works hand-in-hand with Claude Code’s new preCompact hook to re-inject scoped context when compaction happens
Bonus: I built a companion CLI called Claude Hooks Manager to auto-detect Claude context compaction events and reload the right PRPs from the repo.
This setup has been a game-changer for keeping Claude on track through long dev sessions, and it works across: • Claude Code (CLI) • Cursor IDE • Copilot • n8n and other AI-assisted workflows
Open Source: • Context Forge: https://github.com/webdevtodayjason/context-forge • Claude Hooks Manager: https://github.com/webdevtodayjason/claude-hooks
Right now it’s just me dogfooding this heavily in my own work, but I’d love to hear what others in the AI + coding space think — especially if you’re building systems that rely on consistent context management.
Appreciate any feedback or ideas!
— Jason