Skip to content

CONTEXT.md

Latest commit

 

History

History
49 lines (35 loc) · 2.29 KB

CONTEXT.md

File metadata and controls

49 lines (35 loc) · 2.29 KB

Unic Agents Plugins — Monorepo Context

A pnpm workspace monorepo for developing and releasing AI agent extensions built at Unic. This context covers vocabulary that cuts across all plugins in the repo.

Language

Plugin: An agent extension that ships as a bundle of commands, hooks, agents, and/or skills. Agent-agnostic — a Plugin may target Claude Code, GitHub Copilot, or any other agent runtime. Avoid: extension, add-on, integration

Claude Code Plugin: A Plugin that targets the Claude Code runtime and ships as a .claude-plugin bundle. Avoid: Claude plugin (ambiguous), Claude extension

Workspace Package: An internal shared library under packages/ that supports Plugin development. Not user-facing; never installed by a Consumer. Avoid: package (too generic), library, module

Release: A versioned, tagged snapshot of a single Plugin published to main. A per-Plugin event — there is no monorepo-wide release. Avoid: deploy, publish, version bump

Feature: A self-contained unit of work tracked as a directory under docs/issues/<slug>/, containing a PRD and numbered implementation issues. The atomic input to the Feature Runner. Avoid: ticket, epic, story

Feature Runner: The skill that implements a Feature's issues end-to-end in one worktree, branch, and pull request. Backed by unic-dlc-build. Avoid: issue runner, queue runner

Consumer: A repository that installs and uses a Plugin. External to this monorepo. Avoid: client, user repo, target repo, host repo

Relationships

  • A Plugin belongs to one agent ecosystem (e.g., Claude Code) and has zero or more Releases
  • A Claude Code Plugin is a Plugin — the inverse is not always true
  • A Workspace Package supports Plugin development but is not itself a Plugin
  • A Feature drives one Feature Runner execution
  • A Consumer installs one or more Plugins

Example dialogue

Dev: "Should we cut a Release for all Plugins when we bump a Workspace Package?" Domain expert: "No — a Release is per-Plugin. Workspace Packages don't have their own Releases."

Dev: "A Consumer reported the auto-format Plugin failing on Windows." Domain expert: "That's a cross-platform gap. Plugins must use Node.js APIs — no shell commands or POSIX paths."