[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WZ1AP3GFCBAMD712X8KRP7":3,"skill-same:01M6WZ1AP3GFCBAMD712X8KRP7":83},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":6,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":6,"updatedAt":68,"install":69,"resources":82},"01M6WZ1AP3GFCBAMD712X8KRP7","vue-expert-js",null,"Creates Vue 3 components, builds vanilla JS composables, configures Vite projects, and sets up routing and state management using JavaScript only — no TypeScript. Generates JSDoc-typed code with @typedef, @param, and @returns annotations for full type coverage without a TS compiler. Use when building Vue 3 applications with JavaScript only (no TypeScript), when projects require JSDoc-based type hints, when migrating from Vue 2 Options API to Composition API in JS, or when teams prefer vanilla JavaScript, .mjs modules, or need quick prototypes without TypeScript setup.","PIXARTSeu\u002FSynapse","PIXARTSeu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F274446381?v=4","01M6RB4XPN9YBZCRY4FVN9PJCT","Pixarts ","01M6RB4XTF8G9KHQEMC21FGDKD",12,"MIT","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fvue-expert-js\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"vue","vue expert","vue expert js","js","expert","only","when","quick","jsdoc","options","modules","up","frontend","coverage","projects","Composition","api","code","components","typescript","2026-11-10 10:12:30",false,"---\nname: vue-expert-js\ndescription: Creates Vue 3 components, builds vanilla JS composables, configures Vite projects, and sets up routing and state management using JavaScript only — no TypeScript. Generates JSDoc-typed code with @typedef, @param, and @returns annotations for full type coverage without a TS compiler. Use when building Vue 3 applications with JavaScript only (no TypeScript), when projects require JSDoc-based type hints, when migrating from Vue 2 Options API to Composition API in JS, or when teams prefer vanilla JavaScript, .mjs modules, or need quick prototypes without TypeScript setup.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: frontend\n  triggers: Vue JavaScript, Vue without TypeScript, Vue JSDoc, Vue JS only, Vue vanilla JavaScript, .mjs Vue, Vue no TS\n  role: specialist\n  scope: implementation\n  output-format: code\n  related-skills: vue-expert, javascript-pro\n---\n\n# Vue Expert (JavaScript)\n\nSenior Vue specialist building Vue 3 applications with JavaScript and JSDoc typing instead of TypeScript.\n\n## Core Workflow\n\n1. **Design architecture** — Plan component structure and composables with JSDoc type annotations\n2. **Implement** — Build with `\u003Cscript setup>` (no `lang=\"ts\"`), `.mjs` modules where needed\n3. **Annotate** — Add comprehensive JSDoc comments (`@typedef`, `@param`, `@returns`, `@type`) for full type coverage; then run ESLint with the JSDoc plugin (`eslint-plugin-jsdoc`) to verify coverage — fix any missing or malformed annotations before proceeding\n4. **Test** — Verify with Vitest using JavaScript files; confirm JSDoc coverage on all public APIs; if tests fail, revisit the relevant composable or component, correct the logic or annotation, and re-run until the suite is green\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| JSDoc Typing | `references\u002Fjsdoc-typing.md` | JSDoc types, @typedef, @param, type hints |\n| Composables | `references\u002Fcomposables-patterns.md` | custom composables, ref, reactive, lifecycle hooks |\n| Components | `references\u002Fcomponent-architecture.md` | props, emits, slots, provide\u002Finject |\n| State | `references\u002Fstate-management.md` | Pinia, stores, reactive state |\n| Testing | `references\u002Ftesting-patterns.md` | Vitest, component testing, mocking |\n\n**For shared Vue concepts, defer to vue-expert:**\n- `vue-expert\u002Freferences\u002Fcomposition-api.md` - Core reactivity patterns\n- `vue-expert\u002Freferences\u002Fcomponents.md` - Props, emits, slots\n- `vue-expert\u002Freferences\u002Fstate-management.md` - Pinia stores\n\n## Code Patterns\n\n### Component with JSDoc-typed props and emits\n\n```vue\n\u003Cscript setup>\n\u002F**\n * @typedef {Object} UserCardProps\n * @property {string} name - Display name of the user\n * @property {number} age - User's age\n * @property {boolean} [isAdmin=false] - Whether the user has admin rights\n *\u002F\n\n\u002F** @type {UserCardProps} *\u002F\nconst props = defineProps({\n  name:    { type: String,  required: true },\n  age:     { type: Number,  required: true },\n  isAdmin: { type: Boolean, default: false },\n})\n\n\u002F**\n * @typedef {Object} UserCardEmits\n * @property {(id: string) => void} select - Emitted when the card is selected\n *\u002F\nconst emit = defineEmits(['select'])\n\n\u002F** @param {string} id *\u002F\nfunction handleSelect(id) {\n  emit('select', id)\n}\n\u003C\u002Fscript>\n\n\u003Ctemplate>\n  \u003Cdiv @click=\"handleSelect(props.name)\">\n    {{ props.name }} ({{ props.age }})\n  \u003C\u002Fdiv>\n\u003C\u002Ftemplate>\n```\n\n### Composable with @typedef, @param, and @returns\n\n```js\n\u002F\u002F composables\u002FuseCounter.mjs\nimport { ref, computed } from 'vue'\n\n\u002F**\n * @typedef {Object} CounterState\n * @property {import('vue').Ref\u003Cnumber>} count - Reactive count value\n * @property {import('vue').ComputedRef\u003Cboolean>} isPositive - True when count > 0\n * @property {() => void} increment - Increases count by step\n * @property {() => void} reset - Resets count to initial value\n *\u002F\n\n\u002F**\n * Composable for a simple counter with configurable step.\n * @param {number} [initial=0] - Starting value\n * @param {number} [step=1]    - Amount to increment per call\n * @returns {CounterState}\n *\u002F\nexport function useCounter(initial = 0, step = 1) {\n  \u002F** @type {import('vue').Ref\u003Cnumber>} *\u002F\n  const count = ref(initial)\n\n  const isPositive = computed(() => count.value > 0)\n\n  function increment() {\n    count.value += step\n  }\n\n  function reset() {\n    count.value = initial\n  }\n\n  return { count, isPositive, increment, reset }\n}\n```\n\n### @typedef for a complex object used across files\n\n```js\n\u002F\u002F types\u002Fuser.mjs\n\n\u002F**\n * @typedef {Object} User\n * @property {string}   id       - UUID\n * @property {string}   name     - Full display name\n * @property {string}   email    - Contact email\n * @property {'admin'|'viewer'} role - Access level\n *\u002F\n\n\u002F\u002F Import in other files with:\n\u002F\u002F \u002F** @type {import('.\u002Ftypes\u002Fuser.mjs').User} *\u002F\n```\n\n## Constraints\n\n### MUST DO\n- Use Composition API with `\u003Cscript setup>`\n- Use JSDoc comments for type documentation\n- Use `.mjs` extension for ES modules when needed\n- Annotate every public function with `@param` and `@returns`\n- Use `@typedef` for complex object shapes shared across files\n- Use `@type` annotations for reactive variables\n- Follow vue-expert patterns adapted for JavaScript\n\n### MUST NOT DO\n- Use TypeScript syntax (no `\u003Cscript setup lang=\"ts\">`)\n- Use `.ts` file extensions\n- Skip JSDoc types for public APIs\n- Use CommonJS `require()` in Vue files\n- Ignore type safety entirely\n- Mix TypeScript files with JavaScript in the same component\n\n## Output Templates\n\nWhen implementing Vue features in JavaScript:\n1. Component file with `\u003Cscript setup>` (no lang attribute) and JSDoc-typed props\u002Femits\n2. `@typedef` definitions for complex prop or state shapes\n3. Composable with `@param` and `@returns` annotations\n4. Brief note on type coverage\n\n## Knowledge Reference\n\nVue 3 Composition API, JSDoc, ESM modules, Pinia, Vue Router 4, Vite, VueUse, Vitest, Vue Test Utils, JavaScript ES2022+\n","# Vue Expert (JavaScript)\n\nSenior Vue specialist building Vue 3 applications with JavaScript and JSDoc typing instead of TypeScript.\n\n## Core Workflow\n\n1. **Design architecture** — Plan component structure and composables with JSDoc type annotations\n2. **Implement** — Build with `\u003Cscript setup>` (no `lang=\"ts\"`), `.mjs` modules where needed\n3. **Annotate** — Add comprehensive JSDoc comments (`@typedef`, `@param`, `@returns`, `@type`) for full type coverage; then run ESLint with the JSDoc plugin (`eslint-plugin-jsdoc`) to verify coverage — fix any missing or malformed annotations before proceeding\n4. **Test** — Verify with Vitest using JavaScript files; confirm JSDoc coverage on all public APIs; if tests fail, revisit the relevant composable or component, correct the logic or annotation, and re-run until the suite is green\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| JSDoc Typing | `references\u002Fjsdoc-typing.md` | JSDoc types, @typedef, @param, type hints |\n| Composables | `references\u002Fcomposables-patterns.md` | custom composables, ref, reactive, lifecycle hooks |\n| Components | `references\u002Fcomponent-architecture.md` | props, emits, slots, provide\u002Finject |\n| State | `references\u002Fstate-management.md` | Pinia, stores, reactive state |\n| Testing | `references\u002Ftesting-patterns.md` | Vitest, component testing, mocking |\n\n**For shared Vue concepts, defer to vue-expert:**\n- `vue-expert\u002Freferences\u002Fcomposition-api.md` - Core reactivity patterns\n- `vue-expert\u002Freferences\u002Fcomponents.md` - Props, emits, slots\n- `vue-expert\u002Freferences\u002Fstate-management.md` - Pinia stores\n\n## Code Patterns\n\n### Component with JSDoc-typed props and emits\n\n```vue\n\u003Cscript setup>\n\u002F**\n * @typedef {Object} UserCardProps\n * @property {string} name - Display name of the user\n * @property {number} age - User's age\n * @property {boolean} [isAdmin=false] - Whether the user has admin rights\n *\u002F\n\n\u002F** @type {UserCardProps} *\u002F\nconst props = defineProps({\n  name:    { type: String,  required: true },\n  age:     { type: Number,  required: true },\n  isAdmin: { type: Boolean, default: false },\n})\n\n\u002F**\n * @typedef {Object} UserCardEmits\n * @property {(id: string) => void} select - Emitted when the card is selected\n *\u002F\nconst emit = defineEmits(['select'])\n\n\u002F** @param {string} id *\u002F\nfunction handleSelect(id) {\n  emit('select', id)\n}\n\u003C\u002Fscript>\n\n\u003Ctemplate>\n  \u003Cdiv @click=\"handleSelect(props.name)\">\n    {{ props.name }} ({{ props.age }})\n  \u003C\u002Fdiv>\n\u003C\u002Ftemplate>\n```\n\n### Composable with @typedef, @param, and @returns\n\n```js\n\u002F\u002F composables\u002FuseCounter.mjs\nimport { ref, computed } from 'vue'\n\n\u002F**\n * @typedef {Object} CounterState\n * @property {import('vue').Ref\u003Cnumber>} count - Reactive count value\n * @property {import('vue').ComputedRef\u003Cboolean>} isPositive - True when count > 0\n * @property {() => void} increment - Increases count by step\n * @property {() => void} reset - Resets count to initial value\n *\u002F\n\n\u002F**\n * Composable for a simple counter with configurable step.\n * @param {number} [initial=0] - Starting value\n * @param {number} [step=1]    - Amount to increment per call\n * @returns {CounterState}\n *\u002F\nexport function useCounter(initial = 0, step = 1) {\n  \u002F** @type {import('vue').Ref\u003Cnumber>} *\u002F\n  const count = ref(initial)\n\n  const isPositive = computed(() => count.value > 0)\n\n  function increment() {\n    count.value += step\n  }\n\n  function reset() {\n    count.value = initial\n  }\n\n  return { count, isPositive, increment, reset }\n}\n```\n\n### @typedef for a complex object used across files\n\n```js\n\u002F\u002F types\u002Fuser.mjs\n\n\u002F**\n * @typedef {Object} User\n * @property {string}   id       - UUID\n * @property {string}   name     - Full display name\n * @property {string}   email    - Contact email\n * @property {'admin'|'viewer'} role - Access level\n *\u002F\n\n\u002F\u002F Import in other files with:\n\u002F\u002F \u002F** @type {import('.\u002Ftypes\u002Fuser.mjs').User} *\u002F\n```\n\n## Constraints\n\n### MUST DO\n- Use Composition API with `\u003Cscript setup>`\n- Use JSDoc comments for type documentation\n- Use `.mjs` extension for ES modules when needed\n- Annotate every public function with `@param` and `@returns`\n- Use `@typedef` for complex object shapes shared across files\n- Use `@type` annotations for reactive variables\n- Follow vue-expert patterns adapted for JavaScript\n\n### MUST NOT DO\n- Use TypeScript syntax (no `\u003Cscript setup lang=\"ts\">`)\n- Use `.ts` file extensions\n- Skip JSDoc types for public APIs\n- Use CommonJS `require()` in Vue files\n- Ignore type safety entirely\n- Mix TypeScript files with JavaScript in the same component\n\n## Output Templates\n\nWhen implementing Vue features in JavaScript:\n1. Component file with `\u003Cscript setup>` (no lang attribute) and JSDoc-typed props\u002Femits\n2. `@typedef` definitions for complex prop or state shapes\n3. Composable with `@param` and `@returns` annotations\n4. Brief note on type coverage\n\n## Knowledge Reference\n\nVue 3 Composition API, JSDoc, ESM modules, Pinia, Vue Router 4, Vite, VueUse, Vitest, Vue Test Utils, JavaScript ES2022+\n",{"name":5,"license":15,"metadata":54,"description":7},{"role":55,"scope":56,"author":57,"domain":41,"version":58,"triggers":59,"output-format":46,"related-skills":60},"specialist","implementation","https:\u002F\u002Fgithub.com\u002FJeffallan","1.1.0","Vue JavaScript, Vue without TypeScript, Vue JSDoc, Vue JS only, Vue vanilla JavaScript, .mjs Vue, Vue no TS","vue-expert, javascript-pro","main","c19c0bc0a04d25a849ce749fe88250e688f06437","packages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fvue-expert-js",1,"https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse","https:\u002F\u002Fgithub.com\u002FPIXARTSeu","https:\u002F\u002Fpixarts.eu\u002F","2026-09-24 06:30:45",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add PIXARTSeu\u002FSynapse --skill vue-expert-js",{"tool":75,"command":76},"bunx","bunx skills add PIXARTSeu\u002FSynapse --skill vue-expert-js",{"tool":78,"command":79},"pnpm","pnpm dlx skills add PIXARTSeu\u002FSynapse --skill vue-expert-js","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fvue-expert-js\u002FSKILL.md",true,[],[84,110,117,142,166,187],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":92,"publishedAt":49},"01M6X0ECZKGP44NP2JW588B9RG","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[90,91],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[93,94,95,96,97,98,99,47,100,101,102,46,103,104,105,106,107,108,109,35],"react","vercel react best practices","best practices","react best practices","vercel","writing","performance","react components","guidelines","tasks","Optimization","data","refactoring","patterns","next","triggers","data fetching",{"skillNo":111,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":116,"publishedAt":49},"01M6X05WCVH879XKZEAQ15PHQX","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Fskill\u002Fvercel-react-best-practices\u002FSKILL.md",[114,115],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[93,94,95,96,97,98,99,47,100,101,102,46,103,104,105,106,107,108,109,35],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":127,"publishedAt":49},"01M6WZ286AR2SYE9GZYVW0CNYG","wordpress-pro","Develops custom WordPress themes and plugins, creates and registers Gutenberg blocks and block patterns, configures WooCommerce stores, implements WordPress REST API endpoints, applies security hardening (nonces, sanitization, escaping, capability checks), and optimizes performance through caching and query tuning. Use when building WordPress themes, writing plugins, customizing Gutenberg blocks, extending WooCommerce, working with ACF, using the WordPress REST API, applying hooks and filters, or improving WordPress performance and security.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fwordpress-pro\u002FSKILL.md",[123,126],{"categoryNo":124,"categoryName":125,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[128,129,130,98,131,99,46,132,45,133,134,135,136,33,137,138,139,140,141,35],"wordpress","wordpress pro","pro","security","tuning","laravel","reviewer","hooks","filters","query","woocommerce","caching","themes","sanitization",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":150,"publishedAt":49},"01M6WZ1ZVG6PJ4PVN9RTK0BX7Z","websocket-engineer","Use when building real-time communication systems with WebSockets or Socket.IO. Invoke for bidirectional messaging, horizontal scaling with Redis, presence tracking, room management.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fwebsocket-engineer\u002FSKILL.md",[148,149],{"categoryNo":124,"categoryName":125,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[151,152,153,154,46,155,156,45,134,157,33,158,159,160,161,162,163,164,165,35],"websocket","engineer","websocket engineer","architecture","messaging","monitoring","fastapi","time","scaling","io","communication systems","presence","updates","socket","invoke",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":175,"publishedAt":49},"01M6WZ1G86ZR73H0WNM6CGNRGF","vue-expert","Builds Vue 3 components with Composition API patterns, configures Nuxt 3 SSR\u002FSSG projects, sets up Pinia stores, scaffolds Quasar\u002FCapacitor mobile apps, implements PWA features, and optimises Vite builds. Use when creating Vue 3 applications with Composition API, writing reusable composables, managing state with Pinia, building hybrid mobile apps with Quasar or Capacitor, configuring service workers, or tuning Vite configuration and TypeScript integration.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fvue-expert\u002FSKILL.md",[172,173,174],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":124,"categoryName":125,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[29,33,30,41,98,48,47,176,177,44,43,178,179,180,181,182,183,184,185,186],"config","applications","pinia","use","router","workers","mobile","reusable","worker","apps","hybrid",{"skillNo":188,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":193,"publishedAt":49},"01M6WZ127DV7RTQA917MKYB755","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fvercel-react-best-practices\u002FSKILL.md",[191,192],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[93,94,95,96,97,98,99,47,100,101,102,46,103,104,105,106,107,108,109,35]]