Why uze
Agents come and go; your work stays
Every coding agent has its own plugin format, its own skills directory and its own instructions file. Keep the same skill or the same project rules for four of them and you maintain four copies, each drifting on its own.
Run more than one at a time and they collide: two agents editing one checkout, with your own uncommitted work in the middle.
Everything here starts from one idea: agents come and go; your work stays. Whatever you use today will not be what you use in a year, so nothing you invest in should be tied to one of them.
What follows from it
The first two shape the package manager, the third shapes the workspace, and the last holds for both.
Standards, not another format. A plugin is an Agent Plugin, a skill is an
Agent Skill, instructions are AGENTS.md. The open standards are adopted as they are, and uze
invents only what none of them covers. Standards →
Each agent's own way in. A plugin reaches an agent through the most native mechanism that agent has. When one cannot carry something, uze says so instead of faking it. How delivery works →
Git is the source of truth. Where an agent's work stands is read from its branch, never from what the agent claims. An agent works in a checkout of its own, and its work comes home through a rebase and your checks.
Yours stays yours. uze writes only what it can prove it owns, inside blocks it marks. Anything else it finds changed, it reports and leaves alone.