[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71AK8MPJ3SYB405PD6Z0MDN":3,"skill-same:01M71AK8MPJ3SYB405PD6Z0MDN":78},{"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":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M71AK8MPJ3SYB405PD6Z0MDN","docs-page-generator",null,"When the user wants to create, optimize, or structure a documentation site. Also use when the user mentions \"docs\", \"documentation site\", \"docs subdomain\" or \"docs.yourdomain.com\". For API marketing landing, use api-page-generator.","ariadoss\u002Fsuperskills","ariadoss","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F414341?v=4","01M71AC7383PT6JCRZSQJ4AVTM","Danilo Stern-Sapad","01M71AC73Y7NTBTJ9KQYNENRRE",12,"MIT","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fpages\u002Fcontent\u002Fdocs\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],"docs page","generator","docs page generator","docs","page","user","marketing","site","subdomain","optimize","structure","create","documentation","api","when","use","landing","for","2026-11-10 10:12:30",false,"---\nname: docs-page-generator\ndescription: When the user wants to create, optimize, or structure a documentation site. Also use when the user mentions \"docs\", \"documentation site\", \"docs subdomain\" or \"docs.yourdomain.com\". For API marketing landing, use api-page-generator.\nmetadata:\n  version: 1.0.1\n---\n\n# Pages: Documentation Site\n\nGuides documentation site structure, navigation, and content organization. Typically hosted on `docs.*` or `help.*` subdomain. Includes Getting Started, guides, tutorials, **API Reference** (endpoint docs), and troubleshooting. Distinct from API introduction page (api-page-generator).\n\n**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.\n\n## Initial Assessment\n\n**Check for project context first:** If `.claude\u002Fproject-context.md` or `.cursor\u002Fproject-context.md` exists, read it for product, audience, and use cases.\n\nIdentify:\n1. **Product type**: Software, API, hardware, service\n2. **Audience**: End users, developers, admins\n3. **Content sources**: Markdown, MDX, Git, CMS\n4. **Subdomain**: docs.*, help.*, or path (\u002Fdocs)\n\n## Documentation Structure\n\n| Section | Purpose | Typical Content |\n|---------|---------|-----------------|\n| **Getting Started** | Onboarding, first steps | Quick start, installation, first task |\n| **Guides \u002F Tutorials** | Step-by-step learning | How-to articles, workflows |\n| **Concepts** | Background, architecture | Key concepts, glossary links |\n| **API Reference** | Endpoint docs | Auth, request\u002Fresponse, examples; part of docs, not separate page |\n| **Troubleshooting** | Problem solving | FAQ, common errors, support links |\n\n## Best Practices\n\n### Information Architecture\n\n- **Progressive disclosure**: Start simple, link to depth\n- **Sidebar navigation**: Hierarchical, collapsible sections\n- **Search**: Full-text search for long doc sets\n- **Breadcrumbs**: For deep hierarchies\n\n### API Reference (within Docs)\n\nAPI Reference is a section of docs, not a standalone page. Include: endpoints by resource, auth, request\u002Fresponse schemas, error codes, rate limits, code examples (cURL, SDKs). Use OpenAPI\u002FSwagger for consistency.\n\n### Content\n\n- **Task-oriented**: \"How to X\" not \"X feature\"\n- **Code examples**: Copy-paste ready, multiple languages if relevant\n- **Screenshots\u002Fvideos**: For UI-heavy products\n- **Versioning**: Document product\u002FAPI version when applicable\n\n### SEO and Discovery\n\n- **Index docs**: Unless internal-only; use robots if needed\n- **Internal links**: Cross-link related articles, link to main site\n- **Schema**: TechArticle, HowTo for guides\n\n## Output Format\n\n- **Structure** (sections, hierarchy)\n- **Navigation** design (sidebar, top-level)\n- **Getting Started** outline\n- **Content** checklist per section\n- **Subdomain\u002Fpath** recommendation\n\n## Related Skills\n\n- **api-page-generator**: API intro page links to docs\n- **sidebar-generator**: Docs sidebar design\n- **faq-page-generator**: FAQ can live in docs or main site\n- **howto-section-generator**: HowTo step blocks in guides\u002Ftutorials; TechArticle + HowTo alignment\n- **content-strategy**: Doc content planning\n","# Pages: Documentation Site\n\nGuides documentation site structure, navigation, and content organization. Typically hosted on `docs.*` or `help.*` subdomain. Includes Getting Started, guides, tutorials, **API Reference** (endpoint docs), and troubleshooting. Distinct from API introduction page (api-page-generator).\n\n**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.\n\n## Initial Assessment\n\n**Check for project context first:** If `.claude\u002Fproject-context.md` or `.cursor\u002Fproject-context.md` exists, read it for product, audience, and use cases.\n\nIdentify:\n1. **Product type**: Software, API, hardware, service\n2. **Audience**: End users, developers, admins\n3. **Content sources**: Markdown, MDX, Git, CMS\n4. **Subdomain**: docs.*, help.*, or path (\u002Fdocs)\n\n## Documentation Structure\n\n| Section | Purpose | Typical Content |\n|---------|---------|-----------------|\n| **Getting Started** | Onboarding, first steps | Quick start, installation, first task |\n| **Guides \u002F Tutorials** | Step-by-step learning | How-to articles, workflows |\n| **Concepts** | Background, architecture | Key concepts, glossary links |\n| **API Reference** | Endpoint docs | Auth, request\u002Fresponse, examples; part of docs, not separate page |\n| **Troubleshooting** | Problem solving | FAQ, common errors, support links |\n\n## Best Practices\n\n### Information Architecture\n\n- **Progressive disclosure**: Start simple, link to depth\n- **Sidebar navigation**: Hierarchical, collapsible sections\n- **Search**: Full-text search for long doc sets\n- **Breadcrumbs**: For deep hierarchies\n\n### API Reference (within Docs)\n\nAPI Reference is a section of docs, not a standalone page. Include: endpoints by resource, auth, request\u002Fresponse schemas, error codes, rate limits, code examples (cURL, SDKs). Use OpenAPI\u002FSwagger for consistency.\n\n### Content\n\n- **Task-oriented**: \"How to X\" not \"X feature\"\n- **Code examples**: Copy-paste ready, multiple languages if relevant\n- **Screenshots\u002Fvideos**: For UI-heavy products\n- **Versioning**: Document product\u002FAPI version when applicable\n\n### SEO and Discovery\n\n- **Index docs**: Unless internal-only; use robots if needed\n- **Internal links**: Cross-link related articles, link to main site\n- **Schema**: TechArticle, HowTo for guides\n\n## Output Format\n\n- **Structure** (sections, hierarchy)\n- **Navigation** design (sidebar, top-level)\n- **Getting Started** outline\n- **Content** checklist per section\n- **Subdomain\u002Fpath** recommendation\n\n## Related Skills\n\n- **api-page-generator**: API intro page links to docs\n- **sidebar-generator**: Docs sidebar design\n- **faq-page-generator**: FAQ can live in docs or main site\n- **howto-section-generator**: HowTo step blocks in guides\u002Ftutorials; TechArticle + HowTo alignment\n- **content-strategy**: Doc content planning\n",{"name":5,"metadata":52,"description":7},{"version":53},"1.0.1","main","c7ec8d78e5dc37484c2cfe90ab04de163d97dd41","marketing-skills\u002Fpages\u002Fcontent\u002Fdocs",0,"https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills","https:\u002F\u002Fhyperion360.com\u002Fblog\u002Fparallel-ai-agents-engineering-workflow\u002F","https:\u002F\u002Fgithub.com\u002Fariadoss","https:\u002F\u002Fdanilosapad.com\u002F","CEO & Founder of @Hyperion360","2026-11-13 04:11:07",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add ariadoss\u002Fsuperskills --skill docs-page-generator",{"tool":70,"command":71},"bunx","bunx skills add ariadoss\u002Fsuperskills --skill docs-page-generator",{"tool":73,"command":74},"pnpm","pnpm dlx skills add ariadoss\u002Fsuperskills --skill docs-page-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fpages\u002Fcontent\u002Fdocs\u002FSKILL.md",true,[],[79,103,127,146,173,189],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":88,"publishedAt":47},"01M71AZE3MPF891RM354EMRYA1","youtube","Download YouTube video transcripts when user provides a YouTube URL or asks to download\u002Fget\u002Ffetch a transcript from YouTube. Also use when user wants to transcribe or get captions\u002Fsubtitles from a YouTube video.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[85],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[81,34,89,90,91,92,93,94,95,43,96,97,98,99,100,44,101,102],"download","transcribe","write","transcript","video transcripts","Bash","URL","Captions","get","fetch","Video","read","subtitles","transcripts",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":47},"01M71AZAYR85PW6BJGSQXS4BN2","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY\u002FSOLID\u002FYAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs \u002Fplan-eng-review as an independent double-check before execution.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[110,111,91,112,113,114,115,116,117,43,118,119,120,121,122,46,123,124,125,126],"write plan","plan","dry","verification","review","tasks","code","you","auto","eng","coverage","complete","section","test plan","target","as","yagni",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":47},"01M71AZ8NDDP5ZMGEE6FSC4FKR","worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fworktrees\u002FSKILL.md",[],[129,134,135,136,44,137,138,139,140,141,142,113,143,43,144,145],"implementation","workspace","with","plans","feature","isolation","git","directory","work","git worktrees","selection","Safety",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":155,"publishedAt":47},"01M71AZ4ZQHTNWFRZVYHKQFP08","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",[152],{"categoryNo":153,"categoryName":154,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[156,157,158,159,160,161,38,41,162,43,163,164,165,166,167,168,169,170,171,172],"web","perf","web perf","resources","MCP","layout","caching","qa","knowledge","devtools","issues","render","re","performance","chrome devtools","vitals","never",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":47},"01M71AZ2KZNWYEGKKRMJH8PYG2","verify","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[175,121,180,181,142,113,182,183,43,184,44,185,186,187,188],"commands","about","claims","output","assertions","claim","prs","evidence","running",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":195,"publishedAt":47},"01M71AZ0ACCK7N1QMWQK1FV2HJ","validate-idea","Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-idea\u002FSKILL.md",[],[196,197,198,199,200,201,202,43,203,44,204],"validate","idea","validate idea","framework","it","minimalist","test","business","before building"]