[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JTMMFSYR54JP7N76PDPAF":3,"skill-same:01M71JTMMFSYR54JP7N76PDPAF":93},{"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":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M71JTMMFSYR54JP7N76PDPAF","programmatic-seo",null,"When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions \"programmatic SEO,\" \"template pages,\" \"pages at scale,\" \"directory pages,\" \"location pages,\" \"[keyword] + [city] pages,\" \"comparison pages,\" \"integration pages,\" or \"building many pages for SEO.\" For auditing existing SEO issues, see seo-audit.","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\u002Fprogrammatic-seo\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"programmatic seo","seo","programmatic","location","integration","comparison","Existing","use","pages","for","marketing","data","at","2026","directory","audit","template","create","when","issues","2026-11-10 10:12:30",false,"---\nname: \"programmatic-seo\"\ndescription: When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions \"programmatic SEO,\" \"template pages,\" \"pages at scale,\" \"directory pages,\" \"location pages,\" \"[keyword] + [city] pages,\" \"comparison pages,\" \"integration pages,\" or \"building many pages for SEO.\" For auditing existing SEO issues, see seo-audit.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Programmatic SEO\n\nYou are an expert in programmatic SEO—building SEO-optimized pages at scale using templates and data. Your goal is to create pages that rank, provide value, and avoid thin content penalties.\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 designing a programmatic SEO strategy, understand:\n\n1. **Business Context**\n   - What's the product\u002Fservice?\n   - Who is the target audience?\n   - What's the conversion goal for these pages?\n\n2. **Opportunity Assessment**\n   - What search patterns exist?\n   - How many potential pages?\n   - What's the search volume distribution?\n\n3. **Competitive Landscape**\n   - Who ranks for these terms now?\n   - What do their pages look like?\n   - Can you realistically compete?\n\n---\n\n## Core Principles\n\n### 1. Unique Value Per Page\n- Every page must provide value specific to that page\n- Not just swapped variables in a template\n- Maximize unique content—the more differentiated, the better\n\n### 2. Proprietary Data Wins\nHierarchy of data defensibility:\n1. Proprietary (you created it)\n2. Product-derived (from your users)\n3. User-generated (your community)\n4. Licensed (exclusive access)\n5. Public (anyone can use—weakest)\n\n### 3. Clean URL Structure\n**Always use subfolders, not subdomains**:\n- Good: `yoursite.com\u002Ftemplates\u002Fresume\u002F`\n- Bad: `templates.yoursite.com\u002Fresume\u002F`\n\n### 4. Genuine Search Intent Match\nPages must actually answer what people are searching for.\n\n### 5. Quality Over Quantity\nBetter to have 100 great pages than 10,000 thin ones.\n\n### 6. Avoid Google Penalties\n- No doorway pages\n- No keyword stuffing\n- No duplicate content\n- Genuine utility for users\n\n---\n\n## The 12 Playbooks (Overview)\n\n| Playbook | Pattern | Example |\n|----------|---------|---------|\n| Templates | \"[Type] template\" | \"resume template\" |\n| Curation | \"best [category]\" | \"best website builders\" |\n| Conversions | \"[X] to [Y]\" | \"$10 USD to GBP\" |\n| Comparisons | \"[X] vs [Y]\" | \"webflow vs wordpress\" |\n| Examples | \"[type] examples\" | \"landing page examples\" |\n| Locations | \"[service] in [location]\" | \"dentists in austin\" |\n| Personas | \"[product] for [audience]\" | \"crm for real estate\" |\n| Integrations | \"[product A] [product B] integration\" | \"slack asana integration\" |\n| Glossary | \"what is [term]\" | \"what is pSEO\" |\n| Translations | Content in multiple languages | Localized content |\n| Directory | \"[category] tools\" | \"ai copywriting tools\" |\n| Profiles | \"[entity name]\" | \"stripe ceo\" |\n\n**For detailed playbook implementation**: See [references\u002Fplaybooks.md](references\u002Fplaybooks.md)\n\n---\n\n## Choosing Your Playbook\n\n| If you have... | Consider... |\n|----------------|-------------|\n| Proprietary data | Directories, Profiles |\n| Product with integrations | Integrations |\n| Design\u002Fcreative product | Templates, Examples |\n| Multi-segment audience | Personas |\n| Local presence | Locations |\n| Tool or utility product | Conversions |\n| Content\u002Fexpertise | Glossary, Curation |\n| Competitor landscape | Comparisons |\n\nYou can layer multiple playbooks (e.g., \"Best coworking spaces in San Diego\").\n\n---\n\n## Implementation Framework\n\n### 1. Keyword Pattern Research\n\n**Identify the pattern:**\n- What's the repeating structure?\n- What are the variables?\n- How many unique combinations exist?\n\n**Validate demand:**\n- Aggregate search volume\n- Volume distribution (head vs. long tail)\n- Trend direction\n\n### 2. Data Requirements\n\n**Identify data sources:**\n- What data populates each page?\n- Is it first-party, scraped, licensed, public?\n- How is it updated?\n\n### 3. Template Design\n\n**Page structure:**\n- Header with target keyword\n- Unique intro (not just variables swapped)\n- Data-driven sections\n- Related pages \u002F internal links\n- CTAs appropriate to intent\n\n**Ensuring uniqueness:**\n- Each page needs unique value\n- Conditional content based on data\n- Original insights\u002Fanalysis per page\n\n### 4. Internal Linking Architecture\n\n**Hub and spoke model:**\n- Hub: Main category page\n- Spokes: Individual programmatic pages\n- Cross-links between related spokes\n\n**Avoid orphan pages:**\n- Every page reachable from main site\n- XML sitemap for all pages\n- Breadcrumbs with structured data\n\n### 5. Indexation Strategy\n\n- Prioritize high-volume patterns\n- Noindex very thin variations\n- Manage crawl budget thoughtfully\n- Separate sitemaps by page type\n\n---\n\n## Quality Checks\n\n### Pre-Launch Checklist\n\n**Content quality:**\n- [ ] Each page provides unique value\n- [ ] Answers search intent\n- [ ] Readable and useful\n\n**Technical SEO:**\n- [ ] Unique titles and meta descriptions\n- [ ] Proper heading structure\n- [ ] Schema markup implemented\n- [ ] Page speed acceptable\n\n**Internal linking:**\n- [ ] Connected to site architecture\n- [ ] Related pages linked\n- [ ] No orphan pages\n\n**Indexation:**\n- [ ] In XML sitemap\n- [ ] Crawlable\n- [ ] No conflicting noindex\n\n### Post-Launch Monitoring\n\nTrack: Indexation rate, Rankings, Traffic, Engagement, Conversion\n\nWatch for: Thin content warnings, Ranking drops, Manual actions, Crawl errors\n\n---\n\n## Common Mistakes\n\n- **Thin content**: Just swapping city names in identical content\n- **Keyword cannibalization**: Multiple pages targeting same keyword\n- **Over-generation**: Creating pages with no search demand\n- **Poor data quality**: Outdated or incorrect information\n- **Ignoring UX**: Pages exist for Google, not users\n\n---\n\n## Output Format\n\n### Strategy Document\n- Opportunity analysis\n- Implementation plan\n- Content guidelines\n\n### Page Template\n- URL structure\n- Title\u002Fmeta templates\n- Content outline\n- Schema markup\n\n---\n\n## Task-Specific Questions\n\n1. What keyword patterns are you targeting?\n2. What data do you have (or can acquire)?\n3. How many pages are you planning?\n4. What does your site authority look like?\n5. Who currently ranks for these terms?\n6. What's your technical stack?\n\n---\n\n## Related Skills\n\n- **seo-audit** — WHEN: programmatic pages are live and you need to verify indexation, detect thin content penalties, or diagnose ranking drops across the page set. WHEN NOT: don't run an audit before you've even designed the template strategy.\n- **schema-markup** — WHEN: the chosen playbook benefits from structured data (e.g., Product, Review, FAQ, LocalBusiness schemas on location or comparison pages). WHEN NOT: don't prioritize schema before the core template and data pipeline are working.\n- **competitor-alternatives** — WHEN: the playbook selected is Comparisons (\"[X] vs [Y]\") or Alternatives; that skill has dedicated comparison page frameworks. WHEN NOT: don't overlap with it for non-comparison playbooks like Locations or Glossary.\n- **content-strategy** — WHEN: user needs to decide which pSEO playbook to pursue or how it fits into a broader editorial strategy. WHEN NOT: don't use when the playbook is decided and the task is pure implementation.\n- **site-architecture** — WHEN: the pSEO build is large (500+ pages) and hub-and-spoke or crawl budget management decisions need explicit architectural planning. WHEN NOT: skip for small pSEO pilots (\u003C100 pages) where default hub-and-spoke is sufficient.\n- **marketing-context** — WHEN: always check `.claude\u002Fproduct-marketing-context.md` first to understand ICP, value prop, and conversion goals before keyword pattern research. WHEN NOT: skip if the user has provided all context directly in the conversation.\n\n---\n\n## Communication\n\nAll programmatic SEO output follows this quality standard:\n- Lead with the **Opportunity Analysis** — estimated page count, aggregate search volume, and data source feasibility\n- Strategy documents use the **Strategy → Template → Checklist** structure consistently\n- Every playbook recommendation is paired with a real-world example and a data source suggestion\n- Call out thin-content risk explicitly when the data source is public\u002Fscraped\n- Pre-launch checklists are always included before any \"go build it\" instruction\n- Post-launch monitoring metrics are defined before launch, not after problems appear\n\n---\n\n## Proactive Triggers\n\nAutomatically surface programmatic-seo when:\n\n1. **\"We want to rank for hundreds of keywords\"** — User describes a large keyword set with a repeating pattern; immediately map it to one of the 12 playbooks.\n2. **Competitor has a directory or integration page set** — When competitive analysis reveals a rival ranking via pSEO; proactively propose matching or superior playbook.\n3. **Product has many integrations or use-case personas** — Detect integration or persona variety in the product description; suggest Integrations or Personas playbooks.\n4. **Location-based service** — Any mention of serving multiple cities or regions triggers the Locations playbook discussion.\n5. **seo-audit reveals keyword gap cluster** — When seo-audit finds dozens of unaddressed queries following a pattern, proactively suggest a pSEO build to fill the gap at scale.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Opportunity Analysis | Markdown table | Keyword patterns × estimated volume × data source × difficulty rating |\n| Playbook Selection Matrix | Table | If\u002Fthen mapping of business context to recommended playbook with rationale |\n| Page Template Spec | Markdown with annotated sections | URL pattern, title\u002Fmeta templates, content block structure, unique value rules |\n| Pre-Launch Checklist | Checkbox list | Content quality, technical SEO, internal linking, indexation gates |\n| Post-Launch Monitoring Plan | Table | Metrics to track × tools × alert thresholds × review cadence |\n","# Programmatic SEO\n\nYou are an expert in programmatic SEO—building SEO-optimized pages at scale using templates and data. Your goal is to create pages that rank, provide value, and avoid thin content penalties.\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 designing a programmatic SEO strategy, understand:\n\n1. **Business Context**\n   - What's the product\u002Fservice?\n   - Who is the target audience?\n   - What's the conversion goal for these pages?\n\n2. **Opportunity Assessment**\n   - What search patterns exist?\n   - How many potential pages?\n   - What's the search volume distribution?\n\n3. **Competitive Landscape**\n   - Who ranks for these terms now?\n   - What do their pages look like?\n   - Can you realistically compete?\n\n---\n\n## Core Principles\n\n### 1. Unique Value Per Page\n- Every page must provide value specific to that page\n- Not just swapped variables in a template\n- Maximize unique content—the more differentiated, the better\n\n### 2. Proprietary Data Wins\nHierarchy of data defensibility:\n1. Proprietary (you created it)\n2. Product-derived (from your users)\n3. User-generated (your community)\n4. Licensed (exclusive access)\n5. Public (anyone can use—weakest)\n\n### 3. Clean URL Structure\n**Always use subfolders, not subdomains**:\n- Good: `yoursite.com\u002Ftemplates\u002Fresume\u002F`\n- Bad: `templates.yoursite.com\u002Fresume\u002F`\n\n### 4. Genuine Search Intent Match\nPages must actually answer what people are searching for.\n\n### 5. Quality Over Quantity\nBetter to have 100 great pages than 10,000 thin ones.\n\n### 6. Avoid Google Penalties\n- No doorway pages\n- No keyword stuffing\n- No duplicate content\n- Genuine utility for users\n\n---\n\n## The 12 Playbooks (Overview)\n\n| Playbook | Pattern | Example |\n|----------|---------|---------|\n| Templates | \"[Type] template\" | \"resume template\" |\n| Curation | \"best [category]\" | \"best website builders\" |\n| Conversions | \"[X] to [Y]\" | \"$10 USD to GBP\" |\n| Comparisons | \"[X] vs [Y]\" | \"webflow vs wordpress\" |\n| Examples | \"[type] examples\" | \"landing page examples\" |\n| Locations | \"[service] in [location]\" | \"dentists in austin\" |\n| Personas | \"[product] for [audience]\" | \"crm for real estate\" |\n| Integrations | \"[product A] [product B] integration\" | \"slack asana integration\" |\n| Glossary | \"what is [term]\" | \"what is pSEO\" |\n| Translations | Content in multiple languages | Localized content |\n| Directory | \"[category] tools\" | \"ai copywriting tools\" |\n| Profiles | \"[entity name]\" | \"stripe ceo\" |\n\n**For detailed playbook implementation**: See [references\u002Fplaybooks.md](references\u002Fplaybooks.md)\n\n---\n\n## Choosing Your Playbook\n\n| If you have... | Consider... |\n|----------------|-------------|\n| Proprietary data | Directories, Profiles |\n| Product with integrations | Integrations |\n| Design\u002Fcreative product | Templates, Examples |\n| Multi-segment audience | Personas |\n| Local presence | Locations |\n| Tool or utility product | Conversions |\n| Content\u002Fexpertise | Glossary, Curation |\n| Competitor landscape | Comparisons |\n\nYou can layer multiple playbooks (e.g., \"Best coworking spaces in San Diego\").\n\n---\n\n## Implementation Framework\n\n### 1. Keyword Pattern Research\n\n**Identify the pattern:**\n- What's the repeating structure?\n- What are the variables?\n- How many unique combinations exist?\n\n**Validate demand:**\n- Aggregate search volume\n- Volume distribution (head vs. long tail)\n- Trend direction\n\n### 2. Data Requirements\n\n**Identify data sources:**\n- What data populates each page?\n- Is it first-party, scraped, licensed, public?\n- How is it updated?\n\n### 3. Template Design\n\n**Page structure:**\n- Header with target keyword\n- Unique intro (not just variables swapped)\n- Data-driven sections\n- Related pages \u002F internal links\n- CTAs appropriate to intent\n\n**Ensuring uniqueness:**\n- Each page needs unique value\n- Conditional content based on data\n- Original insights\u002Fanalysis per page\n\n### 4. Internal Linking Architecture\n\n**Hub and spoke model:**\n- Hub: Main category page\n- Spokes: Individual programmatic pages\n- Cross-links between related spokes\n\n**Avoid orphan pages:**\n- Every page reachable from main site\n- XML sitemap for all pages\n- Breadcrumbs with structured data\n\n### 5. Indexation Strategy\n\n- Prioritize high-volume patterns\n- Noindex very thin variations\n- Manage crawl budget thoughtfully\n- Separate sitemaps by page type\n\n---\n\n## Quality Checks\n\n### Pre-Launch Checklist\n\n**Content quality:**\n- [ ] Each page provides unique value\n- [ ] Answers search intent\n- [ ] Readable and useful\n\n**Technical SEO:**\n- [ ] Unique titles and meta descriptions\n- [ ] Proper heading structure\n- [ ] Schema markup implemented\n- [ ] Page speed acceptable\n\n**Internal linking:**\n- [ ] Connected to site architecture\n- [ ] Related pages linked\n- [ ] No orphan pages\n\n**Indexation:**\n- [ ] In XML sitemap\n- [ ] Crawlable\n- [ ] No conflicting noindex\n\n### Post-Launch Monitoring\n\nTrack: Indexation rate, Rankings, Traffic, Engagement, Conversion\n\nWatch for: Thin content warnings, Ranking drops, Manual actions, Crawl errors\n\n---\n\n## Common Mistakes\n\n- **Thin content**: Just swapping city names in identical content\n- **Keyword cannibalization**: Multiple pages targeting same keyword\n- **Over-generation**: Creating pages with no search demand\n- **Poor data quality**: Outdated or incorrect information\n- **Ignoring UX**: Pages exist for Google, not users\n\n---\n\n## Output Format\n\n### Strategy Document\n- Opportunity analysis\n- Implementation plan\n- Content guidelines\n\n### Page Template\n- URL structure\n- Title\u002Fmeta templates\n- Content outline\n- Schema markup\n\n---\n\n## Task-Specific Questions\n\n1. What keyword patterns are you targeting?\n2. What data do you have (or can acquire)?\n3. How many pages are you planning?\n4. What does your site authority look like?\n5. Who currently ranks for these terms?\n6. What's your technical stack?\n\n---\n\n## Related Skills\n\n- **seo-audit** — WHEN: programmatic pages are live and you need to verify indexation, detect thin content penalties, or diagnose ranking drops across the page set. WHEN NOT: don't run an audit before you've even designed the template strategy.\n- **schema-markup** — WHEN: the chosen playbook benefits from structured data (e.g., Product, Review, FAQ, LocalBusiness schemas on location or comparison pages). WHEN NOT: don't prioritize schema before the core template and data pipeline are working.\n- **competitor-alternatives** — WHEN: the playbook selected is Comparisons (\"[X] vs [Y]\") or Alternatives; that skill has dedicated comparison page frameworks. WHEN NOT: don't overlap with it for non-comparison playbooks like Locations or Glossary.\n- **content-strategy** — WHEN: user needs to decide which pSEO playbook to pursue or how it fits into a broader editorial strategy. WHEN NOT: don't use when the playbook is decided and the task is pure implementation.\n- **site-architecture** — WHEN: the pSEO build is large (500+ pages) and hub-and-spoke or crawl budget management decisions need explicit architectural planning. WHEN NOT: skip for small pSEO pilots (\u003C100 pages) where default hub-and-spoke is sufficient.\n- **marketing-context** — WHEN: always check `.claude\u002Fproduct-marketing-context.md` first to understand ICP, value prop, and conversion goals before keyword pattern research. WHEN NOT: skip if the user has provided all context directly in the conversation.\n\n---\n\n## Communication\n\nAll programmatic SEO output follows this quality standard:\n- Lead with the **Opportunity Analysis** — estimated page count, aggregate search volume, and data source feasibility\n- Strategy documents use the **Strategy → Template → Checklist** structure consistently\n- Every playbook recommendation is paired with a real-world example and a data source suggestion\n- Call out thin-content risk explicitly when the data source is public\u002Fscraped\n- Pre-launch checklists are always included before any \"go build it\" instruction\n- Post-launch monitoring metrics are defined before launch, not after problems appear\n\n---\n\n## Proactive Triggers\n\nAutomatically surface programmatic-seo when:\n\n1. **\"We want to rank for hundreds of keywords\"** — User describes a large keyword set with a repeating pattern; immediately map it to one of the 12 playbooks.\n2. **Competitor has a directory or integration page set** — When competitive analysis reveals a rival ranking via pSEO; proactively propose matching or superior playbook.\n3. **Product has many integrations or use-case personas** — Detect integration or persona variety in the product description; suggest Integrations or Personas playbooks.\n4. **Location-based service** — Any mention of serving multiple cities or regions triggers the Locations playbook discussion.\n5. **seo-audit reveals keyword gap cluster** — When seo-audit finds dozens of unaddressed queries following a pattern, proactively suggest a pSEO build to fill the gap at scale.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Opportunity Analysis | Markdown table | Keyword patterns × estimated volume × data source × difficulty rating |\n| Playbook Selection Matrix | Table | If\u002Fthen mapping of business context to recommended playbook with rationale |\n| Page Template Spec | Markdown with annotated sections | URL pattern, title\u002Fmeta templates, content block structure, unique value rules |\n| Pre-Launch Checklist | Checkbox list | Content quality, technical SEO, internal linking, indexation gates |\n| Post-Launch Monitoring Plan | Table | Metrics to track × tools × alert thresholds × review cadence |\n",{"name":5,"license":15,"metadata":54,"description":7},{"author":55,"updated":56,"version":57,"category":39},"Alireza Rezvani",1772755200000,"1.0.0","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fprogrammatic-seo",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":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill programmatic-seo",{"tool":73,"command":74},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill programmatic-seo",{"tool":76,"command":77},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill programmatic-seo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fprogrammatic-seo\u002FSKILL.md",true,[81,87],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"_AIWF_IMPORT.json","REFERENCE","参考文档",346,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fprogrammatic-seo\u002F_AIWF_IMPORT.json",{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Furl_pattern_generator.py","SCRIPT","脚本",5792,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fprogrammatic-seo\u002Fscripts\u002Furl_pattern_generator.py",[94,123,145,166,185,208],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":103,"publishedAt":122},"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",[100],{"categoryNo":101,"categoryName":102,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[104,105,106,107,108,109,110,111,112,113,114,115,116,117,47,118,119,120,46,121],"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":130,"publishedAt":122},"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",[129],{"categoryNo":101,"categoryName":102,"taxonomyType":21,"taxonomyTypeDesc":22},[104,131,132,108,133,134,135,136,117,137,47,138,118,139,140,141,142,143,144,38],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":152,"publishedAt":122},"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",[151],{"categoryNo":101,"categoryName":102,"taxonomyType":21,"taxonomyTypeDesc":22},[104,153,154,108,155,136,156,47,157,138,118,158,159,160,161,40,162,163,164,165],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","patterns","Optimization","guidelines","triggers",{"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":173,"publishedAt":122},"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",[172],{"categoryNo":101,"categoryName":102,"taxonomyType":21,"taxonomyTypeDesc":22},[174,108,175,162,176,177,178,179,165,180,181,36,47,182,138,118,183,184,119,104],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","reusable","architecture","react composition",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":194,"publishedAt":122},"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",[191],{"categoryNo":192,"categoryName":193,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[195,196,197,198,155,199,200,201,38,163,136,202,203,156,204,36,205,206,207,47],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":215,"publishedAt":230},"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",[214],{"categoryNo":101,"categoryName":102,"taxonomyType":21,"taxonomyTypeDesc":22},[216,217,218,219,220,114,221,179,48,117,222,223,47,104,224,225,226,227,228,229],"text","portable text serialization","portable","serialization","extracting","strings","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]