[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73AMDRR3A31WEVQABD2QAJ3":3,"skill-same:01M73AMDRR3A31WEVQABD2QAJ3":149},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M73AMDRR3A31WEVQABD2QAJ3","vue-best-practices",null,"MUST be used for Vue.js tasks. Strongly recommends Composition API with `\u003Cscript setup>` and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.","qhjqhj00\u002Fresearch-skills-pool","qhjqhj00","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F29684092?v=4","01M72AE0ZGXVM5C57N512DGQG8","Tommy Chien","01M72AE107ESJMHT7QC5SXX144",3,"MIT","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: vue-best-practices\ndescription: MUST be used for Vue.js tasks. Strongly recommends Composition API with `\u003Cscript setup>` and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.\nlicense: MIT\nmetadata:\n  author: github.com\u002Fvuejs-ai\n  version: \"18.0.0\"\n---\n\n# Vue Best Practices Workflow\n\nUse this skill as an instruction set. Follow the workflow in order unless the user explicitly asks for a different order.\n\n## Core Principles\n- **Keep state predictable:** one source of truth, derive everything else.\n- **Make data flow explicit:** Props down, Events up for most cases.\n- **Favor small, focused components:** easier to test, reuse, and maintain.\n- **Avoid unnecessary re-renders:** use computed properties and watchers wisely.\n- **Readability counts:** write clear, self-documenting code.\n\n## 1) Confirm architecture before coding (required)\n\n- Default stack: Vue 3 + Composition API + `\u003Cscript setup lang=\"ts\">`.\n- If the project explicitly uses Options API, load `vue-options-api-best-practices` skill if available.\n- If the project explicitly uses JSX, load `vue-jsx-best-practices` skill if available.\n\n### 1.1 Must-read core references (required)\n\n- Before implementing any Vue task, make sure to read and apply these core references:\n  - `references\u002Freactivity.md`\n  - `references\u002Fsfc.md`\n  - `references\u002Fcomponent-data-flow.md`\n  - `references\u002Fcomposables.md`\n- Keep these references in active working context for the entire task, not only when a specific issue appears.\n\n### 1.2 Plan component boundaries before coding (required)\n\nCreate a brief component map before implementation for any non-trivial feature.\n\n- Define each component's single responsibility in one sentence.\n- Keep entry\u002Froot and route-level view components as composition surfaces by default.\n- Move feature UI and feature logic out of entry\u002Froot\u002Fview components unless the task is intentionally a tiny single-file demo.\n- Define props\u002Femits contracts for each child component in the map.\n- Prefer a feature folder layout (`components\u002F\u003Cfeature>\u002F...`, `composables\u002Fuse\u003CFeature>.ts`) when adding more than one component.\n\n## 2) Apply essential Vue foundations (required)\n\nThese are essential, must-know foundations. Apply all of them in every Vue task using the core references already loaded in section `1.1`.\n\n### Reactivity\n\n- Must-read reference from `1.1`: [reactivity](references\u002Freactivity.md)\n- Keep source state minimal (`ref`\u002F`reactive`), derive everything possible with `computed`.\n- Use watchers for side effects if needed.\n- Avoid recomputing expensive logic in templates.\n\n### SFC structure and template safety\n\n- Must-read reference from `1.1`: [sfc](references\u002Fsfc.md)\n- Keep SFC sections in this order: `\u003Cscript>` → `\u003Ctemplate>` → `\u003Cstyle>`.\n- Keep SFC responsibilities focused; split large components.\n- Keep templates declarative; move branching\u002Fderivation to script.\n- Apply Vue template safety rules (`v-html`, list rendering, conditional rendering choices).\n\n### Keep components focused\n\nSplit a component when it has **more than one clear responsibility** (e.g. data orchestration + UI, or multiple independent UI sections).\n\n- Prefer **smaller components + composables** over one “mega component”\n- Move **UI sections** into child components (props in, events out).\n- Move **state\u002Fside effects** into composables (`useXxx()`).\n\nApply objective split triggers. Split the component if **any** condition is true:\n\n- It owns both orchestration\u002Fstate and substantial presentational markup for multiple sections.\n- It has 3+ distinct UI sections (for example: form, filters, list, footer\u002Fstatus).\n- A template block is repeated or could become reusable (item rows, cards, list entries).\n\nEntry\u002Froot and route view rule:\n\n- Keep entry\u002Froot and route view components thin: app shell\u002Flayout, provider wiring, and feature composition.\n- Do not place full feature implementations in entry\u002Froot\u002Fview components when those features contain independent parts.\n- For CRUD\u002Flist features (todo, table, catalog, inbox), split at least into:\n  - feature container component\n  - input\u002Fform component\n  - list (and\u002For item) component\n  - footer\u002Factions or filter\u002Fstatus component\n- Allow a single-file implementation only for very small throwaway demos; if chosen, explicitly justify why splitting is unnecessary.\n\n### Component data flow\n\n- Must-read reference from `1.1`: [component-data-flow](references\u002Fcomponent-data-flow.md)\n- Use props down, events up as the primary model.\n- Use `v-model` only for true two-way component contracts.\n- Use provide\u002Finject only for deep-tree dependencies or shared context.\n- Keep contracts explicit and typed with `defineProps`, `defineEmits`, and `InjectionKey` as needed.\n\n### Composables\n\n- Must-read reference from `1.1`: [composables](references\u002Fcomposables.md)\n- Extract logic into composables when it is reused, stateful, or side-effect heavy.\n- Keep composable APIs small, typed, and predictable.\n- Separate feature logic from presentational components.\n\n## 3) Consider optional features only when requirements call for them\n\n### 3.1 Standard optional features\n\nDo not add these by default. Load the matching reference only when the requirement exists.\n\n- Slots: parent needs to control child content\u002Flayout -> [component-slots](references\u002Fcomponent-slots.md)\n- Fallthrough attributes: wrapper\u002Fbase components must forward attrs\u002Fevents safely -> [component-fallthrough-attrs](references\u002Fcomponent-fallthrough-attrs.md)\n- Built-in component `\u003CKeepAlive>` for stateful view caching -> [component-keep-alive](references\u002Fcomponent-keep-alive.md)\n- Built-in component `\u003CTeleport>` for overlays\u002Fportals -> [component-teleport](references\u002Fcomponent-teleport.md)\n- Built-in component `\u003CSuspense>` for async subtree fallback boundaries -> [component-suspense](references\u002Fcomponent-suspense.md)\n- Animation-related features: pick the simplest approach that matches the required motion behavior.\n  - Built-in component `\u003CTransition>` for enter\u002Fleave effects -> [transition](references\u002Fcomponent-transition.md)\n  - Built-in component `\u003CTransitionGroup>` for animated list mutations -> [transition-group](references\u002Fcomponent-transition-group.md)\n  - Class-based animation for non-enter\u002Fleave effects -> [animation-class-based-technique](references\u002Fanimation-class-based-technique.md)\n  - State-driven animation for user-input-driven animation -> [animation-state-driven-technique](references\u002Fanimation-state-driven-technique.md)\n\n### 3.2 Less-common optional features\n\nUse these only when there is explicit product or technical need.\n\n- Directives: behavior is DOM-specific and not a good composable\u002Fcomponent fit -> [directives](references\u002Fdirectives.md)\n- Async components: heavy\u002Frarely-used UI should be lazy loaded -> [component-async](references\u002Fcomponent-async.md)\n- Render functions only when templates cannot express the requirement -> [render-functions](references\u002Frender-functions.md)\n- Plugins when behavior must be installed app-wide -> [plugins](references\u002Fplugins.md)\n- State management patterns: app-wide shared state crosses feature boundaries -> [state-management](references\u002Fstate-management.md)\n\n## 4) Run performance optimization after behavior is correct\n\nPerformance work is a post-functionality pass. Do not optimize before core behavior is implemented and verified.\n\n- Large list rendering bottlenecks -> [perf-virtualize-large-lists](references\u002Fperf-virtualize-large-lists.md)\n- Static subtrees re-rendering unnecessarily -> [perf-v-once-v-memo-directives](references\u002Fperf-v-once-v-memo-directives.md)\n- Over-abstraction in hot list paths -> [perf-avoid-component-abstraction-in-lists](references\u002Fperf-avoid-component-abstraction-in-lists.md)\n- Expensive updates triggered too often -> [updated-hook-performance](references\u002Fupdated-hook-performance.md)\n\n## 5) Final self-check before finishing\n\n- Core behavior works and matches requirements.\n- All must-read references were read and applied.\n- Reactivity model is minimal and predictable.\n- SFC structure and template rules are followed.\n- Components are focused and well-factored, splitting when needed.\n- Entry\u002Froot and route view components remain composition surfaces unless there is an explicit small-demo exception.\n- Component split decisions are explicit and defensible (responsibility boundaries are clear).\n- Data flow contracts are explicit and typed.\n- Composables are used where reuse\u002Fcomplexity justifies them.\n- Moved state\u002Fside effects into composables if applicable\n- Optional features are used only when requirements demand them.\n- Performance changes were applied only after functionality was complete.\n","# Vue Best Practices Workflow\n\nUse this skill as an instruction set. Follow the workflow in order unless the user explicitly asks for a different order.\n\n## Core Principles\n- **Keep state predictable:** one source of truth, derive everything else.\n- **Make data flow explicit:** Props down, Events up for most cases.\n- **Favor small, focused components:** easier to test, reuse, and maintain.\n- **Avoid unnecessary re-renders:** use computed properties and watchers wisely.\n- **Readability counts:** write clear, self-documenting code.\n\n## 1) Confirm architecture before coding (required)\n\n- Default stack: Vue 3 + Composition API + `\u003Cscript setup lang=\"ts\">`.\n- If the project explicitly uses Options API, load `vue-options-api-best-practices` skill if available.\n- If the project explicitly uses JSX, load `vue-jsx-best-practices` skill if available.\n\n### 1.1 Must-read core references (required)\n\n- Before implementing any Vue task, make sure to read and apply these core references:\n  - `references\u002Freactivity.md`\n  - `references\u002Fsfc.md`\n  - `references\u002Fcomponent-data-flow.md`\n  - `references\u002Fcomposables.md`\n- Keep these references in active working context for the entire task, not only when a specific issue appears.\n\n### 1.2 Plan component boundaries before coding (required)\n\nCreate a brief component map before implementation for any non-trivial feature.\n\n- Define each component's single responsibility in one sentence.\n- Keep entry\u002Froot and route-level view components as composition surfaces by default.\n- Move feature UI and feature logic out of entry\u002Froot\u002Fview components unless the task is intentionally a tiny single-file demo.\n- Define props\u002Femits contracts for each child component in the map.\n- Prefer a feature folder layout (`components\u002F\u003Cfeature>\u002F...`, `composables\u002Fuse\u003CFeature>.ts`) when adding more than one component.\n\n## 2) Apply essential Vue foundations (required)\n\nThese are essential, must-know foundations. Apply all of them in every Vue task using the core references already loaded in section `1.1`.\n\n### Reactivity\n\n- Must-read reference from `1.1`: [reactivity](references\u002Freactivity.md)\n- Keep source state minimal (`ref`\u002F`reactive`), derive everything possible with `computed`.\n- Use watchers for side effects if needed.\n- Avoid recomputing expensive logic in templates.\n\n### SFC structure and template safety\n\n- Must-read reference from `1.1`: [sfc](references\u002Fsfc.md)\n- Keep SFC sections in this order: `\u003Cscript>` → `\u003Ctemplate>` → `\u003Cstyle>`.\n- Keep SFC responsibilities focused; split large components.\n- Keep templates declarative; move branching\u002Fderivation to script.\n- Apply Vue template safety rules (`v-html`, list rendering, conditional rendering choices).\n\n### Keep components focused\n\nSplit a component when it has **more than one clear responsibility** (e.g. data orchestration + UI, or multiple independent UI sections).\n\n- Prefer **smaller components + composables** over one “mega component”\n- Move **UI sections** into child components (props in, events out).\n- Move **state\u002Fside effects** into composables (`useXxx()`).\n\nApply objective split triggers. Split the component if **any** condition is true:\n\n- It owns both orchestration\u002Fstate and substantial presentational markup for multiple sections.\n- It has 3+ distinct UI sections (for example: form, filters, list, footer\u002Fstatus).\n- A template block is repeated or could become reusable (item rows, cards, list entries).\n\nEntry\u002Froot and route view rule:\n\n- Keep entry\u002Froot and route view components thin: app shell\u002Flayout, provider wiring, and feature composition.\n- Do not place full feature implementations in entry\u002Froot\u002Fview components when those features contain independent parts.\n- For CRUD\u002Flist features (todo, table, catalog, inbox), split at least into:\n  - feature container component\n  - input\u002Fform component\n  - list (and\u002For item) component\n  - footer\u002Factions or filter\u002Fstatus component\n- Allow a single-file implementation only for very small throwaway demos; if chosen, explicitly justify why splitting is unnecessary.\n\n### Component data flow\n\n- Must-read reference from `1.1`: [component-data-flow](references\u002Fcomponent-data-flow.md)\n- Use props down, events up as the primary model.\n- Use `v-model` only for true two-way component contracts.\n- Use provide\u002Finject only for deep-tree dependencies or shared context.\n- Keep contracts explicit and typed with `defineProps`, `defineEmits`, and `InjectionKey` as needed.\n\n### Composables\n\n- Must-read reference from `1.1`: [composables](references\u002Fcomposables.md)\n- Extract logic into composables when it is reused, stateful, or side-effect heavy.\n- Keep composable APIs small, typed, and predictable.\n- Separate feature logic from presentational components.\n\n## 3) Consider optional features only when requirements call for them\n\n### 3.1 Standard optional features\n\nDo not add these by default. Load the matching reference only when the requirement exists.\n\n- Slots: parent needs to control child content\u002Flayout -> [component-slots](references\u002Fcomponent-slots.md)\n- Fallthrough attributes: wrapper\u002Fbase components must forward attrs\u002Fevents safely -> [component-fallthrough-attrs](references\u002Fcomponent-fallthrough-attrs.md)\n- Built-in component `\u003CKeepAlive>` for stateful view caching -> [component-keep-alive](references\u002Fcomponent-keep-alive.md)\n- Built-in component `\u003CTeleport>` for overlays\u002Fportals -> [component-teleport](references\u002Fcomponent-teleport.md)\n- Built-in component `\u003CSuspense>` for async subtree fallback boundaries -> [component-suspense](references\u002Fcomponent-suspense.md)\n- Animation-related features: pick the simplest approach that matches the required motion behavior.\n  - Built-in component `\u003CTransition>` for enter\u002Fleave effects -> [transition](references\u002Fcomponent-transition.md)\n  - Built-in component `\u003CTransitionGroup>` for animated list mutations -> [transition-group](references\u002Fcomponent-transition-group.md)\n  - Class-based animation for non-enter\u002Fleave effects -> [animation-class-based-technique](references\u002Fanimation-class-based-technique.md)\n  - State-driven animation for user-input-driven animation -> [animation-state-driven-technique](references\u002Fanimation-state-driven-technique.md)\n\n### 3.2 Less-common optional features\n\nUse these only when there is explicit product or technical need.\n\n- Directives: behavior is DOM-specific and not a good composable\u002Fcomponent fit -> [directives](references\u002Fdirectives.md)\n- Async components: heavy\u002Frarely-used UI should be lazy loaded -> [component-async](references\u002Fcomponent-async.md)\n- Render functions only when templates cannot express the requirement -> [render-functions](references\u002Frender-functions.md)\n- Plugins when behavior must be installed app-wide -> [plugins](references\u002Fplugins.md)\n- State management patterns: app-wide shared state crosses feature boundaries -> [state-management](references\u002Fstate-management.md)\n\n## 4) Run performance optimization after behavior is correct\n\nPerformance work is a post-functionality pass. Do not optimize before core behavior is implemented and verified.\n\n- Large list rendering bottlenecks -> [perf-virtualize-large-lists](references\u002Fperf-virtualize-large-lists.md)\n- Static subtrees re-rendering unnecessarily -> [perf-v-once-v-memo-directives](references\u002Fperf-v-once-v-memo-directives.md)\n- Over-abstraction in hot list paths -> [perf-avoid-component-abstraction-in-lists](references\u002Fperf-avoid-component-abstraction-in-lists.md)\n- Expensive updates triggered too often -> [updated-hook-performance](references\u002Fupdated-hook-performance.md)\n\n## 5) Final self-check before finishing\n\n- Core behavior works and matches requirements.\n- All must-read references were read and applied.\n- Reactivity model is minimal and predictable.\n- SFC structure and template rules are followed.\n- Components are focused and well-factored, splitting when needed.\n- Entry\u002Froot and route view components remain composition surfaces unless there is an explicit small-demo exception.\n- Component split decisions are explicit and defensible (responsibility boundaries are clear).\n- Data flow contracts are explicit and typed.\n- Composables are used where reuse\u002Fcomplexity justifies them.\n- Moved state\u002Fside effects into composables if applicable\n- Optional features are used only when requirements demand them.\n- Performance changes were applied only after functionality was complete.\n",{"name":5,"license":15,"metadata":25,"description":7},{"author":26,"version":27},"github.com\u002Fvuejs-ai","18.0.0","master","c247302c836de6438d746b45670990eb71691166","skills_collected\u002Fantfu--skills--skills__vue-best-practices",1,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool","https:\u002F\u002Fgithub.com\u002Fqhjqhj00","chien.io","2026-05-11 15:07:59",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add qhjqhj00\u002Fresearch-skills-pool --skill vue-best-practices",{"tool":42,"command":43},"bunx","bunx skills add qhjqhj00\u002Fresearch-skills-pool --skill vue-best-practices",{"tool":45,"command":46},"pnpm","pnpm dlx skills add qhjqhj00\u002Fresearch-skills-pool --skill vue-best-practices","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002FSKILL.md",true,[50,55,61,65,69,73,77,81,85,89,93,97,101,105,109,113,117,121,125,129,133,137,141,145],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":16},"LICENSE.md","LICENSE","许可证",1098,{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fanimation-class-based-technique.md","REFERENCE","参考文档",5026,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fanimation-class-based-technique.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fanimation-state-driven-technique.md",5829,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fanimation-state-driven-technique.md",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fcomponent-async.md",2532,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fcomponent-async.md",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fcomponent-data-flow.md",6956,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fcomponent-data-flow.md",{"path":74,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fcomponent-fallthrough-attrs.md",4047,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fcomponent-fallthrough-attrs.md",{"path":78,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fcomponent-keep-alive.md",3487,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fcomponent-keep-alive.md",{"path":82,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fcomponent-slots.md",4469,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fcomponent-slots.md",{"path":86,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fcomponent-suspense.md",5367,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fcomponent-suspense.md",{"path":90,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fcomponent-teleport.md",2921,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fcomponent-teleport.md",{"path":94,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fcomponent-transition-group.md",3004,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fcomponent-transition-group.md",{"path":98,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fcomponent-transition.md",2722,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fcomponent-transition.md",{"path":102,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fcomposables.md",7011,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fcomposables.md",{"path":106,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fdirectives.md",3803,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fdirectives.md",{"path":110,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fperf-avoid-component-abstraction-in-lists.md",4683,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fperf-avoid-component-abstraction-in-lists.md",{"path":114,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fperf-v-once-v-memo-directives.md",4769,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fperf-v-once-v-memo-directives.md",{"path":118,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Fperf-virtualize-large-lists.md",5002,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fperf-virtualize-large-lists.md",{"path":122,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":123,"sourceHtmlUrl":124},"references\u002Fplugins.md",3882,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fplugins.md",{"path":126,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":127,"sourceHtmlUrl":128},"references\u002Freactivity.md",8452,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Freactivity.md",{"path":130,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":131,"sourceHtmlUrl":132},"references\u002Frender-functions.md",3866,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Frender-functions.md",{"path":134,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":135,"sourceHtmlUrl":136},"references\u002Fsfc.md",6216,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fsfc.md",{"path":138,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":139,"sourceHtmlUrl":140},"references\u002Fstate-management.md",3380,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fstate-management.md",{"path":142,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":143,"sourceHtmlUrl":144},"references\u002Fupdated-hook-performance.md",4618,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002Freferences\u002Fupdated-hook-performance.md",{"path":146,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":147,"sourceHtmlUrl":148},"SYNC.md",154,"https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Fskills_collected\u002Fantfu--skills--skills__vue-best-practices\u002FSYNC.md",[150,157,164,171,178,185],{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":20},"01M73JJB6EQPFPPVQK2Y9N67Q0","transformer-lens-interpretability","Provides guidance for mechanistic interpretability research using TransformerLens to inspect and manipulate transformer internals via HookPoints and activation caching. Use when reverse-engineering model algorithms, studying attention patterns, or performing activation patching experiments.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F130-transformer-lens\u002FSKILL.md",[],[],{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":20},"01M73JHTANRRWEE9HP98TPEHAY","wiki-vitepress","Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output. Use when the user wants to create a browsable website from generated wiki pages.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F126-wiki-vitepress\u002FSKILL.md",[],[],{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":20},"01M73JHJBMVFW46F1Y8K3SBF43","phoenix-observability","Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F124-phoenix\u002FSKILL.md",[],[],{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":20},"01M73JHFPA3A2806PMP42ZN86Q","frontend-ui-dark-ts","Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F123-frontend-ui-dark-ts\u002FSKILL.md",[],[],{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":20},"01M73JFVBVK57NRJS49TT2VDCT","tensorboard","Visualize training metrics, debug models with histograms, compare experiments, visualize model graphs, and profile performance with TensorBoard - Google's ML visualization toolkit","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F113-tensorboard\u002FSKILL.md",[],[],{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":189,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":192,"publishedAt":20},"01M73JFF6PK6ZCN41C89J7HS2B","markdown-mermaid-writing","Comprehensive markdown and Mermaid diagram writing skill. Use when creating any scientific document, report, analysis, or visualization. Establishes text-based diagrams as the default documentation standard with full style guides (markdown + mermaid), 24 diagram type references, and 9 document templates.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fqhjqhj00\u002Fresearch-skills-pool\u002Fblob\u002Fmaster\u002Ftop100-runs\u002F110-markdown-mermaid-writing\u002FSKILL.md",[],[]]