[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HN2GAZG6ASE1Y35CMX70T":3,"skill-same:01M71HN2GAZG6ASE1Y35CMX70T":125},{"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":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":69,"repositoryHtmlUrl":70,"repositoryHomepageUrl":6,"ownerHtmlUrl":71,"ownerBlogUrl":72,"ownerDescription":73,"updatedAt":74,"install":75,"resources":88},"01M71HN2GAZG6ASE1Y35CMX70T","content-creator",null,"Deprecated redirect skill that routes legacy 'content creator' requests to the correct specialist. Use when a user invokes 'content creator', asks to write a blog post, article, guide, or brand voice analysis (routes to content-production), or asks to plan content, build a topic cluster, or create a content calendar (routes to content-strategy). Does not handle requests directly — identifies user intent and redirects to content-production for writing\u002FSEO\u002Fbrand-voice tasks or content-strategy for planning tasks.","iDorgham\u002FWorkspace-Factory","iDorgham","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136521493?v=4","01M6CNGBDAHE4ARW3YJEF4X2FD","Dorgham","01M71E8H3CXZ7DJX59MTM9JEB2",1,"MIT","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcontent-creator\u002FSKILL.md",[18,23,26,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"creator","content","content creator","plan","create","tasks","analysis","when","Legacy","use","writing","strategy","handle","correct","for","seo","planning","blog post","brand","cluster","2026-11-10 10:12:30",false,"---\nname: \"content-creator\"\ndescription: \"Deprecated redirect skill that routes legacy 'content creator' requests to the correct specialist. Use when a user invokes 'content creator', asks to write a blog post, article, guide, or brand voice analysis (routes to content-production), or asks to plan content, build a topic cluster, or create a content calendar (routes to content-strategy). Does not handle requests directly — identifies user intent and redirects to content-production for writing\u002FSEO\u002Fbrand-voice tasks or content-strategy for planning tasks.\"\nlicense: MIT\nmetadata:\n  version: 2.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n  status: deprecated\n---\n\n# Content Creator → Redirected\n\n> **This skill has been split into two specialist skills.** Use the one that matches your intent:\n\n| You want to... | Use this instead |\n|----------------|-----------------|\n| **Write** a blog post, article, or guide | [content-production](..\u002Fcontent-production\u002F) |\n| **Plan** what content to create, topic clusters, calendar | [content-strategy](..\u002Fcontent-strategy\u002F) |\n| **Analyze brand voice** | [content-production](..\u002Fcontent-production\u002F) (includes `brand_voice_analyzer.py`) |\n| **Optimize SEO** for existing content | [content-production](..\u002Fcontent-production\u002F) (includes `seo_optimizer.py`) |\n| **Create social media content** | [social-content](..\u002Fsocial-content\u002F) |\n\n## Why the Change\n\nThe original `content-creator` tried to do everything: planning, writing, SEO, social, brand voice. That made it a jack of all trades. The specialist skills do each job better:\n\n- **content-production** — Full pipeline: research → brief → draft → optimize → publish. Includes all Python tools from the original content-creator.\n- **content-strategy** — Strategic planning: topic clusters, keyword research, content calendars, prioritization frameworks.\n\n## Proactive Triggers\n\n- **User asks \"content creator\"** → Route to content-production (most likely intent is writing).\n- **User asks \"content plan\" or \"what should I write\"** → Route to content-strategy.\n\n## Output Artifacts\n\n| When you ask for... | Routed to... |\n|---------------------|-------------|\n| \"Write a blog post\" | content-production |\n| \"Content calendar\" | content-strategy |\n| \"Brand voice analysis\" | content-production (`brand_voice_analyzer.py`) |\n| \"SEO optimization\" | content-production (`seo_optimizer.py`) |\n\n## Communication\n\nThis is a redirect skill. Route the user to the correct specialist — don't attempt to handle the request here.\n\n## Related Skills\n\n- **content-production**: Full content execution pipeline (successor).\n- **content-strategy**: Content planning and topic selection (successor).\n- **content-humanizer**: Post-processing AI content to sound authentic.\n- **marketing-context**: Foundation context that both successors read.\n","# Content Creator → Redirected\n\n> **This skill has been split into two specialist skills.** Use the one that matches your intent:\n\n| You want to... | Use this instead |\n|----------------|-----------------|\n| **Write** a blog post, article, or guide | [content-production](..\u002Fcontent-production\u002F) |\n| **Plan** what content to create, topic clusters, calendar | [content-strategy](..\u002Fcontent-strategy\u002F) |\n| **Analyze brand voice** | [content-production](..\u002Fcontent-production\u002F) (includes `brand_voice_analyzer.py`) |\n| **Optimize SEO** for existing content | [content-production](..\u002Fcontent-production\u002F) (includes `seo_optimizer.py`) |\n| **Create social media content** | [social-content](..\u002Fsocial-content\u002F) |\n\n## Why the Change\n\nThe original `content-creator` tried to do everything: planning, writing, SEO, social, brand voice. That made it a jack of all trades. The specialist skills do each job better:\n\n- **content-production** — Full pipeline: research → brief → draft → optimize → publish. Includes all Python tools from the original content-creator.\n- **content-strategy** — Strategic planning: topic clusters, keyword research, content calendars, prioritization frameworks.\n\n## Proactive Triggers\n\n- **User asks \"content creator\"** → Route to content-production (most likely intent is writing).\n- **User asks \"content plan\" or \"what should I write\"** → Route to content-strategy.\n\n## Output Artifacts\n\n| When you ask for... | Routed to... |\n|---------------------|-------------|\n| \"Write a blog post\" | content-production |\n| \"Content calendar\" | content-strategy |\n| \"Brand voice analysis\" | content-production (`brand_voice_analyzer.py`) |\n| \"SEO optimization\" | content-production (`seo_optimizer.py`) |\n\n## Communication\n\nThis is a redirect skill. Route the user to the correct specialist — don't attempt to handle the request here.\n\n## Related Skills\n\n- **content-production**: Full content execution pipeline (successor).\n- **content-strategy**: Content planning and topic selection (successor).\n- **content-humanizer**: Post-processing AI content to sound authentic.\n- **marketing-context**: Foundation context that both successors read.\n",{"name":5,"license":15,"metadata":60,"description":7},{"author":61,"status":62,"updated":63,"version":64,"category":65},"Alireza Rezvani","deprecated",1772755200000,"2.0.0","marketing","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcontent-creator",0,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory","https:\u002F\u002Fgithub.com\u002FiDorgham","Dorgham.me","hey I'm Dorgham \r\nI code, I create, and AI codes back. \r\nMaybe we can give AI the chance!! now we begin. 🚀🤖\r\n... . . . git commit -m \"Hello, Future\" ","2026-05-04 18:39:09",{"source":8,"skillName":5,"commands":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill content-creator",{"tool":81,"command":82},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill content-creator",{"tool":84,"command":85},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill content-creator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcontent-creator\u002FSKILL.md",true,[89,95,101,105,109,113,117,121],{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"_AIWF_IMPORT.json","REFERENCE","参考文档",343,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcontent-creator\u002F_AIWF_IMPORT.json",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"assets\u002Fcontent_calendar_template.md","ASSET","资产文件",1610,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcontent-creator\u002Fassets\u002Fcontent_calendar_template.md",{"path":102,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":103,"sourceHtmlUrl":104},"examples\u002Fbrand_voice_analysis_example.md",4992,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcontent-creator\u002Fexamples\u002Fbrand_voice_analysis_example.md",{"path":106,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":107,"sourceHtmlUrl":108},"examples\u002Fseo_optimization_example.md",7309,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcontent-creator\u002Fexamples\u002Fseo_optimization_example.md",{"path":110,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fanalytics_guide.md",8824,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcontent-creator\u002Freferences\u002Fanalytics_guide.md",{"path":114,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fbrand_guidelines.md",6814,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcontent-creator\u002Freferences\u002Fbrand_guidelines.md",{"path":118,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Fcontent_frameworks.md",11170,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcontent-creator\u002Freferences\u002Fcontent_frameworks.md",{"path":122,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":123,"sourceHtmlUrl":124},"references\u002Fsocial_media_optimization.md",10040,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcontent-creator\u002Freferences\u002Fsocial_media_optimization.md",[126,155,176,197,216,238],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":135,"publishedAt":154},"01M71P8WVBMB2X3D24R0YT0B0E","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_view_transitions\u002Fskill.md",[132],{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[136,137,138,139,140,141,142,143,144,145,146,147,148,149,42,150,151,152,39,153],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","components","api","route","libraries","2026-11-10 13:02:02",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":162,"publishedAt":154},"01M71P8TDGHZ289TSAC5VTG2EW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_native_skills\u002Fskill.md",[161],{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},[136,163,164,140,165,166,167,168,149,169,42,40,150,170,171,172,173,174,175,49],"react native","native","vercel react native skills","react native skills","modules","performance","apps","mobile","expo","list","mobile performance","platform","animations",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":183,"publishedAt":154},"01M71P8QK4JF5BYRGYDDGPZQG9","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\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_best_practices\u002Fskill.md",[182],{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},[136,184,185,140,186,168,45,42,187,40,150,188,189,190,191,192,193,194,195,196],"react best practices","vercel react best practices","best practices","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":204,"publishedAt":154},"01M71P8HVEA70K5N6ZVJCG2ED3","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_composition_patterns\u002Fskill.md",[203],{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},[205,140,206,193,207,208,209,210,196,211,212,44,42,213,40,150,214,215,151,136],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","reusable","architecture","react composition",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":225,"publishedAt":154},"01M71P60XXKKP222ZFJRG7R373","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_supabase_supabase_postgres_best_practices\u002Fskill.md",[222],{"categoryNo":223,"categoryName":224,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[226,227,228,229,186,230,231,232,49,194,168,48,233,45,234,44,235,236,237,42],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","schema","impact","Rules","critical","database",{"skillNo":239,"name":240,"nameZh":6,"description":241,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":242,"categories":243,"keywords":245,"publishedAt":261},"01M71P2ZCEJD0PKC458YTP1FJW","portable-text-serialization","Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_serialization\u002Fskill.md",[244],{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},[246,247,248,249,250,146,251,210,252,149,253,254,42,136,255,256,257,258,259,260],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]