Dev Framework
Dev Framework is visible project memory for AI-assisted development, shipped as a Claude Code plugin with its own marketplace.
It is small in what it depends on and broad in what it covers: fifteen skills, built from Markdown, YAML frontmatter, and portable bash hooks. This portfolio runs on it.
- AI tooling
- Project memory
- Developer experience
The problem
Agents forget everything between sessions, and a monolithic doc file meant to remember for them fights parallel work instead of supporting it.
The shape
Memory splits into a docs/dev/ tree with a home for each kind of knowledge: decisions, learnings, questions, open items, proposals, changelog, features, runbooks, rulesets, and specs.
No Node, no Python, no daemon. It is Markdown, YAML frontmatter, and portable bash hooks.
The loop
Every task starts by reading .summary.md, the whole tree condensed into one file, and the work feeds what it learns and decides back into the tree. One of the hooks blocks AI-attribution commit trailers on the way out.
Recurring learnings get promoted into rulesets, and recall works across projects, so a lesson learned in one repo can surface in another.
What changed
Sessions stop starting from zero. This portfolio runs on Dev Framework: its decisions, learnings, and changelog live in a docs/dev/ tree, and every task here starts from the summary.
A companion app, dev-inbox, covers the human side: a Tauri v2 tray app whose badge counts the open items waiting on me across every configured project, and which marks an item done or dropped with an optional note written back into its Markdown.