monomind 2.7.12 → 2.7.14

package/packages/@monomind/cli/.claude/skills/monolean-review/SKILL.md

@@ -1,57 +0,0 @@
----
-name: monolean-review
-description: >
-  Code review focused exclusively on over-engineering. Finds what to delete:
-  reinvented standard library, unneeded dependencies, speculative abstractions,
-  dead flexibility. One line per finding: location, what to cut, what replaces
-  it. Use when the user says "review for over-engineering", "what can we
-  delete", "is this over-engineered", "simplify review", or invokes
-  /monolean-review. Complements correctness-focused review, this one only
-  hunts complexity.
----
-
-Review diffs for unnecessary complexity. One line per finding: location, what
-to cut, what replaces it. The diff's best outcome is getting shorter.
-
-## Format
-
-`L<line>: <tag> <what>. <replacement>.`, or `<file>:L<line>: ...` for
-multi-file diffs.
-
-Tags:
-
-- `delete:` dead code, unused flexibility, speculative feature. Replacement: nothing.
-- `stdlib:` hand-rolled thing the standard library ships. Name the function.
-- `native:` dependency or code doing what the platform already does. Name the feature.
-- `yagni:` abstraction with one implementation, config nobody sets, layer with one caller.
-- `shrink:` same logic, fewer lines. Show the shorter form.
-
-## Examples
-
-❌ "This EmailValidator class might be more complex than necessary, have you
-considered whether all these validation rules are needed at this stage?"
-
-✅ `L12-38: stdlib: 27-line validator class. "@" in email, 1 line, real validation is the confirmation mail.`
-
-✅ `L4: native: moment.js imported for one format call. Intl.DateTimeFormat, 0 deps.`
-
-✅ `repo.py:L88: yagni: AbstractRepository with one implementation. Inline it until a second one exists.`
-
-✅ `L52-71: delete: retry wrapper around an idempotent local call. Nothing replaces it.`
-
-✅ `L30-44: shrink: manual loop builds dict. dict(zip(keys, values)), 1 line.`
-
-## Scoring
-
-End with the only metric that matters: `net: -<N> lines possible.`
-
-If there is nothing to cut, say `Lean already. Ship.` and stop.
-
-## Boundaries
-
-Scope: over-engineering and complexity only. Correctness bugs, security holes,
-and performance are explicitly out of scope. Route them to a normal review
-pass, not this one. A single smoke test or `assert`-based
-self-check is the monolean minimum, not bloat, never flag it for deletion.
-Does not apply the fixes, only lists them.
-"stop monolean-review" or "normal mode": revert to verbose review style.

package/packages/@monomind/cli/.claude/skills/monomind/browse-agentcore.md

@@ -1,115 +0,0 @@
----
-name: monomind:browse-agentcore
-description: Run browser automation on AWS Bedrock AgentCore cloud browser sessions. Use when the user wants to run browser automation on AWS, use a cloud browser with AWS credentials, or needs a managed browser session backed by AWS infrastructure. Triggers include "use agentcore", "run on AWS", "cloud browser with AWS", "bedrock browser", or any task requiring AWS-hosted browser automation.
-version: 1.0.0
-triggers:
-  - agentcore browser
-  - aws cloud browser
-  - bedrock browser
-  - run browser on aws
-  - browser automation aws
-tools:
-  - Bash
-requires:
-  - monomind >= 1.0.0
----
-
-
-# AWS Bedrock AgentCore Browser (monomind:browse-agentcore)
-
-Run browser automation on cloud browser sessions hosted by AWS Bedrock AgentCore. All standard browser commands work identically — the only difference is where the browser runs.
-
-See `monomind:browse` for the full browser automation reference.
-
-## Setup
-
-Credentials are resolved automatically (in order):
-1. Environment variables (`AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, optionally `AWS_SESSION_TOKEN`)
-2. AWS CLI fallback (`aws configure export-credentials`) — supports SSO, IAM roles, named profiles
-
-No additional setup needed if AWS credentials are already configured.
-
-## Core Workflow
-
-```bash
-# Open a page on an AgentCore cloud browser
-npx monomind browse -p agentcore open https://example.com
-
-# Everything else is identical to local Chrome
-npx monomind browse snapshot -i
-npx monomind browse click @e1
-npx monomind browse screenshot page.png
-npx monomind browse close
-```
-
-## Environment Variables
-
-| Variable | Description | Default |
-|---|---|---|
-| `AGENTCORE_REGION` | AWS region | `us-east-1` |
-| `AGENTCORE_BROWSER_ID` | Browser identifier | `aws.browser.v1` |
-| `AGENTCORE_PROFILE_ID` | Persistent browser profile (cookies, localStorage) | none |
-| `AGENTCORE_SESSION_TIMEOUT` | Session timeout in seconds | `3600` |
-| `AWS_PROFILE` | AWS CLI profile for credential resolution | `default` |
-
-## Set Provider Globally
-
-```bash
-export AGENT_BROWSER_PROVIDER=agentcore
-export AGENTCORE_REGION=us-east-2
-
-npx monomind browse open https://example.com
-npx monomind browse snapshot -i
-npx monomind browse click @e1
-npx monomind browse close
-```
-
-## Persistent Profiles
-
-Reuse login state across sessions:
-
-```bash
-# First run — log in
-AGENTCORE_PROFILE_ID=my-app monomind browse -p agentcore open https://app.example.com/login
-npx monomind browse snapshot -i
-npx monomind browse fill @e1 "user@example.com"
-npx monomind browse fill @e2 "password"
-npx monomind browse click @e3
-npx monomind browse close
-
-# Future runs — already authenticated
-AGENTCORE_PROFILE_ID=my-app monomind browse -p agentcore open https://app.example.com/dashboard
-```
-
-## Credential Patterns
-
-```bash
-# Explicit (CI/CD)
-export AWS_ACCESS_KEY_ID=AKIA...
-export AWS_SECRET_ACCESS_KEY=...
-npx monomind browse -p agentcore open https://example.com
-
-# SSO
-aws sso login --profile my-profile
-AWS_PROFILE=my-profile monomind browse -p agentcore open https://example.com
-
-# Default credential chain (IAM role, etc.)
-npx monomind browse -p agentcore open https://example.com
-```
-
-## Live View
-
-When a session starts, AgentCore prints a Live View URL to stderr — open it in the AWS Console to watch in real time:
-
-```
-Session: abc123-def456
-Live View: https://us-east-1.console.aws.amazon.com/bedrock-agentcore/browser/aws.browser.v1/session/abc123-def456#
-```
-
-## Troubleshooting
-
-| Error | Fix |
-|-------|-----|
-| "Failed to run aws CLI" | Install AWS CLI or set `AWS_ACCESS_KEY_ID`/`AWS_SECRET_ACCESS_KEY` directly |
-| "Run 'aws sso login'" | SSO credentials expired — run `aws sso login` |
-| Session timeout | Increase with `AGENTCORE_SESSION_TIMEOUT=7200` |

package/packages/@monomind/cli/.claude/skills/monomind/browse-electron.md

@@ -1,188 +0,0 @@
----
-name: monomind:browse-electron
-description: Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using browser automation via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, or test an Electron application.
-version: 1.0.0
-triggers:
-  - automate electron
-  - control vscode
-  - interact with discord app
-  - test electron app
-  - connect to desktop app
-  - electron desktop automation
-  - automate slack desktop
-tools:
-  - Bash
-requires:
-  - monomind >= 1.0.0
----
-
-
-# Electron App Automation (monomind:browse-electron)
-
-Automate any Electron desktop app using monomind browse via Chrome DevTools Protocol (CDP). Electron apps are built on Chromium and expose a CDP port, enabling the same snapshot-interact workflow used for web pages.
-
-See `monomind:browse` for the full browser automation reference.
-
-## Core Workflow
-
-1. **Launch** the Electron app with remote debugging enabled
-2. **Connect** monomind browse to the CDP port
-3. **Snapshot** to discover interactive elements
-4. **Interact** using element refs
-5. **Re-snapshot** after navigation or state changes
-
-```bash
-# Launch an Electron app with remote debugging
-open -a "Slack" --args --remote-debugging-port=9222
-
-# Connect monomind browse to the app
-npx monomind browse open --port 0
-
-# Standard workflow from here
-npx monomind browse snapshot -i
-npx monomind browse click @e5
-npx monomind browse screenshot slack-desktop.png
-```
-
-## Launching with CDP
-
-Every Electron app supports `--remote-debugging-port` since it's built into Chromium.
-
-### macOS
-
-```bash
-open -a "Slack" --args --remote-debugging-port=9222
-open -a "Visual Studio Code" --args --remote-debugging-port=9223
-open -a "Discord" --args --remote-debugging-port=9224
-open -a "Figma" --args --remote-debugging-port=9225
-open -a "Notion" --args --remote-debugging-port=9226
-open -a "Spotify" --args --remote-debugging-port=9227
-```
-
-### Linux
-
-```bash
-slack --remote-debugging-port=9222
-code --remote-debugging-port=9223
-discord --remote-debugging-port=9224
-```
-
-### Windows
-
-```bash
-"C:\Users\%USERNAME%\AppData\Local\slack\slack.exe" --remote-debugging-port=9222
-"C:\Users\%USERNAME%\AppData\Local\Programs\Microsoft VS Code\Code.exe" --remote-debugging-port=9223
-```
-
-**Important:** If the app is already running, quit it first — the flag must be present at launch time.
-
-## Connecting
-
-```bash
-# Connect to a specific port (persists for session)
-npx monomind browse open --port 0
-
-# Or pass --cdp on each command
-npx monomind browse --cdp 9222 snapshot -i
-
-# Auto-discover a running Chromium-based app
-npx monomind browse --auto-connect snapshot -i
-```
-
-## Tab Management
-
-Electron apps often have multiple windows or webviews:
-
-```bash
-npx monomind browse tab           # list all targets (windows, webviews)
-npx monomind browse tab t2        # switch by stable id
-npx monomind browse tab --url "*settings*"  # switch by URL pattern
-```
-
-## Webview Support
-
-Electron `<webview>` elements appear as separate targets in the tab list:
-
-```bash
-npx monomind browse open --port 0
-npx monomind browse tab
-# 0: [page]    Slack - Main Window     https://app.slack.com/
-# 1: [webview] Embedded Content        https://example.com/widget
-
-npx monomind browse tab t2        # switch to webview
-npx monomind browse snapshot -i
-npx monomind browse click @e3
-```
-
-## Common Patterns
-
-### Inspect and Navigate
-
-```bash
-open -a "Slack" --args --remote-debugging-port=9222
-sleep 3
-npx monomind browse open --port 0
-npx monomind browse snapshot -i
-npx monomind browse click @e10
-npx monomind browse snapshot -i
-```
-
-### Screenshots
-
-```bash
-npx monomind browse open --port 0
-npx monomind browse screenshot app-state.png
-npx monomind browse screenshot --annotate annotated-app.png
-```
-
-### Extract Data
-
-```bash
-npx monomind browse open --port 0
-npx monomind browse snapshot -i
-npx monomind browse get text @e5
-npx monomind browse snapshot --json > app-state.json
-```
-
-### Fill Forms
-
-```bash
-npx monomind browse open --port 0
-npx monomind browse snapshot -i
-npx monomind browse fill @e3 "search query"
-npx monomind browse press Enter
-npx monomind browse wait 1000
-npx monomind browse snapshot -i
-```
-
-### Multiple Apps Simultaneously
-
-```bash
-npx monomind browse --session slack connect 9222
-npx monomind browse --session vscode connect 9223
-
-npx monomind browse --session slack snapshot -i
-npx monomind browse --session vscode snapshot -i
-```
-
-## Color Scheme
-
-```bash
-npx monomind browse open --port 0
-npx monomind browse --color-scheme dark snapshot -i
-# or
-AGENT_BROWSER_COLOR_SCHEME=dark npx monomind browse open --port 0
-```
-
-## Troubleshooting
-
-| Problem | Fix |
-|---------|-----|
-| "Connection refused" | App not launched with `--remote-debugging-port`, or port mismatch |
-| Connect fails after launch | Wait a few seconds — `sleep 3` before connect |
-| Elements not in snapshot | Use `monomind browse tab` to switch to the right window/webview |
-| Can't type in inputs | Try `monomind browse keyboard type "text"` or `keyboard inserttext "text"` |
-
-## Supported Apps
-
-Any Electron app: Slack, Discord, Teams, Signal, VS Code, GitHub Desktop, Postman, Figma, Notion, Obsidian, Spotify, Linear, 1Password, and more.

package/packages/@monomind/cli/.claude/skills/monomind/browse-qa.md

@@ -1,228 +0,0 @@
----
-name: monomind:browse-qa
-description: Systematic exploratory testing of a web application to find bugs, UX issues, and quality problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or review the quality of a web app. Produces a structured report with full reproduction evidence — step-by-step screenshots, repro steps, and severity ratings for every finding.
-version: 1.0.0
-triggers:
-  - dogfood
-  - qa this app
-  - find bugs
-  - exploratory test
-  - bug hunt
-  - test this site
-  - quality review
-  - ux review
-  - find issues
-  - systematic test
-tools:
-  - Bash
-requires:
-  - monomind >= 1.0.0
----
-
-
-# Systematic QA / Dogfood Testing (monomind:browse-qa)
-
-Systematically explore a web application, find issues, and produce a report with full reproduction evidence for every finding.
-
-See `monomind:browse` for the full browser automation reference.
-
-## Inputs
-
-| Parameter | Default | Example override |
-|---|---|---|
-| **Target URL** | _(required)_ | `vercel.com`, `http://localhost:3000` |
-| **Session name** | Slugified domain | `my-qa-session` |
-| **Output directory** | `./qa-output/` | `/tmp/qa` |
-| **Scope** | Full app | `Focus on the billing page` |
-| **Authentication** | None | `Sign in as user@example.com` |
-
-Start immediately with defaults. Only ask if authentication is mentioned but credentials are missing.
-
-Always call `monomind browse` directly — using `npx monomind browse`. It uses the native TypeScript CDP client.
-
-## Workflow
-
-```
-1. Initialize    → Set up session, output dirs, report file
-2. Authenticate  → Sign in if needed, save state
-3. Orient        → Navigate to starting point, initial snapshot
-4. Explore       → Systematically visit pages and test features
-5. Document      → Screenshot + record each issue as found
-6. Wrap up       → Summary counts, close session
-```
-
-### 1. Initialize
-
-```bash
-mkdir -p ./qa-output/screenshots
-SESSION="$(echo '<TARGET_URL>' | sed 's|https\?://||; s|/.*||; s|\.|-|g')"
-npx monomind browse --session "$SESSION" open <TARGET_URL>
-npx monomind browse --session "$SESSION" wait --load networkidle
-```
-
-### 2. Authenticate (if needed)
-
-```bash
-npx monomind browse --session "$SESSION" snapshot -i
-npx monomind browse --session "$SESSION" fill @e1 "<EMAIL>"
-npx monomind browse --session "$SESSION" fill @e2 "<PASSWORD>"
-npx monomind browse --session "$SESSION" click @e3
-npx monomind browse --session "$SESSION" wait --load networkidle
-
-# Save auth state for reuse
-npx monomind browse --session "$SESSION" state save ./qa-output/auth-state.json
-```
-
-For OTP/email codes: ask the user, wait for input, then enter the code.
-
-### 3. Orient
-
-```bash
-npx monomind browse --session "$SESSION" screenshot --annotate ./qa-output/screenshots/00-initial.png
-npx monomind browse --session "$SESSION" snapshot -i
-npx monomind browse --session "$SESSION" get title
-npx monomind browse --session "$SESSION" get url
-```
-
-Document the starting state: what is visible, main navigation elements, key actions available.
-
-### 4. Explore
-
-For each area/page:
-
-```bash
-npx monomind browse --session "$SESSION" click @e[nav-item]
-npx monomind browse --session "$SESSION" wait --load networkidle
-npx monomind browse --session "$SESSION" snapshot -i
-npx monomind browse --session "$SESSION" screenshot ./qa-output/screenshots/<page-name>.png
-```
-
-**Test systematically:**
-- Navigation: does every link work? Does back/forward work?
-- Forms: submit empty, submit invalid, submit valid
-- Interactive elements: hover states, click states, disabled states
-- Responsive: `monomind browse set viewport 375 812` (mobile), `1280 720` (desktop)
-- Error states: what happens when APIs fail? Use `network route` to simulate failures
-- Loading states: `wait --load networkidle` then check if spinners resolve
-
-### 5. Document Each Issue
-
-For every issue found:
-
-```bash
-# 1. Screenshot the broken state
-npx monomind browse --session "$SESSION" screenshot ./qa-output/screenshots/bug-<N>-<name>.png
-
-# 2. Record reproduction steps in report
-```
-
-Issue format:
-```
-## Issue N: <short title>
-
-**Severity:** Critical / High / Medium / Low
-**URL:** <current URL>
-**Steps to reproduce:**
-1. <step>
-2. <step>
-**Expected:** <what should happen>
-**Actual:** <what happened>
-**Screenshot:** screenshots/bug-N-name.png
-```
-
-### 6. Wrap Up
-
-```bash
-npx monomind browse --session "$SESSION" close
-```
-
-Print summary:
-```
-QA SUMMARY
-━━━━━━━━━━━━━━━━━━━━━━━━
-Target:  <URL>
-Pages:   <N> tested
-Issues:  Critical=<N> High=<N> Medium=<N> Low=<N>
-Output:  ./qa-output/
-```
-
-## Severity Guide
-
-| Level | Description | Example |
-|---|---|---|
-| Critical | Blocks core user flow | Login broken, payment fails |
-| High | Major feature broken | Form won't submit, page 404 |
-| Medium | Degraded experience | Wrong error message, slow load |
-| Low | Polish / cosmetic | Alignment off, typo |
-
-## Testing Checklist
-
-**Navigation:**
-- [ ] All nav links work
-- [ ] Breadcrumbs correct
-- [ ] Back/forward work
-- [ ] No broken links (`get url` shows expected path)
-
-**Forms:**
-- [ ] Empty submit → validation errors shown
-- [ ] Invalid data → appropriate error
-- [ ] Valid data → success state
-- [ ] Required field indicators visible
-
-**Interactive:**
-- [ ] All buttons clickable (check `is enabled`)
-- [ ] Dropdowns open and close
-- [ ] Modals open and close
-- [ ] Tooltips appear on hover
-
-**Responsive:**
-- [ ] Mobile (375×812): `monomind browse set viewport 375 812`
-- [ ] Tablet (768×1024): `monomind browse set viewport 768 1024`
-- [ ] Desktop (1280×720): `monomind browse set viewport 1280 720`
-
-**Error states:**
-- [ ] Network error: `monomind browse network route "https://api.*" --abort`
-- [ ] Empty state: check when lists/tables have no data
-- [ ] 404 page: navigate to `/nonexistent-path`
-
-**Accessibility:**
-- [ ] Tab order logical (press Tab through all elements)
-- [ ] All inputs have labels (visible in snapshot)
-- [ ] Buttons have accessible names
-
-## API Error Simulation
-
-```bash
-# Block all API calls to test error handling
-npx monomind browse batch \
-  '["open"]' \
-  '["network", "route", "https://api.example.com/*", "--abort"]' \
-  '["navigate", "https://app.example.com/dashboard"]'
-npx monomind browse snapshot -i
-# → Verify error states render correctly
-```
-
-## Diff Regression Testing
-
-```bash
-# Baseline
-npx monomind browse open https://app.example.com && monomind browse snapshot -i > ./qa-output/baseline.txt
-
-# After change
-npx monomind browse open https://app.example.com && monomind browse diff snapshot --baseline ./qa-output/baseline.txt
-```
-
-## Monomind Integration
-
-```bash
-# Create tasks for critical bugs
-npx monomind task create \
-  --title "CRITICAL: <issue title>" \
-  --description "Steps: <repro steps>. Screenshot: ./qa-output/screenshots/bug-N.png"
-
-# Store QA session patterns for reuse
-npx monomind memory store \
-  --namespace browse \
-  --key "qa-flow-<app>" \
-  --value "open → wait networkidle → screenshot → systematically test nav/forms/responsive"
-```