Skip to content

ONBOARDING.md

Latest commit

 

History

History
97 lines (70 loc) · 6.88 KB

ONBOARDING.md

File metadata and controls

97 lines (70 loc) · 6.88 KB
Raw

Welcome to Unic Agent Plugins

How We Use Claude

Based on Oriol Torrent Florensa's usage over the last 30 days (178 sessions):

Work Type Breakdown:

  • Improve Quality ████████░░░░░░░░░░░░ 41%
  • Build Feature ██████░░░░░░░░░░░░░░ 28%
  • Plan & Design ███░░░░░░░░░░░░░░░░░ 13%
  • Debug Fix ██░░░░░░░░░░░░░░░░░░ 10%
  • Write Docs ██░░░░░░░░░░░░░░░░░░ 8%

Top Skills & Commands:

  • /grill-with-docs ████████████████████ 22x/month
  • /triage ██████████████░░░░░░ 15x/month
  • /archon ████████████░░░░░░░░ 13x/month
  • /to-issues ████████░░░░░░░░░░░░ 9x/month
  • /tdd ██████░░░░░░░░░░░░░░ 7x/month
  • /plugin-dev:skill-development █████░░░░░░░░░░░░░░░ 6x/month
  • /skills █████░░░░░░░░░░░░░░░ 6x/month
  • /archon-rollout ████░░░░░░░░░░░░░░░░ 5x/month
  • /to-prd ████░░░░░░░░░░░░░░░░ 5x/month
  • /zoom-out ████░░░░░░░░░░░░░░░░ 5x/month

Top MCP Servers:

  • Context7 ████████████████████ 4 calls

Your Setup Checklist

Codebases

MCP Servers to Activate

  • Context7 — fetches current docs for libraries, frameworks, SDKs and CLI tools (so answers reflect recent API changes, not stale training data). It ships via the context7 plugin; set CONTEXT7_API_KEY (or run npx ctx7@latest login) for higher rate limits.
  • Figma Dev Mode MCP — optional, only needed when using unic-spec-review to review Figma designs; the /unic-spec-review:spec-doctor command fails loud if a pasted Figma link needs it and it is not connected.
  • Playwright MCP — optional, only needed when using unic-spec-review to inspect a live production system; likewise checked by /unic-spec-review:spec-doctor.

Skills to Know About

  • /grill-with-docs — adversarial grilling of a plan against the project's domain model and ADRs, updating CONTEXT.md/ADRs inline as decisions firm up. The team's most-used skill: it stress-tests PR findings and locks designs before any code is written.
  • /triage — moves issues through the 8-state triage workflow; the default for "where do I stand" on open issues and prepping work for an AFK agent.
  • /archon — runs AI workflows in isolated git worktrees for parallel development; the basis of the team's custom delivery harness.
  • /archon-rollout — dispatches archon-fix-github-issue per issue respecting the dependency tree, with standing guardrails and a deduped monitor; the team's way of shipping a chain of ready-for-agent issues.
  • /to-issues — breaks a plan or PRD into independently-grabbable issues using tracer-bullet vertical slices.
  • /to-prd — turns the current conversation into a PRD and publishes it to the issue tracker.
  • /tdd — test-first red-green-refactor loop for building features and fixing bugs.
  • /plugin-dev:skill-development — guidance for authoring and improving Claude Code skills.
  • /zoom-out — step back and orient on a tangle of changes or untracked files.
  • /unic-pr-review:review-pr — multi-agent Azure DevOps PR review (intent checking, Confidence-scored Findings, interactive Approval Loop); the v2 successor to the deprecated pr-review plugin.
  • /unic-spec-review:review-spec — adversarial eleven-agent review of Confluence web specs (plus Figma and live-system sources), posting selected Findings back as Confluence comments.

Team Tips

  • Gitflow, always via PR. Branch from develop, PR back to develop; main only takes release merges. Use feature/<name> for all develop-targeting work (features and bugs); hotfix/ is reserved for fixes branched off main. Small doc/housekeeping changes can go straight to develop.
  • Run the verification loop before pushing. pnpm ci:check (not just pnpm format — Biome's import sorting is not auto-fixed by format), then pnpm test and pnpm typecheck. CI runs all three OSes × Node 22/24, so check cross-platform assumptions (use node:path/node:fs, not shell commands).
  • Versioning is scripted. Bump with pnpm --filter <plugin> bump <patch|minor|major> — never hand-edit marketplace.json. CHANGELOG headers must be ## [X.Y.Z] — YYYY-MM-DD, and verify:changelog gates any PR that touches guarded files (commands, scripts, plugin.json, plugin README.md).
  • Never create or delete LICENSE files — the maintainer manages those by hand in every package.
  • Spec-first delivery. Work flows /grill-with-docs → /to-prd → /to-issues → /archon-rollout. Only ready-for-agent issues with locked acceptance criteria get dispatched to an agent.
  • Trust CI on GitHub, not an agent's self-report. When an Archon run reports "all green / mergeable," confirm with gh pr checks <n> before merging — the run summary and its exit code can both mislead.

Get Started

A good first task is getting the workspace green locally:

  1. pnpm install
  2. pnpm ci:check && pnpm test && pnpm typecheck — all should pass on a clean develop.
  3. Skim CONTEXT-MAP.md at the repo root to see the bounded contexts, then read one plugin's CONTEXT.md and its docs/adr/ to learn how decisions are recorded.

From there, run /triage to see where open issues stand, and pick up a ready-for-agent issue or pair on a triage pass.