Portfolio

Open-source tool · Developer experience + AI agents

Klosti

Claude Code, Codex, Cursor, and Gemini each read their own rule files, skills, hooks, and MCP servers. Spread across home folders and projects, nobody sees them all. Klosti maps them, and finds where they disagree.

My role. I designed and built it: the engine, the CLI, the macOS app, and the brand.

The question

A global rule says one thing. A project rule says the opposite. A skill quietly asks for a third. The agent picks one and nobody notices. How do you see what an agent actually loads, in the order it loads it?

The decision

Draw load order as a thread. Global, plugins, then project. Rule files are beads on it. A contradiction is a knot that ties the files involved. Fixes happen in place, with a backup and an undo.

The build

One command: npx klosti. A local scanner reads agent settings and code folders, masking anything that looks like a credential. An AI review, run through your own Claude Code, checks skills against rules and each other. Results are cached by content. A menu bar app watches for changes and says when your setup moves.

A rule you cannot see is a rule you cannot trust.

TypeScript · Node.js · Tauri · Claude · Next.js