Preserve Team Intelligence
While Building at AI Speed
Your team discusses, debates, decides.
Then Claude builds. In 20 minutes.
But only the code survives.
PCF captures collective intelligence as it emerges—before you lose it. The discussions. The constraints. The trade-offs. The "why."
Built by developers, for developers. Open source. Zero lock-in.
The Intelligence Gap
AI makes building fast. But fast without memory is dangerous.
The Scenario
TEAM DISCUSSION (30 minutes)
PM: "Users need to share stories"
Designer: "Privacy is critical"
CTO: "Cost must be under £0.10/user"
Dev: "Firebase vs Cloudflare?"
Team decides: Cloudflare + private links only
DEVELOPER TO CLAUDE CODE (2 minutes)
What Claude DOESN'T Get
Why Cloudflare over Firebase (cost constraint)
Why private links only (privacy model)
Why no username search (prevent unwanted discovery)
Who made which calls (CTO cost decision, designer privacy)
PCF Captures All of This Before You Start Coding
The constraints (cost per user, privacy requirements)
The options considered (Firebase, Supabase, Cloudflare)
The trade-offs accepted (less mature ecosystem)
Who decided what (CTO on cost, designer on privacy)
Result: Future teams understand your reasoning, not just your code.
Mediate Before You Build
AI can turn "idea" into "code" in minutes.
PCF forces a pause: "What are we actually building and why?"
The Discipline
Before you open Claude Code. Before you type the prompt. Take 30 seconds to capture what you're about to build.
What PCF Asks:
- •What problem are we solving?
- •What constraints matter?
- •What options did we consider?
- •Why this approach?
- •What trade-offs are we accepting?
What You Get:
- ✓Clarity before you code
- ✓Context that survives the sprint
- ✓Decisions explained to future-you
- ✓Onboarding docs that write themselves
- ✓Team alignment on the "why"
Not a Blocker. A Gift to Future-You.
30 seconds now:
Capture why you're building this
30 minutes saved later:
When someone asks "why did we build it this way?"
Three Ways to Capture
Choose the method that fits your workflow. Use all three. Mix and match.
MCP Server
Real-time capture during Claude Code sessions
Setup:
5 minute setup
Prompts you: "Let me save what we just decided." Captures session summary, commits, chat links, and decisions as they happen.
Best for:
Git Hooks
Triggered on significant commits
Setup:
Works with any tool
When you commit >50 lines or use keywords, PCF asks: "Capture context for this commit?" Quick form saves decision summary alongside code.
Best for:
CLI Tool
Manual capture, query, and timeline
Setup:
npm install -g
Full control when you need it. Capture context manually, query past decisions, view timeline of changes. Works with any workflow.
Best for:
Example: Query with CLI
→ Date: 2024-11-15
→ Reason: Cost constraint (<£0.10/user)
→ Decided by: CTO
→ Trade-off: Less mature ecosystem than Firebase
Developer Edition Principles
Built by developers, for developers. No BS. No lock-in. Just context that works.
Git-Native
Context lives in your repo (.context/). Versions with your code. Fork, branch, merge like code. Works with GitHub, GitLab, Bitbucket.
Zero Lock-In
Standard JSON/Markdown format. No proprietary formats. Don't like our tools? Fork and build your own. Context is yours, always.
Tool-Agnostic
Works with Claude Code, Cursor, Windsurf, Cline, etc. MCP for Claude, CLI for everything else. Switch tools freely, context travels.
Team-First
Multi-participant capture (who said what). PR reviews include context changes. New team members get full story on clone. Shared understanding.
Minimal Friction
Capture takes 30 seconds, not 30 minutes. Auto-prompts at natural points. Optional, not mandatory. Query is instant: pcf query "auth"
What Your Context Looks Like
myproject/
src/ ← Your code
.context/ ← Your context
decisions/
2024-11-15-storage-choice.md
2024-11-20-auth-approach.md
discussions/
2024-11-15-team-sync.json
sessions/
2024-11-16-oauth-impl.json
constraints/
cost-per-user.md
privacy-requirements.md
trade-offs/
cloudflare-vs-firebase.mdStandard files. Standard git. Anyone can read it. Any tool can access it.
Team Onboarding That Actually Works
Imagine saying: "Clone the repo, everything's there—code and context."
Without PCF
New dev:
"Why did we build it this way?"
Current answer:
"Check the PR comments?"
(Scattered. Incomplete. Missing non-technical context.)
With PCF
New dev:
"Why Cloudflare?"
PCF answer:
Decision: Use Cloudflare for storage
Constraint: Cost must be <£0.10/user
Options considered: Firebase, Supabase, Cloudflare
Why Cloudflare: Free tier meets cost constraint
Decided by: CTO
Date: 2024-11-15
Trade-off accepted: Less mature ecosystem
→ Related discussion: team-sync-2024-11-15.json
Result: New teammates understand your reasoning, not just your code.
No more "check Slack from March" or "ask Sarah, she built that."
Everything's in the repo.
Get Early Access
Be among the first to build at AI speed with collective intelligence intact.