How I built an AI copilot that runs my life as a solo builder

The problem

When you work alone, nobody reminds you to document, follow up with a prospect, post on LinkedIn, or stop spending 6 hours on a side project that generates zero revenue.

I built a system with Claude Code that does all of that. Not a chatbot. A real copilot that knows my projects, my schedule, my clients, my past mistakes, and calls me out when I drift.

This post documents the entire system. Every file, every workflow, every design decision.

Overview

The system is called Liberty. It’s a local folder that transforms Claude Code into a daily copilot.

What it does:

• Automatic end-of-day recap (cross-referencing Notion + Calendar + Kanban)
• Business tracking: prospects, invoices, follow-ups, alerts
• LinkedIn content generation (2 variants per post)
• Automated competitive intelligence (LinkedIn, Instagram, Reddit)
• Learning extraction: every mistake Claude makes, it never makes again
• Proactive check-in: it knows what time it is and what you should be doing

What it uses:

• Claude Code (terminal)
• Notion (central database)
• Google Calendar (schedule)
• Unipile API (LinkedIn)
• Apify (Instagram/Reddit scraping)
• Airtable (media cache)

Project structure:

liberty/
├── CLAUDE.md                    # Copilot instructions
├── .mcp.json                    # External service connections
├── scripts/hooks/               # 3 activity hooks
├── .claude/
│   ├── commands/                # 12 slash commands
│   └── agents/                  # 6 specialized agents
└── memory/                      # Persistent memory
    ├── MEMORY.md                # Main context
    └── learnings.md             # Scored learnings

1. CLAUDE.md: the system’s brain

This is the most important file. Claude Code reads it at the start of every session. It defines who you are, how it should behave, and what rules to follow.

What it contains

Your profile:

- Solo builder in career transition (ex-freelance CTO → indie builder)
- Dual priority: n8n/AI training (immediate cash) + product building (long term)

Why this matters: Claude adapts its suggestions to your context. If you’re a senior dev, it doesn’t explain basics. If you need cash, it reminds you not to over-build.

Data sources:

### Notion
- Dev Kanban: collection <your-collection-id>
  Statuses: Backlog → Todo → In progress → Review → Done → Archive
- Daily log "my notes": collection <your-collection-id>

### Google Calendar
- Main calendar for meetings, calls, training, deadlines

Every command knows exactly where to find information in Notion. No searching, no ambiguity.

Operating rules:

1. Always speak in French
2. Be direct and critical, no people-pleasing
3. Prioritize cash, training comes before building
4. Log everything, every notable action must be tracked
5. Don't guess, go fetch the info
6. Suggest improvements

Rule 3 is the most important. Without it, Claude lets you code for 8 hours on a side project without saying a word. With it, it pulls you back.

2. Commands: 12 actions in one line

Each command is an .md file in .claude/commands/. When you type /daily-recap, Claude reads the file and executes the workflow described in it.

/copilot-pulse: the automatic check-in

This is the startup command. It checks the time, your schedule, and applies rules:

Condition	Action
Before 10am	”LinkedIn routine first. Before coding.”
7:30pm-10pm	”Run /learn then /daily-recap.”
/learn forgotten > 2 days	Insistent mode. Refuses to continue.
Long session with no cash link	”You’ve been building for a while. Cash first.”
Session start	Display schedule + priority tasks

The insistent mode is intentional. If you haven’t run /learn in 2 days, Claude literally blocks the conversation. It’s the only way to enforce discipline when you work alone.

/daily-recap: the end-of-day summary

Crosses three sources:

1. Today’s Google Calendar events
2. Modified Kanban tasks (Done, In progress)
3. Today’s note in Notion

Generates a structured recap and pushes it to Notion:

## Recap 03/11/2026

### Done today
- Claudehub.fr: complete init (Astro 6 + React 19 + Supabase)
- 14 commits, from zero to near-complete SaaS

### In progress
- Supabase Auth: GitHub OAuth to activate

### Tomorrow's todo
- [ ] [P1] LinkedIn routine
- [ ] [P1] Prep Client B call 3pm
- [ ] [P2] Continue claudehub.fr

### Day score
- Productivity: 5/5
- Training progress: 0/5
- Build progress: 5/5

The score is honest. If you’ve done nothing for cash, it shows.

/learn: the self-improving memory

This is the most underrated command. At the end of a session, it analyzes everything that happened and extracts three types of learnings:

Corrections (weight 3): moments you corrected Claude

[score: 2] Notion multi-select: send each value separately,
not a comma-separated string. API rejects "AI, n8n" but accepts "AI".

Patterns (weight 2): approaches that work

[score: 2] HTML single-file infographic (1080x1350) + Puppeteer screencast
= efficient pipeline for animated LinkedIn content.

Decisions (weight 1): business/tech choices

[03/11] Human Agency: we do NOT sell packages but change management consulting.

Each learning has a score. If Claude makes the same mistake again, the score goes up. At 3, the learning gets promoted to main memory (MEMORY.md) and becomes permanent.

Result: after 10 sessions, Claude knows your Notion conventions, design preferences, intelligence filters, business contacts. It stops asking the same questions.

/linkedin-post: 2 variants in 30 seconds

Grabs the day’s context (Kanban, daily log, Calendar) and generates two posts:

• Variant A (safe): factual, value-oriented
• Variant B (polarizing): strong opinion, provokes reaction

Strict rules: max 1200 characters, zero hashtags, zero em dashes (AI marker), authentic dev-sharing tone, no influencer vibes.

/pipeline: the business dashboard

## Business Pipeline - 03/12/2026

### Hot prospects
| Name              | Amount  | Status          | Follow-up |
| Client A          | €X,000  | Negotiation     | 03/15     |
| Client B          | ?       | First contact   | Today     |

### Overdue follow-ups
| Name            | Planned | Overdue | Contact            |
| Client C        | 03/11   | 1d      | contact@client.com |

### Metrics
- Signed revenue this month: €0
- Revenue in negotiation: €X,000

Automatic alerts: follow-up > 7 days = red, unpaid invoice > 30 days = red, cold prospect > 14 days = suggestion.

Other commands

Command	Function
/log-today	Create/update today’s note in Notion
/todo-update	Update Kanban statuses
/plan-tomorrow	Prepare tomorrow’s todo (Calendar + Kanban)
/veille	Scrape Instagram + Reddit via Apify
/veille-linkedin	Search trending LinkedIn posts (Unipile)
/weekly-review	Weekly review with metrics and retrospective
/inspiration	Mantras and reminders when you doubt