What it took to get a learning app into Claude's connector directory

Braineos is now listed in Claude's connector directory. Here's what the review looked at, and what we changed to pass it.

Planning backwards from an exam date

How we built Braineos's study planner: one pure function shared by a public page and a signed-in card, plans that never shift, and why it gives no minutes-per-day figure.

One answer log, three readers

How Braineos started keeping every answer, why we chose a log over running counters, and how one read side feeds the progress page, CertBrain's readiness panel and the Claude connector.

Learning a codebase with flashcards and Claude Code

We built a Claude Code plugin that turns a folder of code into a spaced-repetition deck of its key concepts. Here's why, and what makes a good card about code.

One pipeline, many sites: our Docker and Woodpecker setup

How a small studio deploys several independent apps from one CI server and one modest droplet, and the scheduling gotcha that silently stopped a site from deploying.

Two events and a funnel: what we measure with PostHog

Why our apps track only a sign-up and one meaningful first action, why we chose PostHog Cloud over self-hosting, and the questions that small setup answers.

How we run a team of AI coding agents

Several Claude Code sessions working at once, across several apps. The roles, the shared issues repo, and the status files and decisions log that keep them coordinated.

Async development with Claude Code's Remote Control

Starting agent work at the desk and checking in from a phone. How we use Remote Control to keep long-running coding sessions moving away from the keyboard.