chore(perps): prefix all perps skill names with perps-

abretonc7s · abretonc7s · commit f6eec5c661e9 · 2026-06-30T21:03:47.000+02:00
Rename perps domain skills so they share a perps- prefix and are
easily identifiable in lists and installed names (mms-perps-*).

- breakdown-perps-tickets   -&gt; perps-breakdown-tickets
- fix-perps-bug             -&gt; perps-fix-bug
- review-perps-pr           -&gt; perps-review-pr
- validate-perps-multiproject -&gt; perps-validate-multiproject
- write-perps-ticket        -&gt; perps-write-ticket

Updates skill dirs, frontmatter name, repos/*.md parent fields, and
all cross-skill references in skill bodies.
diff --git a/domains/perps/skills/perps-breakdown-tickets/skill.md b/domains/perps/skills/perps-breakdown-tickets/skill.md
@@ -1,5 +1,5 @@
 ---
-name: breakdown-perps-tickets
+name: perps-breakdown-tickets
 description: Interactively break a perps product requirement into split, dispatch-ready technical tickets across MetaMask Core, its release, Mobile, and Extension. Use when a product manager (or a codebase-aware Claude acting for one) has a perps bug or feature and needs engineering-grade tickets, correctly routed now that @metamask/perps-controller is the Core source of truth. Triages where the change actually lives, emits only the applicable layer tickets with dependency links, and enforces token-efficient, signal-over-noise tickets agents can act on directly.
 maturity: experimental
 ---
@@ -171,4 +171,4 @@ Layer specifics:
 - `knowledge/screens.md` — route/component names for the "Affected" field.
 - `knowledge/formatting-rules.md` — perps number/precision rules for acceptance criteria.
 - `knowledge/shared-package-analysis.md` — duplicated utilities to check both sides.
-- Related skills: `fix-perps-bug` (implement a client fix), `review-perps-pr` (review the resulting PRs).
+- Related skills: `perps-fix-bug` (implement a client fix), `perps-review-pr` (review the resulting PRs).
diff --git a/domains/perps/skills/perps-fix-bug/repos/core.md b/domains/perps/skills/perps-fix-bug/repos/core.md
@@ -1,6 +1,6 @@
 ---
 repo: core
-parent: fix-perps-bug
+parent: perps-fix-bug
 ---
 
 ## File Paths
diff --git a/domains/perps/skills/perps-fix-bug/repos/metamask-extension.md b/domains/perps/skills/perps-fix-bug/repos/metamask-extension.md
@@ -1,6 +1,6 @@
 ---
 repo: metamask-extension
-parent: fix-perps-bug
+parent: perps-fix-bug
 ---
 
 ## File Paths
diff --git a/domains/perps/skills/perps-fix-bug/repos/metamask-mobile.md b/domains/perps/skills/perps-fix-bug/repos/metamask-mobile.md
@@ -1,6 +1,6 @@
 ---
 repo: metamask-mobile
-parent: fix-perps-bug
+parent: perps-fix-bug
 ---
 
 ## File Paths
diff --git a/domains/perps/skills/perps-fix-bug/skill.md b/domains/perps/skills/perps-fix-bug/skill.md
@@ -1,5 +1,5 @@
 ---
-name: fix-perps-bug
+name: perps-fix-bug
 description: Debug and fix perps feature bugs
 maturity: stable
 ---
diff --git a/domains/perps/skills/perps-review-pr/repos/core.md b/domains/perps/skills/perps-review-pr/repos/core.md
@@ -1,6 +1,6 @@
 ---
 repo: core
-parent: review-perps-pr
+parent: perps-review-pr
 ---
 
 ## File Paths
diff --git a/domains/perps/skills/perps-review-pr/repos/metamask-extension.md b/domains/perps/skills/perps-review-pr/repos/metamask-extension.md
@@ -1,6 +1,6 @@
 ---
 repo: metamask-extension
-parent: review-perps-pr
+parent: perps-review-pr
 ---
 
 ## File Paths
diff --git a/domains/perps/skills/perps-review-pr/repos/metamask-mobile.md b/domains/perps/skills/perps-review-pr/repos/metamask-mobile.md
@@ -1,6 +1,6 @@
 ---
 repo: metamask-mobile
-parent: review-perps-pr
+parent: perps-review-pr
 ---
 
 ## File Paths
diff --git a/domains/perps/skills/perps-review-pr/skill.md b/domains/perps/skills/perps-review-pr/skill.md
@@ -1,5 +1,5 @@
 ---
-name: review-perps-pr
+name: perps-review-pr
 description: >-
   Pre-flight self-review gate for perps PRs. A perps dev runs it on their OWN PR to drive a
   looping double-agentic cross-review — two different model CLIs (Claude, Codex, Cursor)
diff --git a/domains/perps/skills/perps-validate-multiproject/scripts/perps-validate.sh b/domains/perps/skills/perps-validate-multiproject/scripts/perps-validate.sh
diff --git a/domains/perps/skills/perps-validate-multiproject/skill.md b/domains/perps/skills/perps-validate-multiproject/skill.md
@@ -1,5 +1,5 @@
 ---
-name: validate-perps-multiproject
+name: perps-validate-multiproject
 description: Interactively validate perps changes across local MetaMask Core, Mobile, and Extension checkouts. Use when a Core @metamask/perps-controller change must be checked in Mobile/Extension, or when a Mobile/Extension perps change needs parity validation in the other client. Defaults to current checkout as owner, yalc for Core package transport, read-only validation targets, and the smallest meaningful proof; asks the user only when required folders or proof level cannot be resolved.
 maturity: stable
 ---
diff --git a/domains/perps/skills/perps-write-ticket/skill.md b/domains/perps/skills/perps-write-ticket/skill.md
@@ -1,6 +1,6 @@
 ---
-name: write-perps-ticket
-description: Interactively author one clean, complete perps ticket — bug, EPIC, or initiative — that states intent and expected outcome without implementation. Use when a PM (or a Claude acting for one) has a raw perps observation, feature idea, or strategic goal and wants a single well-formed ticket ready for engineering to break down. This is the first (product) pass; the engineering split + layer routing is a separate pass (breakdown-perps-tickets). Captures what/expected/repro, makes the ticket surfaceable so it doesn't get lost, and stops before implementation or repo routing.
+name: perps-write-ticket
+description: Interactively author one clean, complete perps ticket — bug, EPIC, or initiative — that states intent and expected outcome without implementation. Use when a PM (or a Claude acting for one) has a raw perps observation, feature idea, or strategic goal and wants a single well-formed ticket ready for engineering to break down. This is the first (product) pass; the engineering split + layer routing is a separate pass (perps-breakdown-tickets). Captures what/expected/repro, makes the ticket surfaceable so it doesn't get lost, and stops before implementation or repo routing.
 maturity: experimental
 ---
 
@@ -18,10 +18,10 @@ the product team can file and engineering can break down as-is. You describe
 
 This is the **first (product) pass**. The technical split — which repos/layers
 change, dependency order, component routing — is the engineer's job and lives in
-`breakdown-perps-tickets`. Do not do it here.
+`perps-breakdown-tickets`. Do not do it here.
 
 Not for: engineering task breakdown, or routing a ticket across Core/clients
-(→ `breakdown-perps-tickets`).
+(→ `perps-breakdown-tickets`).
 
 ## Operating principle: intent, not implementation
 
@@ -56,7 +56,7 @@ Ask which kind, or infer it and confirm. Each has its own shape:
 3. **Draft the ticket** in the matching format below.
 4. **Make it surfaceable** (see below) so it doesn't vanish into the backlog.
 5. **Stop at the product boundary.** Do not add implementation, file paths, or a
-   layer split. Hand off: a bug/EPIC is ready for `breakdown-perps-tickets`.
+   layer split. Hand off: a bug/EPIC is ready for `perps-breakdown-tickets`.
 
 ## Surfacing (so bugs don't get lost)
 
@@ -124,7 +124,7 @@ tickets). Leave open if not yet decided.
 
 ## Handoff
 
-A bug or EPIC produced here is the **input** to `breakdown-perps-tickets`, which
+A bug or EPIC produced here is the **input** to `perps-breakdown-tickets`, which
 (with codebase access) routes it across Core/Core-release/Mobile/Extension and
 emits the engineering task tickets. Keep this skill on the product side of that
 line.
@@ -135,5 +135,5 @@ line.
   surface labels (optional; plain words are fine for a product ticket).
 - `../../knowledge/formatting-rules.md` — number semantics, to describe expected
   values correctly without prescribing decimals.
-- Related skills: `breakdown-perps-tickets` (engineering split + routing — the
-  next pass), `fix-perps-bug` (implement a fix).
+- Related skills: `perps-breakdown-tickets` (engineering split + routing — the
+  next pass), `perps-fix-bug` (implement a fix).
