[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AFMK47H247K7NP0DZM348K":3,"skill-same:01M7AFMK47H247K7NP0DZM348K":63},{"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":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7AFMK47H247K7NP0DZM348K","trove-react-view-transitions",null,"Implement smooth, native-feeling animations with React's View Transition API (the `ViewTransition` component, `addTransitionType`, CSS view-transition pseudo-elements). Use for page transitions, shared element morphs, Suspense reveals, list identity, or animating between React UI states without a third-party animation library. Use when: view transition; shared element animation; page transition; startViewTransition.","bravew\u002Ftrove","bravew","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10855844?v=4","01M7ACJ91JZSQYHT81XPVYR7VA","Yong","01M7AFERNR92HDPGNGP5QA16DM",10,"MIT","https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fplugins\u002Ftrove-dev\u002F.copilot\u002Fskills\u002Ftrove-react-view-transitions\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: trove-react-view-transitions\ndescription: \"Implement smooth, native-feeling animations with React's View Transition API (the `ViewTransition` component, `addTransitionType`, CSS view-transition pseudo-elements). Use for page transitions, shared element morphs, Suspense reveals, list identity, or animating between React UI states without a third-party animation library. Use when: view transition; shared element animation; page transition; startViewTransition.\"\nlicense: MIT\n---\n\u003C!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly -->\n\u003C!-- Regenerate: bun run build:skills -->\n\n## Session Init\n\nThis skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.\n\n# React View Transitions\n\nAnimate between UI states using the browser's native View Transition API.\nDeclare what animates with `\u003CViewTransition>`, trigger when with\n`startTransition`, `useDeferredValue`, or `Suspense`, and control how with CSS\nclasses from `references\u002Fcss-recipes.md`. Unsupported browsers skip animations.\n\n## Stack Notes\n\nThis skill assumes a Vite-based React app (React Router, not Next.js\nApp Router). `\u003CViewTransition>` and `addTransitionType` are stable in React 19.3,\nso use `react` and `react-dom` 19.3 or newer and verify with `npm ls react`.\nEarlier stable versions do not include these APIs. The `references\u002Fnextjs.md`\nfile is only for future Next.js work.\n\n## Load On Demand\n\n- `references\u002Fimplementation.md` - required workflow when adding transitions.\n- `references\u002Fcss-recipes.md` - CSS recipes to copy into the global stylesheet.\n- `references\u002Fpatterns.md` - examples, events API, timing, and troubleshooting.\n- `references\u002Fnextjs.md` - Next.js App Router reference only.\n\nDo not inline those references into the conversation. Load the relevant file\nwhen the implementation step needs it.\n\n## When To Animate\n\nEvery transition must communicate continuity or spatial relationship. If you\ncannot name what the motion communicates, skip it.\n\nApply every fitting pattern in this order:\n\n| Priority | Pattern | Communicates |\n|---|---|---|\n| 1 | Shared element (`name`) | Same thing, going deeper |\n| 2 | Suspense reveal | Data loaded |\n| 3 | List identity (`key`) | Same items, new arrangement |\n| 4 | State change (`enter`\u002F`exit`) | Something appeared\u002Fdisappeared |\n| 5 | Route change | Going to a new place |\n\nUse directional slides only for hierarchy or ordered sequences. Lateral tabs\nshould use a cross-fade or no animation.\n\n## Implementation Workflow\n\n1. Load `references\u002Fimplementation.md` and start with the audit. Map every\n   `\u003CLink>`, router navigation, `\u003CSuspense>` boundary, page component,\n   persistent element, and shared visual element.\n2. Copy the complete CSS recipe set from `references\u002Fcss-recipes.md` into the\n   global stylesheet before wiring components.\n3. Isolate persistent headers, navbars, sidebars, sticky controls, and matching\n   skeleton\u002Fcontent controls with `viewTransitionName`.\n4. For hierarchical route changes, tag direction with `addTransitionType` inside\n   `startTransition`, then wrap page components, not layouts, in a type-keyed\n   `\u003CViewTransition>`.\n5. For Suspense, wrap fallback and content separately. Use string props, not\n   type maps; Suspense resolves fire as separate transitions without route type.\n6. For shared elements, use globally unique `name` values such as\n   `photo-${id}` and add fallback `enter`\u002F`exit` when a pair might not form.\n7. Verify every row in the navigation map: mount\u002Funmount behavior, named-pair\n   formation, `default=\"none\"`, persistent element isolation, and reduced\n   motion.\n\n## Non-Negotiable Rules\n\n- Only `startTransition`, `useDeferredValue`, or `Suspense` activate React view\n  transitions. Regular `setState` does not animate.\n- `\u003CViewTransition>` must appear before any DOM node it needs to animate.\n  Wrapping the VT inside a `\u003Cdiv>` suppresses enter\u002Fexit.\n- Use `default=\"none\"` and explicit triggers. Bare VTs cross-fade on every\n  transition, including revalidation and background updates.\n- Type-keyed props must include `default: \"none\"` unless broad cross-fades are\n  intentional.\n- Pair `enter` with `exit`; otherwise the old page vanishes while the new one\n  animates.\n- Never use a fade-out exit on pages with shared morphs. Use a directional exit\n  so the morph stays visually coherent.\n- `router.back()` and browser back\u002Fforward do not trigger view transitions;\n  navigate to an explicit URL instead.\n- Nested VTs inside an exiting parent do not run their own enter\u002Fexit. Avoid\n  layout-level wrappers around page content.\n\n## Verification\n\nRun the app and inspect the real transitions, including reduced-motion mode.\nCheck desktop and mobile viewports. Confirm that unsupported browsers degrade\nto no animation rather than broken layout or invisible content.\n\n## Source\n\nUpstream: `vercel-labs\u002Fagent-skills` `react-view-transitions` (MIT). Adapted\nfor the Trove marketplace.\n","\u003C!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly -->\n\u003C!-- Regenerate: bun run build:skills -->\n\n## Session Init\n\nThis skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.\n\n# React View Transitions\n\nAnimate between UI states using the browser's native View Transition API.\nDeclare what animates with `\u003CViewTransition>`, trigger when with\n`startTransition`, `useDeferredValue`, or `Suspense`, and control how with CSS\nclasses from `references\u002Fcss-recipes.md`. Unsupported browsers skip animations.\n\n## Stack Notes\n\nThis skill assumes a Vite-based React app (React Router, not Next.js\nApp Router). `\u003CViewTransition>` and `addTransitionType` are stable in React 19.3,\nso use `react` and `react-dom` 19.3 or newer and verify with `npm ls react`.\nEarlier stable versions do not include these APIs. The `references\u002Fnextjs.md`\nfile is only for future Next.js work.\n\n## Load On Demand\n\n- `references\u002Fimplementation.md` - required workflow when adding transitions.\n- `references\u002Fcss-recipes.md` - CSS recipes to copy into the global stylesheet.\n- `references\u002Fpatterns.md` - examples, events API, timing, and troubleshooting.\n- `references\u002Fnextjs.md` - Next.js App Router reference only.\n\nDo not inline those references into the conversation. Load the relevant file\nwhen the implementation step needs it.\n\n## When To Animate\n\nEvery transition must communicate continuity or spatial relationship. If you\ncannot name what the motion communicates, skip it.\n\nApply every fitting pattern in this order:\n\n| Priority | Pattern | Communicates |\n|---|---|---|\n| 1 | Shared element (`name`) | Same thing, going deeper |\n| 2 | Suspense reveal | Data loaded |\n| 3 | List identity (`key`) | Same items, new arrangement |\n| 4 | State change (`enter`\u002F`exit`) | Something appeared\u002Fdisappeared |\n| 5 | Route change | Going to a new place |\n\nUse directional slides only for hierarchy or ordered sequences. Lateral tabs\nshould use a cross-fade or no animation.\n\n## Implementation Workflow\n\n1. Load `references\u002Fimplementation.md` and start with the audit. Map every\n   `\u003CLink>`, router navigation, `\u003CSuspense>` boundary, page component,\n   persistent element, and shared visual element.\n2. Copy the complete CSS recipe set from `references\u002Fcss-recipes.md` into the\n   global stylesheet before wiring components.\n3. Isolate persistent headers, navbars, sidebars, sticky controls, and matching\n   skeleton\u002Fcontent controls with `viewTransitionName`.\n4. For hierarchical route changes, tag direction with `addTransitionType` inside\n   `startTransition`, then wrap page components, not layouts, in a type-keyed\n   `\u003CViewTransition>`.\n5. For Suspense, wrap fallback and content separately. Use string props, not\n   type maps; Suspense resolves fire as separate transitions without route type.\n6. For shared elements, use globally unique `name` values such as\n   `photo-${id}` and add fallback `enter`\u002F`exit` when a pair might not form.\n7. Verify every row in the navigation map: mount\u002Funmount behavior, named-pair\n   formation, `default=\"none\"`, persistent element isolation, and reduced\n   motion.\n\n## Non-Negotiable Rules\n\n- Only `startTransition`, `useDeferredValue`, or `Suspense` activate React view\n  transitions. Regular `setState` does not animate.\n- `\u003CViewTransition>` must appear before any DOM node it needs to animate.\n  Wrapping the VT inside a `\u003Cdiv>` suppresses enter\u002Fexit.\n- Use `default=\"none\"` and explicit triggers. Bare VTs cross-fade on every\n  transition, including revalidation and background updates.\n- Type-keyed props must include `default: \"none\"` unless broad cross-fades are\n  intentional.\n- Pair `enter` with `exit`; otherwise the old page vanishes while the new one\n  animates.\n- Never use a fade-out exit on pages with shared morphs. Use a directional exit\n  so the morph stays visually coherent.\n- `router.back()` and browser back\u002Fforward do not trigger view transitions;\n  navigate to an explicit URL instead.\n- Nested VTs inside an exiting parent do not run their own enter\u002Fexit. Avoid\n  layout-level wrappers around page content.\n\n## Verification\n\nRun the app and inspect the real transitions, including reduced-motion mode.\nCheck desktop and mobile viewports. Confirm that unsupported browsers degrade\nto no animation rather than broken layout or invisible content.\n\n## Source\n\nUpstream: `vercel-labs\u002Fagent-skills` `react-view-transitions` (MIT). Adapted\nfor the Trove marketplace.\n",{"name":5,"license":15,"description":7},"main","f88db1f1cf0e0703dd962051ebc142db961d7799","plugins\u002Ftrove-dev\u002F.copilot\u002Fskills\u002Ftrove-react-view-transitions",1,"https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove","https:\u002F\u002Fgithub.com\u002Fbravew","2026-11-12 07:56:32",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add bravew\u002Ftrove --skill trove-react-view-transitions",{"tool":37,"command":38},"bunx","bunx skills add bravew\u002Ftrove --skill trove-react-view-transitions",{"tool":40,"command":41},"pnpm","pnpm dlx skills add bravew\u002Ftrove --skill trove-react-view-transitions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fplugins\u002Ftrove-dev\u002F.copilot\u002Fskills\u002Ftrove-react-view-transitions\u002FSKILL.md",true,[45,51,55,59],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fcss-recipes.md","REFERENCE","参考文档",5226,"https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fplugins\u002Ftrove-dev\u002F.copilot\u002Fskills\u002Ftrove-react-view-transitions\u002Freferences\u002Fcss-recipes.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fimplementation.md",10165,"https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fplugins\u002Ftrove-dev\u002F.copilot\u002Fskills\u002Ftrove-react-view-transitions\u002Freferences\u002Fimplementation.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fnextjs.md",6496,"https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fplugins\u002Ftrove-dev\u002F.copilot\u002Fskills\u002Ftrove-react-view-transitions\u002Freferences\u002Fnextjs.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fpatterns.md",8347,"https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fplugins\u002Ftrove-dev\u002F.copilot\u002Fskills\u002Ftrove-react-view-transitions\u002Freferences\u002Fpatterns.md",[64,71,78,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7AGJDHTQAS1VK6P7VJAV79G","using-trove","Skill discipline anchor for the Trove marketplace. Loaded once per session; routes the agent to the right trove-* skill before code, planning, review, or git actions.","https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fusing-trove\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7AGJAS4V4TXE6TV6F839BGZ","trove-write-skill","Skill authoring workflow. Use when creating or updating a Codex or Trove skill, including rubrics, tasks, metadata, and validation.","https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Ftrove-write-skill\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7AGJ87K41ZAC8DDBAV17QFW","trove-worktree","Git worktree workflow for spikes, risky experiments, and broad refactors that should not disturb the user's current branch.","https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Ftrove-worktree\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7AGJ32V58VYBFYMS9EMHRY4","trove-why","Reconstruct design rationale and decision history from evidence — source control, issue tracker (Linear), docs (Notion), chat (Slack), error tracking (Sentry) — with calibrated confidence. Use for \"why does X work this way\", \"why did we pick Y\", regressions, and postmortems. Use trove-explain for how it works now.","https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Ftrove-why\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7AGJ0FHJSRR8MMXC3V8XNHF","trove-verify","Completion verification workflow. Use before claiming done, fixed, complete, ready, or shipped.","https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Ftrove-verify\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7AGHWV4B9SDS60RH5W0B0K5","trove-unslop","Cut AI tells from writing — PR descriptions, release notes, specs, commit bodies, and replies. Use before finalizing prose, or when the user asks to clean up, de-slop, or make text sound human.","https:\u002F\u002Fgithub.com\u002Fbravew\u002Ftrove\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Ftrove-unslop\u002FSKILL.md",[],[]]