Chipflow Context Daddy
chipflow-context-daddy is a Claude Code plugin for the Build phase that manages project manifest, repo mapping, and persistent learnings so agent context survives across sessions.
by ChipFlow · github.com/ChipFlow/context-daddy
Give Claude Code a persistent project manifest, repo map with duplicate detection, and a learnings system so context survives long sessions and handoffs.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install chipflow-context-daddy@ChipFlow/context-daddyBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:ChipFlow/context-daddy") and the paste-ready config with skillselion.get_install_config("plugin:ChipFlow/context-daddy").
What it does
chipflow-context-daddy is a Claude Code plugin bundle dedicated to context management for solo builders on large or long-lived repositories. It provides a project manifest so the agent starts from an agreed map of what matters, a repo map workflow that highlights duplication before you refactor blindly, and a learnings system meant to preserve decisions that usually die in chat history. The positioning emphasizes responsible use on adult codebases where exploration noise and forgotten rationale slow every new session. Install it when tribal knowledge, narrative context, and cross-session continuity are bigger bottlenecks than raw code generation. It pairs naturally with documentation-heavy phases and ongoing iteration, because the same manifest and learnings reduce re-explaining architecture after every break. One plugin count keeps scope narrow: this is infrastructure for memory and orientation, not a feature generator.
Highlights
- Project manifest for stable, session-spanning orientation
- Repo map with duplicate detection to reduce redundant exploration
- Learnings system that captures narrative tribal knowledge across chats
- Living documentation that outlasts single-session memory limits
- Single-plugin bundle focused on context daddy tooling for mature codebases
Why builders use it
Agents lose tribal knowledge and re-walk the same repo paths every session, wasting tokens and repeating mistakes on mature codebases.
After install, Claude Code can lean on a manifest, deduplicated repo map, and stored learnings instead of rediscovering your project from scratch.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 8 stars, 0 votes.
FAQ
Who is chipflow-context-daddy for?
It is for Claude Code users maintaining complex codebases who need manifests, repo maps, and learnings that persist beyond one chat.
When should I use chipflow-context-daddy?
Use it when exploration repeats, duplicates confuse refactors, or tribal knowledge keeps getting re-explained to the agent.
How do I add chipflow-context-daddy to my agent?
Register the ChipFlow/context-daddy marketplace or plugin source in Claude Code and enable the context-daddy plugin for your workspace.
Comments
Share how you use chipflow-context-daddy, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.