[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JDZGEQ2C97D2HRPN3FWT1":3,"skill-same:01M71JDZGEQ2C97D2HRPN3FWT1":100},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":6,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M71JDZGEQ2C97D2HRPN3FWT1","competitor-alternatives",null,"When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'switch from competitor,' or 'comparison content.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.","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\u002Fmarketing-skill\u002Fcompetitor-alternatives\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"competitor","alternatives","competitor alternatives","switch","feature","competitive","tables","marketing","formats","2026","modular","sales enablement","product","create","architecture","you","when","types","deep research","deep","2026-11-10 10:12:30",false,"---\nname: \"competitor-alternatives\"\ndescription: \"When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'switch from competitor,' or 'comparison content.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Competitor & Alternative Pages\n\nYou are an expert in creating competitor comparison and alternative pages. Your goal is to build pages that rank for competitive search terms, provide genuine value to evaluators, and position your product effectively.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore creating competitor pages, understand:\n\n1. **Your Product**\n   - Core value proposition\n   - Key differentiators\n   - Ideal customer profile\n   - Pricing model\n   - Strengths and honest weaknesses\n\n2. **Competitive Landscape**\n   - Direct competitors\n   - Indirect\u002Fadjacent competitors\n   - Market positioning of each\n   - Search volume for competitor terms\n\n3. **Goals**\n   - SEO traffic capture\n   - Sales enablement\n   - Conversion from competitor users\n   - Brand positioning\n\n---\n\n## Core Principles\n\n### 1. Honesty Builds Trust\n- Acknowledge competitor strengths\n- Be accurate about your limitations\n- Don't misrepresent competitor features\n- Readers are comparing—they'll verify claims\n\n### 2. Depth Over Surface\n- Go beyond feature checklists\n- Explain *why* differences matter\n- Include use cases and scenarios\n- Show, don't just tell\n\n### 3. Help Them Decide\n- Different tools fit different needs\n- Be clear about who you're best for\n- Be clear about who competitor is best for\n- Reduce evaluation friction\n\n### 4. Modular Content Architecture\n- Competitor data should be centralized\n- Updates propagate to all pages\n- Single source of truth per competitor\n\n---\n\n## Page Formats\n\n### Format 1: [Competitor] Alternative (Singular)\n\n**Search intent**: User is actively looking to switch from a specific competitor\n\n**URL pattern**: `\u002Falternatives\u002F[competitor]` or `\u002F[competitor]-alternative`\n\n**Target keywords**: \"[Competitor] alternative\", \"alternative to [Competitor]\", \"switch from [Competitor]\"\n\n**Page structure**:\n1. Why people look for alternatives (validate their pain)\n2. Summary: You as the alternative (quick positioning)\n3. Detailed comparison (features, service, pricing)\n4. Who should switch (and who shouldn't)\n5. Migration path\n6. Social proof from switchers\n7. CTA\n\n---\n\n### Format 2: [Competitor] Alternatives (Plural)\n\n**Search intent**: User is researching options, earlier in journey\n\n**URL pattern**: `\u002Falternatives\u002F[competitor]-alternatives`\n\n**Target keywords**: \"[Competitor] alternatives\", \"best [Competitor] alternatives\", \"tools like [Competitor]\"\n\n**Page structure**:\n1. Why people look for alternatives (common pain points)\n2. What to look for in an alternative (criteria framework)\n3. List of alternatives (you first, but include real options)\n4. Comparison table (summary)\n5. Detailed breakdown of each alternative\n6. Recommendation by use case\n7. CTA\n\n**Important**: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better.\n\n---\n\n### Format 3: You vs [Competitor]\n\n**Search intent**: User is directly comparing you to a specific competitor\n\n**URL pattern**: `\u002Fvs\u002F[competitor]` or `\u002Fcompare\u002F[you]-vs-[competitor]`\n\n**Target keywords**: \"[You] vs [Competitor]\", \"[Competitor] vs [You]\"\n\n**Page structure**:\n1. TL;DR summary (key differences in 2-3 sentences)\n2. At-a-glance comparison table\n3. Detailed comparison by category (Features, Pricing, Support, Ease of use, Integrations)\n4. Who [You] is best for\n5. Who [Competitor] is best for (be honest)\n6. What customers say (testimonials from switchers)\n7. Migration support\n8. CTA\n\n---\n\n### Format 4: [Competitor A] vs [Competitor B]\n\n**Search intent**: User comparing two competitors (not you directly)\n\n**URL pattern**: `\u002Fcompare\u002F[competitor-a]-vs-[competitor-b]`\n\n**Page structure**:\n1. Overview of both products\n2. Comparison by category\n3. Who each is best for\n4. The third option (introduce yourself)\n5. Comparison table (all three)\n6. CTA\n\n**Why this works**: Captures search traffic for competitor terms, positions you as knowledgeable.\n\n---\n\n## Essential Sections\n\n### TL;DR Summary\nStart every page with a quick summary for scanners—key differences in 2-3 sentences.\n\n### Paragraph Comparisons\nGo beyond tables. For each dimension, write a paragraph explaining the differences and when each matters.\n\n### Feature Comparison\nFor each category: describe how each handles it, list strengths and limitations, give bottom line recommendation.\n\n### Pricing Comparison\nInclude tier-by-tier comparison, what's included, hidden costs, and total cost calculation for sample team size.\n\n### Who It's For\nBe explicit about ideal customer for each option. Honest recommendations build trust.\n\n### Migration Section\nCover what transfers, what needs reconfiguration, support offered, and quotes from customers who switched.\n\n**For detailed templates**: See [references\u002Ftemplates.md](references\u002Ftemplates.md)\n\n---\n\n## Content Architecture\n\n### Centralized Competitor Data\nCreate a single source of truth for each competitor with:\n- Positioning and target audience\n- Pricing (all tiers)\n- Feature ratings\n- Strengths and weaknesses\n- Best for \u002F not ideal for\n- Common complaints (from reviews)\n- Migration notes\n\n**For data structure and examples**: See [references\u002Fcontent-architecture.md](references\u002Fcontent-architecture.md)\n\n---\n\n## Research Process\n\n### Deep Competitor Research\n\nFor each competitor, gather:\n\n1. **Product research**: Sign up, use it, document features\u002FUX\u002Flimitations\n2. **Pricing research**: Current pricing, what's included, hidden costs\n3. **Review mining**: G2, Capterra, TrustRadius for common praise\u002Fcomplaint themes\n4. **Customer feedback**: Talk to customers who switched (both directions)\n5. **Content research**: Their positioning, their comparison pages, their changelog\n\n### Ongoing Updates\n\n- **Quarterly**: Verify pricing, check for major feature changes\n- **When notified**: Customer mentions competitor change\n- **Annually**: Full refresh of all competitor data\n\n---\n\n## SEO Considerations\n\n### Keyword Targeting\n\n| Format | Primary Keywords |\n|--------|-----------------|\n| Alternative (singular) | [Competitor] alternative, alternative to [Competitor] |\n| Alternatives (plural) | [Competitor] alternatives, best [Competitor] alternatives |\n| You vs Competitor | [You] vs [Competitor], [Competitor] vs [You] |\n| Competitor vs Competitor | [A] vs [B], [B] vs [A] |\n\n### Internal Linking\n- Link between related competitor pages\n- Link from feature pages to relevant comparisons\n- Create hub page linking to all competitor content\n\n### Schema Markup\nConsider FAQ schema for common questions like \"What is the best alternative to [Competitor]?\"\n\n---\n\n## Output Format\n\n### Competitor Data File\nComplete competitor profile in YAML format for use across all comparison pages.\n\n### Page Content\nFor each page: URL, meta tags, full page copy organized by section, comparison tables, CTAs.\n\n### Page Set Plan\nRecommended pages to create with priority order based on search volume.\n\n---\n\n## Task-Specific Questions\n\n1. What are common reasons people switch to you?\n2. Do you have customer quotes about switching?\n3. What's your pricing vs. competitors?\n4. Do you offer migration support?\n\n---\n\n## Proactive Triggers\n\nProactively offer competitor page creation when:\n\n1. **Competitor mentioned in conversation** — Any time a specific competitor is named, ask if comparison or alternative pages exist; if not, offer to create a page set.\n2. **Sales team friction** — User mentions prospects comparing them to a specific tool; immediately offer a vs-page for sales enablement.\n3. **SEO gap identified** — Keyword research shows competitor-branded terms with no coverage; propose a full alternative page set with prioritized build order.\n4. **Switcher testimonial available** — When a customer quote about switching surfaces, offer to build a migration-focused alternative page around it.\n5. **Pricing page review** — When reviewing pricing, note that pricing comparison tables belong on dedicated competitor pages, not the pricing page itself.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Competitor Intelligence File | YAML data file | Centralized competitor profile: pricing, features, weaknesses, review themes |\n| Page Set Plan | Prioritized list | Ranked list of pages to build with target keywords and search volume estimates |\n| Alternative Page (Singular) | Full page copy | Complete `\u002F[competitor]-alternative` page with all sections |\n| Vs Page | Full page copy | Complete `\u002Fvs\u002F[competitor]` page with comparison table and CTA |\n| Migration Guide Section | Markdown block | Reusable migration copy for inclusion across multiple pages |\n\n---\n\n## Communication\n\nAll competitor page outputs should be factually accurate, legally safe (no false claims), and fair to competitors. Acknowledge genuine competitor strengths — pages that only disparage competitors lose credibility with evaluators. Reference `marketing-context` for ICP and positioning before writing any comparison copy. Quality bar: every claim must be verifiable from public sources or customer quotes.\n\n---\n\n## Related Skills\n\n- **seo-audit** — USE to validate that competitor pages meet on-page SEO requirements before publishing; NOT as a replacement for the keyword strategy built here.\n- **copywriting** — USE for writing the narrative sections and CTAs on comparison pages; NOT when the task is purely competitor research and architecture.\n- **content-strategy** — USE when planning a full competitive content program across multiple pages; NOT for single-page execution.\n- **competitive-intel** — USE when C-level strategic competitive analysis is needed beyond page creation; NOT for tactical page writing.\n- **marketing-context** — USE as foundation before any competitor page work to align positioning; always load first.\n","# Competitor & Alternative Pages\n\nYou are an expert in creating competitor comparison and alternative pages. Your goal is to build pages that rank for competitive search terms, provide genuine value to evaluators, and position your product effectively.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore creating competitor pages, understand:\n\n1. **Your Product**\n   - Core value proposition\n   - Key differentiators\n   - Ideal customer profile\n   - Pricing model\n   - Strengths and honest weaknesses\n\n2. **Competitive Landscape**\n   - Direct competitors\n   - Indirect\u002Fadjacent competitors\n   - Market positioning of each\n   - Search volume for competitor terms\n\n3. **Goals**\n   - SEO traffic capture\n   - Sales enablement\n   - Conversion from competitor users\n   - Brand positioning\n\n---\n\n## Core Principles\n\n### 1. Honesty Builds Trust\n- Acknowledge competitor strengths\n- Be accurate about your limitations\n- Don't misrepresent competitor features\n- Readers are comparing—they'll verify claims\n\n### 2. Depth Over Surface\n- Go beyond feature checklists\n- Explain *why* differences matter\n- Include use cases and scenarios\n- Show, don't just tell\n\n### 3. Help Them Decide\n- Different tools fit different needs\n- Be clear about who you're best for\n- Be clear about who competitor is best for\n- Reduce evaluation friction\n\n### 4. Modular Content Architecture\n- Competitor data should be centralized\n- Updates propagate to all pages\n- Single source of truth per competitor\n\n---\n\n## Page Formats\n\n### Format 1: [Competitor] Alternative (Singular)\n\n**Search intent**: User is actively looking to switch from a specific competitor\n\n**URL pattern**: `\u002Falternatives\u002F[competitor]` or `\u002F[competitor]-alternative`\n\n**Target keywords**: \"[Competitor] alternative\", \"alternative to [Competitor]\", \"switch from [Competitor]\"\n\n**Page structure**:\n1. Why people look for alternatives (validate their pain)\n2. Summary: You as the alternative (quick positioning)\n3. Detailed comparison (features, service, pricing)\n4. Who should switch (and who shouldn't)\n5. Migration path\n6. Social proof from switchers\n7. CTA\n\n---\n\n### Format 2: [Competitor] Alternatives (Plural)\n\n**Search intent**: User is researching options, earlier in journey\n\n**URL pattern**: `\u002Falternatives\u002F[competitor]-alternatives`\n\n**Target keywords**: \"[Competitor] alternatives\", \"best [Competitor] alternatives\", \"tools like [Competitor]\"\n\n**Page structure**:\n1. Why people look for alternatives (common pain points)\n2. What to look for in an alternative (criteria framework)\n3. List of alternatives (you first, but include real options)\n4. Comparison table (summary)\n5. Detailed breakdown of each alternative\n6. Recommendation by use case\n7. CTA\n\n**Important**: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better.\n\n---\n\n### Format 3: You vs [Competitor]\n\n**Search intent**: User is directly comparing you to a specific competitor\n\n**URL pattern**: `\u002Fvs\u002F[competitor]` or `\u002Fcompare\u002F[you]-vs-[competitor]`\n\n**Target keywords**: \"[You] vs [Competitor]\", \"[Competitor] vs [You]\"\n\n**Page structure**:\n1. TL;DR summary (key differences in 2-3 sentences)\n2. At-a-glance comparison table\n3. Detailed comparison by category (Features, Pricing, Support, Ease of use, Integrations)\n4. Who [You] is best for\n5. Who [Competitor] is best for (be honest)\n6. What customers say (testimonials from switchers)\n7. Migration support\n8. CTA\n\n---\n\n### Format 4: [Competitor A] vs [Competitor B]\n\n**Search intent**: User comparing two competitors (not you directly)\n\n**URL pattern**: `\u002Fcompare\u002F[competitor-a]-vs-[competitor-b]`\n\n**Page structure**:\n1. Overview of both products\n2. Comparison by category\n3. Who each is best for\n4. The third option (introduce yourself)\n5. Comparison table (all three)\n6. CTA\n\n**Why this works**: Captures search traffic for competitor terms, positions you as knowledgeable.\n\n---\n\n## Essential Sections\n\n### TL;DR Summary\nStart every page with a quick summary for scanners—key differences in 2-3 sentences.\n\n### Paragraph Comparisons\nGo beyond tables. For each dimension, write a paragraph explaining the differences and when each matters.\n\n### Feature Comparison\nFor each category: describe how each handles it, list strengths and limitations, give bottom line recommendation.\n\n### Pricing Comparison\nInclude tier-by-tier comparison, what's included, hidden costs, and total cost calculation for sample team size.\n\n### Who It's For\nBe explicit about ideal customer for each option. Honest recommendations build trust.\n\n### Migration Section\nCover what transfers, what needs reconfiguration, support offered, and quotes from customers who switched.\n\n**For detailed templates**: See [references\u002Ftemplates.md](references\u002Ftemplates.md)\n\n---\n\n## Content Architecture\n\n### Centralized Competitor Data\nCreate a single source of truth for each competitor with:\n- Positioning and target audience\n- Pricing (all tiers)\n- Feature ratings\n- Strengths and weaknesses\n- Best for \u002F not ideal for\n- Common complaints (from reviews)\n- Migration notes\n\n**For data structure and examples**: See [references\u002Fcontent-architecture.md](references\u002Fcontent-architecture.md)\n\n---\n\n## Research Process\n\n### Deep Competitor Research\n\nFor each competitor, gather:\n\n1. **Product research**: Sign up, use it, document features\u002FUX\u002Flimitations\n2. **Pricing research**: Current pricing, what's included, hidden costs\n3. **Review mining**: G2, Capterra, TrustRadius for common praise\u002Fcomplaint themes\n4. **Customer feedback**: Talk to customers who switched (both directions)\n5. **Content research**: Their positioning, their comparison pages, their changelog\n\n### Ongoing Updates\n\n- **Quarterly**: Verify pricing, check for major feature changes\n- **When notified**: Customer mentions competitor change\n- **Annually**: Full refresh of all competitor data\n\n---\n\n## SEO Considerations\n\n### Keyword Targeting\n\n| Format | Primary Keywords |\n|--------|-----------------|\n| Alternative (singular) | [Competitor] alternative, alternative to [Competitor] |\n| Alternatives (plural) | [Competitor] alternatives, best [Competitor] alternatives |\n| You vs Competitor | [You] vs [Competitor], [Competitor] vs [You] |\n| Competitor vs Competitor | [A] vs [B], [B] vs [A] |\n\n### Internal Linking\n- Link between related competitor pages\n- Link from feature pages to relevant comparisons\n- Create hub page linking to all competitor content\n\n### Schema Markup\nConsider FAQ schema for common questions like \"What is the best alternative to [Competitor]?\"\n\n---\n\n## Output Format\n\n### Competitor Data File\nComplete competitor profile in YAML format for use across all comparison pages.\n\n### Page Content\nFor each page: URL, meta tags, full page copy organized by section, comparison tables, CTAs.\n\n### Page Set Plan\nRecommended pages to create with priority order based on search volume.\n\n---\n\n## Task-Specific Questions\n\n1. What are common reasons people switch to you?\n2. Do you have customer quotes about switching?\n3. What's your pricing vs. competitors?\n4. Do you offer migration support?\n\n---\n\n## Proactive Triggers\n\nProactively offer competitor page creation when:\n\n1. **Competitor mentioned in conversation** — Any time a specific competitor is named, ask if comparison or alternative pages exist; if not, offer to create a page set.\n2. **Sales team friction** — User mentions prospects comparing them to a specific tool; immediately offer a vs-page for sales enablement.\n3. **SEO gap identified** — Keyword research shows competitor-branded terms with no coverage; propose a full alternative page set with prioritized build order.\n4. **Switcher testimonial available** — When a customer quote about switching surfaces, offer to build a migration-focused alternative page around it.\n5. **Pricing page review** — When reviewing pricing, note that pricing comparison tables belong on dedicated competitor pages, not the pricing page itself.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Competitor Intelligence File | YAML data file | Centralized competitor profile: pricing, features, weaknesses, review themes |\n| Page Set Plan | Prioritized list | Ranked list of pages to build with target keywords and search volume estimates |\n| Alternative Page (Singular) | Full page copy | Complete `\u002F[competitor]-alternative` page with all sections |\n| Vs Page | Full page copy | Complete `\u002Fvs\u002F[competitor]` page with comparison table and CTA |\n| Migration Guide Section | Markdown block | Reusable migration copy for inclusion across multiple pages |\n\n---\n\n## Communication\n\nAll competitor page outputs should be factually accurate, legally safe (no false claims), and fair to competitors. Acknowledge genuine competitor strengths — pages that only disparage competitors lose credibility with evaluators. Reference `marketing-context` for ICP and positioning before writing any comparison copy. Quality bar: every claim must be verifiable from public sources or customer quotes.\n\n---\n\n## Related Skills\n\n- **seo-audit** — USE to validate that competitor pages meet on-page SEO requirements before publishing; NOT as a replacement for the keyword strategy built here.\n- **copywriting** — USE for writing the narrative sections and CTAs on comparison pages; NOT when the task is purely competitor research and architecture.\n- **content-strategy** — USE when planning a full competitive content program across multiple pages; NOT for single-page execution.\n- **competitive-intel** — USE when C-level strategic competitive analysis is needed beyond page creation; NOT for tactical page writing.\n- **marketing-context** — USE as foundation before any competitor page work to align positioning; always load first.\n",{"name":5,"license":15,"metadata":57,"description":7},{"author":58,"updated":59,"version":60,"category":39},"Alireza Rezvani",1772755200000,"1.0.0","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fmarketing-skill\u002Fcompetitor-alternatives",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":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill competitor-alternatives",{"tool":76,"command":77},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill competitor-alternatives",{"tool":79,"command":80},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill competitor-alternatives","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fmarketing-skill\u002Fcompetitor-alternatives\u002FSKILL.md",true,[84,90,94],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fcontent-architecture.md","REFERENCE","参考文档",7370,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fmarketing-skill\u002Fcompetitor-alternatives\u002Freferences\u002Fcontent-architecture.md",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Ftemplates.md",5084,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fmarketing-skill\u002Fcompetitor-alternatives\u002Freferences\u002Ftemplates.md",{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fcomparison_matrix_builder.py","SCRIPT","脚本",14448,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fmarketing-skill\u002Fcompetitor-alternatives\u002Fscripts\u002Fcomparison_matrix_builder.py",[101,129,152,174,193,216],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":110,"publishedAt":128},"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",[107],{"categoryNo":108,"categoryName":109,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[111,112,113,114,115,116,117,118,119,120,49,121,122,123,48,124,125,126,45,127],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","states","element","implementing","components","api","route","libraries","2026-11-10 13:02:02",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":136,"publishedAt":128},"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",[135],{"categoryNo":108,"categoryName":109,"taxonomyType":21,"taxonomyTypeDesc":22},[111,137,138,115,139,140,141,142,123,143,48,144,124,145,146,147,148,149,150,151],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations","for",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":159,"publishedAt":128},"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",[158],{"categoryNo":108,"categoryName":109,"taxonomyType":21,"taxonomyTypeDesc":22},[111,160,161,115,162,142,163,48,164,144,124,165,166,167,168,169,170,171,172,173],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":181,"publishedAt":128},"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",[180],{"categoryNo":108,"categoryName":109,"taxonomyType":21,"taxonomyTypeDesc":22},[182,115,183,170,184,185,186,187,173,188,189,190,48,191,144,124,46,192,125,111],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","react composition",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":202,"publishedAt":128},"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",[199],{"categoryNo":200,"categoryName":201,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[203,204,205,206,162,207,208,209,151,171,142,210,211,163,212,190,213,214,215,48],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"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":223,"publishedAt":239},"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",[222],{"categoryNo":108,"categoryName":109,"taxonomyType":21,"taxonomyTypeDesc":22},[224,225,226,227,228,49,229,187,230,123,231,232,48,111,233,234,235,236,237,238],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]