Mate-managed Claude Code hooks: artifact-path guardrail, session banner, and companion guidance. Ships inside @uniqbit/mate-core and is never published separately. A managed launch loads it with --plugin-dir; a wrapped repository instead inlines the guard and guidance commands into its settings, with ${CLAUDEPLUGINRO.
★not rated 12
changed 1mo agoA
tokens not measured
originalMIT
Build a project domain model using Mate context-map scope and Companion Repository artifacts. Loaded by mate-grill-with-docs; do not start on your own.
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
Explain the current topic, the applied change, or a named spec capability in a browser-rendered Mate report. Use only when the user explicitly invokes the skill to see how something works, what a change did, what a spec capability specifies, or wants a diagram, call tree, or rendered diff of the current work.
Verify React changes with Mate's pinned React Doctor. Use when a task is tagged [skill:mate-react-doctor], when the shared Mate verification rules call for it before finishing an OpenSpec change, or when the user asks to scan, check, or triage React diagnostics for the current changes.
Implement a change on a recorded delivery branch, offering change/ instead of a protected branch. Builds on the OpenSpec apply workflow. Use when the user wants to implement, apply, or continue implementing a reviewed change.
Archive a change through mate artifact archive, which records its delivery, reports merge state and its warnings, and runs the OpenSpec archive, also before the merge. Use when the user wants to archive, finalize, or close out an implemented change.
Reverse-engineer an OpenSpec spec for one existing feature and write it directly to the canonical spec, ready to publish. Use when the user wants to backfill, document, or spec existing or legacy behavior that has no spec yet.
Pick the pre-explore mode a request needs (interview, grilling, or skip) from what it already states, then run that one mode. Use only when the user explicitly starts clarifying an idea before exploring a change.
Explore a change with its Working Repository and Area resolved from the companion context map, and suggest slicing a large feature into several changes. Builds on the OpenSpec explore workflow. Use when the user wants to explore, investigate, or think through a change before proposing it.
Propose a change with its schema chosen by the minimal eligibility test (mate-minimal or mate-v1) and one change per agreed slice. Builds on the OpenSpec propose workflow. Use when the user wants to turn an explored direction into a change proposal, or revise an existing change's plan.
Discover, select, and publish archived OpenSpec changes and drifted canonical specs through mate artifact publish, holding back archives whose delivery branch is not merged. Use when the user wants to publish, ship, or push archived artifacts and anchor each one with a dated revert tag.
★not rated 12 todayA61 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: