Software Projects
MOSAIC
MOSAIC is an open-source Obsidian workspace where people and AI agents can organize knowledge, run projects and reuse skills. I designed it around one shared operating layer, so the workflow can move between AI providers while the notes and rules stay together.
Why I built it
As I used AI for different kinds of work, the surrounding context mattered as much as the prompt: where information belonged, which instructions applied and what a completed task should look like. MOSAIC turns that working structure into a reusable workspace built from plain Markdown files.
What it does
- Guided setup adapts the workspace to the person's recurring work, with separate choices for skills, templates and workflows.
- Inbox triage and weekly reviews connect captured material to projects, knowledge and next actions.
- One skill library holds reusable capabilities, with tools to discover, create and validate additional skills.
- A workspace health check reports broken links, missing note types, stalled projects and a stale inbox.
One operating layer across agents
The canonical instructions live in 00_MOSAIC, alongside the skill library, navigation maps and workflow protocols. Thin adapters point Codex, Claude Code, GitHub Copilot, Gemini CLI and Google Antigravity to that same source. This avoids maintaining a separate copy of the system for each client. It requires a file-aware agent; other clients can use the documented bootstrap prompt.
My role and the use of AI
I own the product direction, requirements, review criteria and release decisions. AI agents have provided extensive support with research, drafting, implementation, testing and iteration. My work is in designing the system, deciding how its parts fit together and reviewing the resulting behavior and documentation.
Validation and private data
Python tools check release structure, configuration, links, portable skills and third-party provenance. Separate test suites cover skill tooling and workspace health checks. Personal configuration and profiles stay in an ignored local folder; setup also explains how to keep notes out of a public repository. Changes to core rules follow an explicit review process.
Try it
Clone or download the repository, open it as an Obsidian vault, and ask a supported agent to set up MOSAIC. The workspace uses plain Markdown and Obsidian's core features, with no community plugins required. Python is needed only for the maintenance tools. Original MOSAIC material is MIT-licensed, with separate notices for bundled third-party material.