[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77XG5SDAW7FN4XNERN85MAZ":3,"skill-same:01M77XG5SDAW7FN4XNERN85MAZ":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M77XG5SDAW7FN4XNERN85MAZ","view",null,"Bring up the vean app on THIS worktree's latest code so the human can click around — launch the native Tauri dev window (or a browser tab) on the current project or one you name, live-reloading this checkout's viewer. Use when the user says \u002Fview, \"open the app\", \"let me see it\", \"bring up the editor\", or wants to poke at a change themselves. This is the sanctioned foreground-window path — the human-facing sibling of the headless `drive` skill (which proves a change with a clip). Takes an optional project path\u002Fname\u002Ftitle to open something specific.","Tshah-95\u002Fvean","Tshah-95","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F61719799?v=4","01M77XFPWNV1MYNPKE46Q22K2K","Tejas Shah","01M77XFPXD72CK366HC1W28BCZ",21,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002FTshah-95\u002Fvean\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fview\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: view\ndescription: Bring up the vean app on THIS worktree's latest code so the human can click around — launch the native Tauri dev window (or a browser tab) on the current project or one you name, live-reloading this checkout's viewer. Use when the user says \u002Fview, \"open the app\", \"let me see it\", \"bring up the editor\", or wants to poke at a change themselves. This is the sanctioned foreground-window path — the human-facing sibling of the headless `drive` skill (which proves a change with a clip). Takes an optional project path\u002Fname\u002Ftitle to open something specific.\n---\n\n# view — bring up the app so the human can click around\n\nThe user invoked `\u002Fview` because they want a **window on their screen, now**,\nrunning **this worktree's latest code**, so they can drive it themselves. Your job\nis to launch it, tell them exactly what they're looking at (which branch, which\nproject), and then **step back** — you don't screenshot it, you don't drive it,\nyou hand them the app.\n\nThis is the deliberate opposite of `drive`:\n\n| | `\u002Fview` (this skill) | `drive` |\n|---|---|---|\n| Audience | the **human** — they click | the **agent** — proof for chat |\n| Surface | a real **foreground window** (native app or browser tab) | headless browser, no visible window |\n| Output | \"it's up, go poke at it\" | a screenshot\u002F`.webm` clip referenced back in chat |\n| Screen takeover | **yes, on purpose** — that's the whole point | never |\n\n`\u002Fview` **is** the explicit ask that the \"no screen takeover\" rule carves out an\nexception for. Bringing the window forward is exactly what was requested.\n\nThis exception is human-only and is never test evidence. Agents must not drive\nthe foreground window after launch. Browser verification uses\n`bun run drive verify`. Native menus, file dialogs, focus, and window lifecycle\nhave no unattended local oracle; never use host computer-use to manufacture one.\n\n## The one fact that makes this correct\n\n`vean open` is worktree-sensitive **only if you run it from this checkout's\nsource**, not the global `vean` bin. `setup:cli` (`bun link`) points the bare\n`vean` symlink at whichever tree linked last — so `vean open` may launch a\n*different* worktree's code against this cwd (silent version skew; see\nDESIGN-WORKTREE.md §\"Sharp edges\" \u002F the `drive` skill). Always launch via:\n\n```bash\nbun src\u002Fcli.ts open …        # import.meta.dir → THIS worktree's src\u002F and app\u002F\n```\n\nTwo more traps this skill exists to avoid:\n\n- **Bare `vean open` (no flags) opens the *installed* `\u002FApplications\u002Fvean.app`** —\n  a potentially stale installed snapshot that ignores your uncommitted `viewer\u002F`\n  changes and isn't tied to this worktree. Wrong for \"see my latest changes.\"\n- The `--dev` path serves the **live HMR viewer from this checkout**; the installed\n  app always serves the built `viewer\u002Fdist`. For \"the change I just made,\" you\n  want `--dev` (native) or `--view browser` (the default browser path is also live\n  HMR).\n\n## Launch it (default: native Tauri dev window)\n\nResolve the project first (optional arg), then launch the native dev window on it.\n**Run it backgrounded** — `tauri:dev` is a long-running process (dev server + the\nwindow); backgrounding keeps its parent alive so the window persists, and frees\nyou to report back.\n\n```bash\n# Optional: which project? Bare = this worktree's current\u002Factive project.\n#   Accepts a project id, its title (e.g. `open retire`), or a filesystem path.\nbun src\u002Fcli.ts open [project] --dev\n```\n\n- Launch this with the harness running it **in the background** (`run_in_background:\n  true`). It stays live as long as the app window is open.\n- **First launch in a fresh worktree is slow** — `tauri:dev` compiles the Rust\n  shell once (needs Rust\u002FCargo; `bun run app:doctor -- --native` verifies it).\n  Subsequent launches are fast, and the viewer hot-reloads without a relaunch. Say\n  so when you report, so the wait isn't a surprise.\n\n### The instant alternative — a browser tab (identical UI, no Rust compile)\n\nWhen they just want to *see the UI change* fast, or Rust\u002Fnative isn't set up, the\nbrowser view renders the **byte-identical viewer + backend** the native window\ndoes, with live HMR, and comes up in seconds:\n\n```bash\nbun src\u002Fcli.ts open [project] --view browser   # opens the default browser at 127.0.0.1\n```\n\nThe only thing the native window buys over this is a real app frame + the native\nmenus (File → Open Project…, Add Media Root…). If the user said \"the app\" \u002F\n\"Tauri,\" default to `--dev`; if they said \"just let me see it\" or you know native\nisn't built, offer\u002Fuse `--view browser`.\n\n### Claude Desktop's Preview pane (the in-app sibling)\n\nIn a Claude Desktop (Code tab) session, the **Preview button** serves the same\nlive viewer *inside the app*: `.claude\u002Flaunch.json` runs\n`scripts\u002Fpreview-launch.ts`, which starts `vean preview --no-open` on port 5176\n— or whatever port the app reassigns via the `PORT` env var (`autoPort`) — with\nthe project resolved like `drive` does (`.vean\u002Fworktree.json` `defaultProject` →\nthis checkout). Same HMR viewer, same worktree-latest code; the user just clicks\nPreview instead of getting a separate window. If they ask why Preview shows the\nwrong project, that pointer file is where to look.\n\n## Report what they're looking at\n\nThe user needs to know the window reflects the **right** worktree and project —\nthat's the whole value of launching from this checkout. After launching, tell them:\n\n```bash\ngit branch --show-current                 # which branch this worktree is on\nbun scripts\u002Fdrive.ts name                 # the worktree slug (same one drive uses)\nbun src\u002Fcli.ts project current --json     # the resolved active project\n```\n\nReport a one-liner like: *\"vean dev app coming up on branch `\u003Cbranch>`\n(worktree `\u003Cslug>`), project **\u003Ctitle>** — native window, first compile ~1–2 min,\nthen it's live. Poke around; the viewer hot-reloads as I push more changes.\"*\n\n## \"Something specific\"\n\n`open` selects a **project**; it does not deep-link to a clip or frame. So:\n\n- A project **path \u002F id \u002F title** → pass it as `[project]`; the app boots straight\n  at it.\n- A **timeline \u002F route reference** (`timeline:main`, a `.mlt`, `media:raw`) → open\n  the project that *contains* it, then tell the user to navigate there in the UI\n  (there's no frame-level deep-link arg yet — if that keeps coming up, that's a\n  real feature request for the `open` action, not a workaround to hide here).\n\n## Discipline\n\n- **Launch, report, step back.** Don't drive, click, or screenshot the window you\n  brought up for the human — that's `drive`'s job, and doing it would fight them\n  for focus.\n- **Run from this worktree via `bun src\u002Fcli.ts open`** — never the bare `vean`\n  bin. The point of `\u002Fview` is \"*this* checkout's code.\"\n- **Background the launch** so the window survives and chat isn't blocked. It stays\n  up until the user closes the app (native) or you stop the background task\n  (browser: `bun run drive down --all` reaps preview sidecars, or kill the task).\n- **Don't rebuild anything.** `\u002Fview` reflects your working tree live via HMR; no\n  `app:build` \u002F `viewer:build` needed to see a `viewer\u002F` change.\n","# view — bring up the app so the human can click around\n\nThe user invoked `\u002Fview` because they want a **window on their screen, now**,\nrunning **this worktree's latest code**, so they can drive it themselves. Your job\nis to launch it, tell them exactly what they're looking at (which branch, which\nproject), and then **step back** — you don't screenshot it, you don't drive it,\nyou hand them the app.\n\nThis is the deliberate opposite of `drive`:\n\n| | `\u002Fview` (this skill) | `drive` |\n|---|---|---|\n| Audience | the **human** — they click | the **agent** — proof for chat |\n| Surface | a real **foreground window** (native app or browser tab) | headless browser, no visible window |\n| Output | \"it's up, go poke at it\" | a screenshot\u002F`.webm` clip referenced back in chat |\n| Screen takeover | **yes, on purpose** — that's the whole point | never |\n\n`\u002Fview` **is** the explicit ask that the \"no screen takeover\" rule carves out an\nexception for. Bringing the window forward is exactly what was requested.\n\nThis exception is human-only and is never test evidence. Agents must not drive\nthe foreground window after launch. Browser verification uses\n`bun run drive verify`. Native menus, file dialogs, focus, and window lifecycle\nhave no unattended local oracle; never use host computer-use to manufacture one.\n\n## The one fact that makes this correct\n\n`vean open` is worktree-sensitive **only if you run it from this checkout's\nsource**, not the global `vean` bin. `setup:cli` (`bun link`) points the bare\n`vean` symlink at whichever tree linked last — so `vean open` may launch a\n*different* worktree's code against this cwd (silent version skew; see\nDESIGN-WORKTREE.md §\"Sharp edges\" \u002F the `drive` skill). Always launch via:\n\n```bash\nbun src\u002Fcli.ts open …        # import.meta.dir → THIS worktree's src\u002F and app\u002F\n```\n\nTwo more traps this skill exists to avoid:\n\n- **Bare `vean open` (no flags) opens the *installed* `\u002FApplications\u002Fvean.app`** —\n  a potentially stale installed snapshot that ignores your uncommitted `viewer\u002F`\n  changes and isn't tied to this worktree. Wrong for \"see my latest changes.\"\n- The `--dev` path serves the **live HMR viewer from this checkout**; the installed\n  app always serves the built `viewer\u002Fdist`. For \"the change I just made,\" you\n  want `--dev` (native) or `--view browser` (the default browser path is also live\n  HMR).\n\n## Launch it (default: native Tauri dev window)\n\nResolve the project first (optional arg), then launch the native dev window on it.\n**Run it backgrounded** — `tauri:dev` is a long-running process (dev server + the\nwindow); backgrounding keeps its parent alive so the window persists, and frees\nyou to report back.\n\n```bash\n# Optional: which project? Bare = this worktree's current\u002Factive project.\n#   Accepts a project id, its title (e.g. `open retire`), or a filesystem path.\nbun src\u002Fcli.ts open [project] --dev\n```\n\n- Launch this with the harness running it **in the background** (`run_in_background:\n  true`). It stays live as long as the app window is open.\n- **First launch in a fresh worktree is slow** — `tauri:dev` compiles the Rust\n  shell once (needs Rust\u002FCargo; `bun run app:doctor -- --native` verifies it).\n  Subsequent launches are fast, and the viewer hot-reloads without a relaunch. Say\n  so when you report, so the wait isn't a surprise.\n\n### The instant alternative — a browser tab (identical UI, no Rust compile)\n\nWhen they just want to *see the UI change* fast, or Rust\u002Fnative isn't set up, the\nbrowser view renders the **byte-identical viewer + backend** the native window\ndoes, with live HMR, and comes up in seconds:\n\n```bash\nbun src\u002Fcli.ts open [project] --view browser   # opens the default browser at 127.0.0.1\n```\n\nThe only thing the native window buys over this is a real app frame + the native\nmenus (File → Open Project…, Add Media Root…). If the user said \"the app\" \u002F\n\"Tauri,\" default to `--dev`; if they said \"just let me see it\" or you know native\nisn't built, offer\u002Fuse `--view browser`.\n\n### Claude Desktop's Preview pane (the in-app sibling)\n\nIn a Claude Desktop (Code tab) session, the **Preview button** serves the same\nlive viewer *inside the app*: `.claude\u002Flaunch.json` runs\n`scripts\u002Fpreview-launch.ts`, which starts `vean preview --no-open` on port 5176\n— or whatever port the app reassigns via the `PORT` env var (`autoPort`) — with\nthe project resolved like `drive` does (`.vean\u002Fworktree.json` `defaultProject` →\nthis checkout). Same HMR viewer, same worktree-latest code; the user just clicks\nPreview instead of getting a separate window. If they ask why Preview shows the\nwrong project, that pointer file is where to look.\n\n## Report what they're looking at\n\nThe user needs to know the window reflects the **right** worktree and project —\nthat's the whole value of launching from this checkout. After launching, tell them:\n\n```bash\ngit branch --show-current                 # which branch this worktree is on\nbun scripts\u002Fdrive.ts name                 # the worktree slug (same one drive uses)\nbun src\u002Fcli.ts project current --json     # the resolved active project\n```\n\nReport a one-liner like: *\"vean dev app coming up on branch `\u003Cbranch>`\n(worktree `\u003Cslug>`), project **\u003Ctitle>** — native window, first compile ~1–2 min,\nthen it's live. Poke around; the viewer hot-reloads as I push more changes.\"*\n\n## \"Something specific\"\n\n`open` selects a **project**; it does not deep-link to a clip or frame. So:\n\n- A project **path \u002F id \u002F title** → pass it as `[project]`; the app boots straight\n  at it.\n- A **timeline \u002F route reference** (`timeline:main`, a `.mlt`, `media:raw`) → open\n  the project that *contains* it, then tell the user to navigate there in the UI\n  (there's no frame-level deep-link arg yet — if that keeps coming up, that's a\n  real feature request for the `open` action, not a workaround to hide here).\n\n## Discipline\n\n- **Launch, report, step back.** Don't drive, click, or screenshot the window you\n  brought up for the human — that's `drive`'s job, and doing it would fight them\n  for focus.\n- **Run from this worktree via `bun src\u002Fcli.ts open`** — never the bare `vean`\n  bin. The point of `\u002Fview` is \"*this* checkout's code.\"\n- **Background the launch** so the window survives and chat isn't blocked. It stays\n  up until the user closes the app (native) or you stop the background task\n  (browser: `bun run drive down --all` reaps preview sidecars, or kill the task).\n- **Don't rebuild anything.** `\u002Fview` reflects your working tree live via HMR; no\n  `app:build` \u002F `viewer:build` needed to see a `viewer\u002F` change.\n",{"name":5,"description":7},"main","7efc6011377b9ed9f5eb74159f973b4fe89c3630",".agents\u002Fskills\u002Fview",3,"https:\u002F\u002Fgithub.com\u002FTshah-95\u002Fvean","https:\u002F\u002Fgithub.com\u002FTshah-95","2026-07-14 05:39:58",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Tshah-95\u002Fvean --skill view",{"tool":37,"command":38},"bunx","bunx skills add Tshah-95\u002Fvean --skill view",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Tshah-95\u002Fvean --skill view","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTshah-95\u002Fvean\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fview\u002FSKILL.md",true,[],[46,52,58,64,69,74],{"skillNo":47,"name":48,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M77XGJXBZPPRET0GNS7W5ZJ0","setup","https:\u002F\u002Fgithub.com\u002FTshah-95\u002Fvean\u002Fblob\u002Fmain\u002Fskills\u002Fsetup\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M77XGJ2TYDRAAM4RWEGEJ17H","editing","https:\u002F\u002Fgithub.com\u002FTshah-95\u002Fvean\u002Fblob\u002Fmain\u002Fskills\u002Fediting\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M77XGH0NYJ19W12G92HANR7Q","drive","https:\u002F\u002Fgithub.com\u002FTshah-95\u002Fvean\u002Fblob\u002Fmain\u002Fskills\u002Fdrive\u002FSKILL.md",[],[],{"skillNo":65,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M77XGG2759J1RQBGH3W23TA2","https:\u002F\u002Fgithub.com\u002FTshah-95\u002Fvean\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fview\u002FSKILL.md",[],[],{"skillNo":70,"name":48,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M77XGF2FTRX0ZNJVSC9NKYVF","https:\u002F\u002Fgithub.com\u002FTshah-95\u002Fvean\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsetup\u002FSKILL.md",[],[],{"skillNo":75,"name":54,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M77XGE7BPAKD4ZQTS1247MTB","https:\u002F\u002Fgithub.com\u002FTshah-95\u002Fvean\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fediting\u002FSKILL.md",[],[]]