Skip to content

Count page views and project clicks with PostHog (EU servers)? It loads only if you choose Allow. Privacy

All projects

Solo Empire CLI

Run the daily operations of a one-person studio from one checked-in toolkit, not scattered scripts.

Daily operations ran on ad-hoc scripts spread across folders, with no shared tests or entry point.

Tech Domain · Book Dev|Published|Evidence: Internal System|Python, TypeScript, Taskfile, SQLite

An internal system; this case study is the public evidence.

No public demoView source

Case Study

Before

Daily operations (tasks, goals, habits, SEO reports, registries, sync jobs) ran on scripts spread across one large workspace.

After

One toolkit with `task test` and a strict quality gate that runs offline. Tests that need a sibling repository skip with a visible SKIP line.

How it's solved

Split the tooling into its own repository: Python scripts for the daily workflows, a TypeScript owner CLI (infra/cli.ts), registries, integration clients and an offline test suite run through Taskfile tasks.

Trade-offs

Built around one operator's layout and sibling repositories; there is no CI workflow yet, so checks run locally.

Related Articles

Further reading on related topics from the blog

Related Projects

More in Tech Domain · Book Dev