with one click
unimatrix
unimatrix contains 16 collected skills from dug-21, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Version bump, changelog generation, tag, and push to trigger the release pipeline.
Manage a goal's capability map in Unimatrix — the behaviorally-proven units that must exist for a goal to be delivered. Decompose goals into capabilities, track delivery status, and report what's left. Status advances to proven ONLY on attached behavioral evidence.
Unimatrix Zero — vision guide mode. Strategic advisor for product evolution, feature ordering, vision alignment, security posture, and codebase health. Conversational. Does not modify application code or run delivery protocols.
Post-merge retrospective — extracts patterns, procedures, and lessons from shipped features into Unimatrix. Use after a feature PR is merged.
Store an architectural decision record in Unimatrix. ADRs live in Unimatrix only — no ADR files. Use after each design decision.
Ad-hoc independent product-lens review via uni-zero-reviewer. Use for re-reviews after rework or reviews outside protocol runs. Advisory only — human makes the call.
Store an architectural decision record in Unimatrix. ADRs live in Unimatrix only — no ADR files. Use after each design decision.
Initialize Unimatrix in a repository: append knowledge block to CLAUDE.md and produce agent orientation recommendations.
Populate Unimatrix with foundational repository knowledge through human-directed, gated exploration.
Deterministic lookup of Unimatrix knowledge by exact filters. Use when you know what you want — a specific feature, category, entry ID, or status.
Semantic search across Unimatrix knowledge. Use when exploring a topic, looking for related decisions, patterns, or conventions.
Query Unimatrix for component patterns, procedures, and conventions before designing or implementing. Use BEFORE writing pseudocode or code.
Store a lesson learned from a failure, gate rejection, or unexpected issue. Use after bugfixes and gate failures to prevent recurrence.
Store a reusable implementation pattern in Unimatrix. Use when you discover a gotcha, trap, or reusable solution that future agents should know.
Store or update a technical procedure (how-to) in Unimatrix. Use during retrospectives when a technique has evolved or been discovered.
PR security review and merge readiness check. Use after delivery or bugfix opens a PR, or standalone when human wants to review a PR.