Skip to content

frankkuipersgit/feeder

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 

Repository files navigation

Feeder

Feeder feeds your Git repository with updated skills and rules based on emails, meetings, chats, and other project communications.


The Problem

Project information is fragmented:

  • Emails
  • WhatsApp chats
  • Phone calls
  • Meeting transcripts
  • Notes
  • ChatGPT conversations

Context lives everywhere. Skills and rules in your repo get outdated. Cursor loses accuracy. Requirements drift.

Feeder solves this.


The Idea

ANY project information goes in
→ Gets routed to the correct project
→ Gets categorized and structured
→ Your Git repository is automatically updated

Your repo becomes the single source of truth.


What Feeder Does

1. Ingest Information

Supports input from:

  • Email
  • WhatsApp (WAHA / MCP)
  • Meeting transcripts
  • Manual notes
  • Chat logs

Everything becomes a structured Event.


2. Multi-Project Routing

Feeder automatically determines:

  • Which project this belongs to
  • What type of information it is

Examples:

  • Requirement
  • Decision
  • Open question
  • Scope change
  • Action item
  • Risk
  • Commercial agreement

Routing uses:

  • Deterministic rules (domains, phone numbers, threads)
  • Semantic matching
  • AI classification

3. Project Memory Engine

Each project maintains:

  • Requirements
  • Decisions
  • Open questions
  • Action items
  • Context digest

Stored both as structured data and as repository documents.


4. Repository Sync

Each project links to a Git repository.

Feeder automatically:

  • Updates docs/
  • Updates skills/
  • Updates rules/
  • Updates agents.md
  • Generates roadmaps or PoC proposals
  • Creates commits or PRs

Cursor always operates on up-to-date context.


5. Project Chat

You can directly feed new knowledge:

"I just had a call. They want to expand the AFAS integration."

That message enters the same pipeline:

→ Categorized
→ Structured
→ Synced to the repository

Chat becomes an input mechanism for structured project memory.


Architecture Overview

Information Pipeline:

Input Sources
→ Event Store
→ Project Routing
→ Categorization
→ Structured Memory
→ Git Repository Update
→ Cursor-ready context


Why Feeder

Feeder is designed for:

  • AI-assisted development workflows
  • Cursor-based repositories
  • Multi-project environments
  • Agencies and freelance developers
  • Teams that rely on evolving requirements

It eliminates manual restructuring and keeps project intelligence continuously synchronized.


Core Principle

The repository is the single source of truth.

All project information eventually becomes structured, versioned knowledge inside Git.


Status

Concept / Early Stage
Designed for AI-native development environments.


Vision

Move from scattered conversations
to structured project intelligence
to a self-updating development repository.

No manual copy-pasting. No lost decisions. No context drift.

About

Feeder feeds your Git repository with updated skills and rules based on emails, meetings, chats, and other project communications.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors