Fix duplicate skill docs and overly broad tarball cleanup

- Merge duplicate '## Skills' and '## Cursor Skills' sections in agent-setup.md
  into a single consolidated section with the most complete descriptions
- Fix tarball cleanup in packdep.js to use regex matching version number (digit)
  after prefix, preventing false matches on similarly-named packages
  (e.g., 'edge-core-' no longer matches 'edge-core-js-*.tgz')

Author: cursoragent

.cursor/skills/package-deps/scripts/packdep.js

@@ -69,9 +69,12 @@ for (const depDir of depDirs) {
 
   // Remove old tarballs for this package from the GUI directory.
   // Tarball names follow npm's convention: scoped "@foo/bar" → "foo-bar-*"
+  // Use regex to match version number (digit) after prefix to avoid matching
+  // similarly-named packages (e.g., "edge-core-" should not match "edge-core-js-*")
   const namePrefix = depName.replace(/^@/, '').replace(/\//, '-')
+  const prefixPattern = new RegExp(`^${namePrefix}-\\d.*\\.tgz$`)
   for (const file of fs.readdirSync(guiDir)) {
-    if (file.startsWith(namePrefix + '-') && file.endsWith('.tgz')) {
+    if (prefixPattern.test(file)) {
       console.log(`  Removing old tarball: ${file}`)
       fs.unlinkSync(path.join(guiDir, file))
     }

docs/agent-setup.md

@@ -30,17 +30,17 @@ Execute a planning document and iteratively refine the implementation until it p
 
 ## Skills
 
-Skills are defined in `.cursor/skills/` and are automatically invoked by Cursor when relevant. They can also be referenced from commands via `@.cursor/skills/<name>/SKILL.md`.
+Skills are defined in `.cursor/skills/` and provide reusable workflows that commands and other skills can invoke. They are also surfaced to the agent automatically and can be triggered directly.
 
 ### debug-edge
 
 Compile, launch, and debug the Edge wallet app on an iOS simulator.
 
 **Prerequisites**: Xcode, working directory `edge-react-gui`, MCP servers `xcodebuild` and `mobile-mcp`
 
-**Workflow**: Install deps → Clean iOS → Prepare iOS → Start Metro → Build and launch → Login if needed
+**Workflow**: Install deps → Clean iOS build artifacts → Prepare iOS → Clean Xcode build → Start Metro bundler → Build and launch app → Log into test account if needed
 
-**Tip**: For plugin repo debugging (edge-core-js, edge-currency-accountbased, edge-exchange-plugins, edge-currency-plugins), use `log.warn()` instead of `console.log` to see output in Metro logs.
+**Tip**: For plugin repo debugging (edge-core-js, edge-currency-accountbased, edge-exchange-plugins, edge-currency-plugins), use `log.warn()` instead of `console.log` to see output in Metro logs. Enable the corresponding `DEBUG_*` flag in `env.json` and run `yarn start` in the plugin repo for hot-reload.
 
 ### fix-code
 
@@ -58,31 +58,29 @@ Address reviewer comments on a GitHub pull request.
 
 **Usage**: Provide a GitHub PR URL or number.
 
-**Workflow**: Collect reviewer comments → Create fix plan → Pause for user iteration → Implement fixes with fixup commits → Push with `--force-with-lease`
+**Workflow**: Fetch reviewer comments → Filter actionable items → Create fix plan in `/tmp` → Pause for user approval → Implement each fix as a fixup commit (checkout original commit, edit, cherry-pick remaining) → Push with `--force-with-lease`
 
 **Constraints**: Does not auto-squash. Leaves fixup commits visible for reviewer.
 
-### package-deps
-
-Package local dependency repos and link them to edge-react-gui for testing.
+### gh-review
 
-**Usage**: Specify dependency repos to package.
+Orchestrate an interactive GitHub PR review session using the `gh` CLI.
 
-**Workflow**: `npm pack` → Rename with UTC timestamp → Copy to edge-react-gui → Update `package.json` reference
+**Prerequisites**: `gh` CLI installed and authenticated
 
-### review-code
+**Usage**: Provide a PR reference (URL, number, or "current PR") and comment instructions.
 
-Review code changes for quality and convention compliance.
+**Workflow**: Start or resume a pending review → Add inline comments interactively (single-line or multi-line) via GraphQL API → Present summary of all comments → Submit only after explicit user confirmation as APPROVE, COMMENT, or REQUEST_CHANGES
 
-**Usage**: Provide a GitHub PR URL, PR number, local branch name, or "current branch".
+**Key detail**: Uses GraphQL `addPullRequestReviewThread` for incremental comments because the REST API returns 422 when a pending review already exists.
 
-**Workflow**: Checkout code → Get diff → Launch review subagents (`review-react`, `review-errors`, `review-state`, etc.) → Compile findings → Save to `/tmp` → For PRs: submit inline comments via GitHub MCP
+### package-deps
 
----
+Package local dependency repos and link them to edge-react-gui for testing.
 
-## Cursor Skills
+**Usage**: Specify dependency repos to package.
 
-Skills are defined in `.cursor/skills/` and provide reusable workflows that commands and other skills can invoke. They are also surfaced to the agent automatically and can be triggered directly.
+**Workflow**: `npm pack` → Rename with UTC timestamp → Copy to edge-react-gui → Update `package.json` reference
 
 ### review-code
 
@@ -94,56 +92,6 @@ Review code changes for quality and convention compliance. Supports both GitHub
 
 ---
 
-### fix-pr
-
-Address reviewer comments on a GitHub pull request.
-
-**Usage**: Provide a GitHub PR URL or number.
-
-**Workflow**: Fetch reviewer comments → Filter actionable items → Create fix plan in `/tmp` → Pause for user approval → Implement each fix as a fixup commit (checkout original commit, edit, cherry-pick remaining) → Push with `--force-with-lease`
-
-**Constraints**: Does not auto-squash. Leaves fixup commits visible for reviewer.
-
----
-
-### fix-code
-
-Implement fixes from a plan document by editing code.
-
-**Usage**: Provide a plan document path (typically generated by `fix-pr` or `review-code`).
-
-**Workflow**: Parse plan → Edit files → Run `yarn precommit` → Present summary
-
-**Constraints**: Does not commit or push. Leaves changes unstaged for user review.
-
----
-
-### debug-edge
-
-Compile, launch, and debug the Edge wallet app on an iOS simulator.
-
-**Prerequisites**: Xcode, working directory `edge-react-gui`, MCP servers `xcodebuild` and `mobile-mcp`
-
-**Workflow**: Install deps → Clean iOS build artifacts → Prepare iOS → Clean Xcode build → Start Metro bundler → Build and launch app → Log into test account if needed
-
-**Tip**: For plugin repo debugging (edge-core-js, edge-currency-accountbased, edge-exchange-plugins, edge-currency-plugins), use `log.warn()` instead of `console.log` to see output in Metro logs. Enable the corresponding `DEBUG_*` flag in `env.json` and run `yarn start` in the plugin repo for hot-reload.
-
----
-
-### gh-review
-
-Orchestrate an interactive GitHub PR review session using the `gh` CLI.
-
-**Prerequisites**: `gh` CLI installed and authenticated
-
-**Usage**: Provide a PR reference (URL, number, or "current PR") and comment instructions.
-
-**Workflow**: Start or resume a pending review → Add inline comments interactively (single-line or multi-line) via GraphQL API → Present summary of all comments → Submit only after explicit user confirmation as APPROVE, COMMENT, or REQUEST_CHANGES
-
-**Key detail**: Uses GraphQL `addPullRequestReviewThread` for incremental comments because the REST API returns 422 when a pending review already exists.
-
----
-
 ## Best Practices
 
 1. **Monitor Metro bundler** when debugging—JavaScript logs appear there