ContextsBase is a single-source context infrastructure platform (web app) that manages unified project knowledge for AI agents. Served seamlessly over MCP, it holds your specs, rules, data models, workflows, and guidelines in one place. It isn't limited to web development. Whether you're building backend APIs, mobile apps, systems software, or even managing marketing campaigns and brand engines, it acts as the central source of truth that your agents read from and report back to.
What inspired this: I was shipping a side project almost entirely with Claude Code and Cursor. The code was good. The product was wrong. The agent invented a tier field on Customer that didn't exist and every new session started with me pasting the same Notion doc back into the chat. When a teammate changed a rule on Thursday, the code from Tuesday was quietly out of date and nothing told us.
Every one of those failures was the same failure. The agent never had the actual product truth, and nothing checked its work against it.
The problem I was trying to solve
Every team has a knowledge base for humans: a wiki, a data model diagram, acceptance criteria. Agents get a pasted prompt. ContextsBase is the knowledge base your coding agents read from. You write features, business rules, the data model, and test cases once. Your agent, whichever one you use, pulls them over MCP in one call, builds the feature, writes tests that assert the business rule instead of clicking a button, and records what it built against which spec.
We don't supply the agent. Bring Claude Code, Cursor, Copilot, or Windsurf. We supply what they build from.
How it evolved
The first version was just structured specs. Then I noticed the test problem: everybody's E2E suite proves the UI works, almost nobody asserts the rule. So test cases became Given/When/Then business rules that the agent turns into Playwright code. Then came iterations, an ordered queue agents pull from one step at a time so two agents never build the same thing. Recently we added a theme designer, so agents build on-brand from published tokens, and a page editor where you click any element on your live site, change the words or styling, and your agent applies it to the real code.
About ContextsBase - Backlog for Coding Agents on Product Hunt
“From chat prompts to AI backlog Platform.”
ContextsBase - Backlog for Coding Agents launched on Product Hunt on September 18th, 2026 and earned 74 upvotes and 3 comments, placing #24 on the daily leaderboard. ContextsBase is a single-source context infrastructure platform (web app) that manages unified project knowledge for AI agents. Served seamlessly over MCP, it holds your specs, rules, data models, workflows, and guidelines in one place. It isn't limited to web development. Whether you're building backend APIs, mobile apps, systems software, or even managing marketing campaigns and brand engines, it acts as the central source of truth that your agents read from and report back to.
On the analytics side, ContextsBase - Backlog for Coding Agents competes within Developer Tools, Artificial Intelligence, Tech and OpenAI Day — topics that collectively have 1.6M followers on Product Hunt. The dashboard above tracks how ContextsBase - Backlog for Coding Agents performed against the three products that launched closest to it on the same day.
Who hunted ContextsBase - Backlog for Coding Agents?
ContextsBase - Backlog for Coding Agents was hunted by Amir Alam. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of ContextsBase - Backlog for Coding Agents including community comment highlights and product details, visit the product overview.
Amir Alam
What inspired this:
I was shipping a side project almost entirely with Claude Code and Cursor. The code was good. The product was wrong. The agent invented a tier field on Customer that didn't exist and every new session started with me pasting the same Notion doc back into the chat. When a teammate changed a rule on Thursday, the code from Tuesday was quietly out of date and nothing told us.
Every one of those failures was the same failure. The agent never had the actual product truth, and nothing checked its work against it.
The problem I was trying to solve
Every team has a knowledge base for humans: a wiki, a data model diagram, acceptance criteria. Agents get a pasted prompt. ContextsBase is the knowledge base your coding agents read from. You write features, business rules, the data model, and test cases once. Your agent, whichever one you use, pulls them over MCP in one call, builds the feature, writes tests that assert the business rule instead of clicking a button, and records what it built against which spec.
We don't supply the agent. Bring Claude Code, Cursor, Copilot, or Windsurf. We supply what they build from.
How it evolved
The first version was just structured specs. Then I noticed the test problem: everybody's E2E suite proves the UI works, almost nobody asserts the rule. So test cases became Given/When/Then business rules that the agent turns into Playwright code. Then came iterations, an ordered queue agents pull from one step at a time so two agents never build the same thing. Recently we added a theme designer, so agents build on-brand from published tokens, and a page editor where you click any element on your live site, change the words or styling, and your agent applies it to the real code.