[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71AVV1ZSS0Y5GG4ZFV24Y9K":3,"skill-same:01M71AVV1ZSS0Y5GG4ZFV24Y9K":70},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M71AVV1ZSS0Y5GG4ZFV24Y9K","website-structure",null,"When the user wants to plan website structure, decide which pages to build, or prioritize pages for a new or existing site. Also use when the user mentions \"website structure\", \"site structure\", \"which pages do I need\" or \"page planning\". For a specific page template (e.g. homepage), use homepage-generator or landing-page-generator as appropriate. Not for organic SEO roadmap alone; use seo-strategy.","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\u002Fstrategies\u002Fstructure\u002Fwebsite-structure\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"structure","website structure","website","pages","new","when","Existing","for","which","generator","as","seo","planning","do","roadmap","use","landing","strategy","decide","page","2026-11-10 10:12:30",false,"---\nname: website-structure\ndescription: When the user wants to plan website structure, decide which pages to build, or prioritize pages for a new or existing site. Also use when the user mentions \"website structure\", \"site structure\", \"which pages do I need\" or \"page planning\". For a specific page template (e.g. homepage), use homepage-generator or landing-page-generator as appropriate. Not for organic SEO roadmap alone; use seo-strategy.\nmetadata:\n  version: 1.5.0\n---\n\n# Strategy: Website Structure\n\nGuides website structure planning: which pages to build, page priority, and how structure supports UX, SEO, and growth. Structure is the organization and connection of pages; it affects user navigation, Google's understanding of content importance, crawlability, and sitelinks in SERPs. See **serp-features** for sitelinks and SERP optimization.\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 type, audience, and growth goals.\n\nIdentify:\n1. **Website type**: Product\u002FSaaS, B2B, E-commerce, Portfolio, Forum, Directory\n2. **Stage**: New site (plan from scratch) vs. existing (extend or audit)\n3. **Growth strategy**: Affiliate, education, multi-language, community, B2B, developer\n4. **Constraints**: Team size, budget, tech stack\n\n## Page Priority Framework\n\nPlan pages by priority for development scheduling. See [skills-reference §2 Page Taxonomy](..\u002F..\u002F..\u002Fdocs\u002Fskills-reference.md#2-page-taxonomy) for full page types and website-type mapping.\n\n| Priority | Pages | Notes |\n|----------|-------|-------|\n| **Must Have** | Home, Product\u002FFeatures, Pricing, Blog, About, Privacy, Terms, Contact | Essential for trust and conversion; Pricing: public page in nav for self-serve; enterprise-only may use \"Contact sales\" instead; see **pricing-page-generator** (Visibility & Placement) |\n| **Great to Have** | Testimonials, FAQ, Sitemap (HTML), 404, Refund\u002FReturns | Support UX and SEO |\n| **Optional** | Search Results, News, Careers, Disclosure | Situational |\n| **Traffic-driven** | Category\u002FCollection pages | For content-heavy or e-commerce; needs Category + Tags |\n\n## Generic Template Structure\n\nApplicable to SaaS, tools, and content sites. Adapt by removing unused nodes (e.g. no API → drop API) and adding specific modules (e.g. industry, region).\n\n| Section | Typical Paths | Page Skills |\n|---------|---------------|-------------|\n| **Root** | \u002F, \u002Ffeatures, \u002Fpricing, \u002Fdemo, \u002Fcontact | homepage-generator, features-page-generator, pricing-page-generator |\n| **Tools** | \u002Ftools, \u002Ffree-tools; hub + per-tool pages | tools-page-generator; free tools for lead gen; often SPA; programmatic; see **programmatic-seo** |\n| **Resources** | \u002Fblog, \u002Fchangelog, \u002Fglossary, \u002Ffaq, \u002Ftutorials | blog-page-generator, changelog-page-generator, glossary-page-generator, faq-page-generator |\n| **Partnership** | \u002Faffiliate, \u002Fstartups, \u002Fambassadors | affiliate-page-generator, landing-page-generator |\n| **Legal** | \u002Fterms, \u002Fprivacy, \u002Fcareers | terms-page-generator, privacy-page-generator, careers-page-generator |\n| **Competitor** | \u002Falternatives, \u002Fcompare, \u002Fmigrate | alternatives-page-generator, migration-page-generator |\n| **Standalone** | \u002Fdashboard, \u002Flogin, \u002Fsignup, \u002Fdocs, \u002Fapi, \u002Fstatus, \u002Fsupport | signup-login-page-generator, docs-page-generator, api-page-generator, status-page-generator |\n\n## Growth Strategy → Structure Mapping\n\nStructure reflects growth strategy. Subdirectories signal channels:\n\n| Goal | Path Example | Page\u002FChannel |\n|------|--------------|--------------|\n| Affiliate conversion | \u002Faffiliate | affiliate-page-generator |\n| Education\u002Fstudent plan | \u002Feducation, \u002Fstartups, \u002Fstudent-discount | education-program, startups-page-generator |\n| Multi-language | \u002Fzh-CN, \u002Fja | localization-strategy |\n| Community | \u002Fambassadors, \u002Fshowcase | creator-program, landing-page-generator |\n| B2B \u002F Enterprise | Solutions (industry-first), Use cases (scenario-first; can be sub-pages), Customer stories | solutions-page-generator, use-cases-page-generator, customer-stories-page-generator |\n| Developer product | \u002Fapi, \u002Fdocs, \u002Fstatus | api-page-generator, docs-page-generator, status-page-generator |\n| User feedback | Feedback, Roadmap | feedback-page-generator; External (Canny, FeatureBase) |\n| Plugins\u002FIntegrations | \u002Fintegrations, \u002Fplugins | integrations-page-generator, category-page-generator |\n| Giveaway\u002FContest | \u002Fgiveaway | contest-page-generator |\n\n## Domain Structure (Multiple Products)\n\nWhen planning for multiple products or brands, see **domain-architecture** for subfolder vs subdomain vs independent domain. This skill covers page structure within a single domain. For initial domain choice (Brand vs PMD vs EMD, TLD), see **domain-selection**.\n\n## Planning Workflow\n\n1. **Choose template**: Start from generic structure; map to [skills-reference §2](..\u002F..\u002F..\u002Fdocs\u002Fskills-reference.md#2-page-taxonomy) website types\n2. **Trim modules**: Remove irrelevant nodes (e.g. no API → drop \u002Fapi, \u002Fdocs)\n3. **Add specifics**: Industry pages, region, product variants\n4. **Assign URLs**: Per node; follow **url-structure** (lowercase, hyphens, short, keyword-rich)\n5. **Export list**: \"Page type + URL + Priority\" for dev scheduling\n6. **Tech stack**: Match page types to services (DNS, auth, CMS, status page, etc.)\n7. **Iterate**: Expand with new features, markets; keep structure clear\n\n## Structure Principles\n\n| Principle | Guideline |\n|-----------|-----------|\n| **Flat structure** | Max 4 clicks from homepage to any page; improves crawlability and weight distribution |\n| **Early planning** | Plan structure before growth; can start right after domain purchase |\n| **Sitelinks** | Good structure + TOC + authoritative internal links → natural sitelinks in SERP (cannot be forced via schema); see **serp-features** |\n| **Orphan prevention** | Every page needs internal links; see **site-crawlability** and **internal-links** |\n| **Features vs Use cases** | \u002Ffeatures = capability-first; \u002Fuse-cases = scenario-first; differentiate content angle, link between, avoid overlap; see **features-page-generator**, **use-cases-page-generator** |\n| **Clear navigation** | Clear hierarchy and nav improve task completion; users find what they need faster; see **navigation-menu-generator** |\n| **Pricing placement** | Marketing site: \u002Fpricing in main nav for prospects; in-app: Settings → Billing in sidebar for logged-in users (subscription management). Enterprise-only: \"Contact sales\" may replace public pricing page; see **pricing-page-generator** |\n\n## Homepage Module Reference\n\nSee **homepage-generator** for common modules (Headline, Subheadline, CTA, Benefits, Social Proof, etc.), navigation options, and **hero-generator** for hero design.\n\n## Output Format\n\n- **Page list** with priority (Must Have \u002F Great to Have \u002F Optional)\n- **URL structure** (paths per section)\n- **Website-type fit** (which pages apply per [skills-reference §2](..\u002F..\u002F..\u002Fdocs\u002Fskills-reference.md#2-page-taxonomy))\n- **Growth mapping** (which paths support which channels)\n- **Next steps**: url-structure for URL rules; xml-sitemap for submission; site-crawlability for audit\n\n## References\n\n- [Website structure SEO guide](https:\u002F\u002Falignify.co\u002Fzh\u002Fseo\u002Fwebsite-structure) — Alignify: structure importance, page priority, generic template, planning workflow, growth mapping, homepage modules\n- **[skills-reference §2](..\u002F..\u002F..\u002Fdocs\u002Fskills-reference.md#2-page-taxonomy)** — Full page types, website-type matrix, core vs extended; use for page selection\n\n## Related Skills\n\n- **seo-strategy**: SEO workflow order; structure planning fits before Technical phase\n- **domain-selection**: Initial domain choice; do before structure when choosing domain\n- **domain-architecture**: Subfolder vs subdomain vs independent; do before structure if domain decision pending\n- **url-structure**: URL optimization, hierarchy, slugs; apply after structure is defined\n- **site-crawlability**: Crawlability, orphan pages, redirects; audit existing structure\n- **internal-links**: Link strategy, hub-spoke; implement after pages exist\n- **xml-sitemap**: Sitemap creation; include planned URLs\n- **breadcrumb-generator**: Breadcrumb for hierarchy; large sites, e-commerce\n- **navigation-menu-generator**: Nav design; primary, footer, mobile\n- **content-strategy**: Content clusters, pillar pages; complements structure planning\n","# Strategy: Website Structure\n\nGuides website structure planning: which pages to build, page priority, and how structure supports UX, SEO, and growth. Structure is the organization and connection of pages; it affects user navigation, Google's understanding of content importance, crawlability, and sitelinks in SERPs. See **serp-features** for sitelinks and SERP optimization.\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 type, audience, and growth goals.\n\nIdentify:\n1. **Website type**: Product\u002FSaaS, B2B, E-commerce, Portfolio, Forum, Directory\n2. **Stage**: New site (plan from scratch) vs. existing (extend or audit)\n3. **Growth strategy**: Affiliate, education, multi-language, community, B2B, developer\n4. **Constraints**: Team size, budget, tech stack\n\n## Page Priority Framework\n\nPlan pages by priority for development scheduling. See [skills-reference §2 Page Taxonomy](..\u002F..\u002F..\u002Fdocs\u002Fskills-reference.md#2-page-taxonomy) for full page types and website-type mapping.\n\n| Priority | Pages | Notes |\n|----------|-------|-------|\n| **Must Have** | Home, Product\u002FFeatures, Pricing, Blog, About, Privacy, Terms, Contact | Essential for trust and conversion; Pricing: public page in nav for self-serve; enterprise-only may use \"Contact sales\" instead; see **pricing-page-generator** (Visibility & Placement) |\n| **Great to Have** | Testimonials, FAQ, Sitemap (HTML), 404, Refund\u002FReturns | Support UX and SEO |\n| **Optional** | Search Results, News, Careers, Disclosure | Situational |\n| **Traffic-driven** | Category\u002FCollection pages | For content-heavy or e-commerce; needs Category + Tags |\n\n## Generic Template Structure\n\nApplicable to SaaS, tools, and content sites. Adapt by removing unused nodes (e.g. no API → drop API) and adding specific modules (e.g. industry, region).\n\n| Section | Typical Paths | Page Skills |\n|---------|---------------|-------------|\n| **Root** | \u002F, \u002Ffeatures, \u002Fpricing, \u002Fdemo, \u002Fcontact | homepage-generator, features-page-generator, pricing-page-generator |\n| **Tools** | \u002Ftools, \u002Ffree-tools; hub + per-tool pages | tools-page-generator; free tools for lead gen; often SPA; programmatic; see **programmatic-seo** |\n| **Resources** | \u002Fblog, \u002Fchangelog, \u002Fglossary, \u002Ffaq, \u002Ftutorials | blog-page-generator, changelog-page-generator, glossary-page-generator, faq-page-generator |\n| **Partnership** | \u002Faffiliate, \u002Fstartups, \u002Fambassadors | affiliate-page-generator, landing-page-generator |\n| **Legal** | \u002Fterms, \u002Fprivacy, \u002Fcareers | terms-page-generator, privacy-page-generator, careers-page-generator |\n| **Competitor** | \u002Falternatives, \u002Fcompare, \u002Fmigrate | alternatives-page-generator, migration-page-generator |\n| **Standalone** | \u002Fdashboard, \u002Flogin, \u002Fsignup, \u002Fdocs, \u002Fapi, \u002Fstatus, \u002Fsupport | signup-login-page-generator, docs-page-generator, api-page-generator, status-page-generator |\n\n## Growth Strategy → Structure Mapping\n\nStructure reflects growth strategy. Subdirectories signal channels:\n\n| Goal | Path Example | Page\u002FChannel |\n|------|--------------|--------------|\n| Affiliate conversion | \u002Faffiliate | affiliate-page-generator |\n| Education\u002Fstudent plan | \u002Feducation, \u002Fstartups, \u002Fstudent-discount | education-program, startups-page-generator |\n| Multi-language | \u002Fzh-CN, \u002Fja | localization-strategy |\n| Community | \u002Fambassadors, \u002Fshowcase | creator-program, landing-page-generator |\n| B2B \u002F Enterprise | Solutions (industry-first), Use cases (scenario-first; can be sub-pages), Customer stories | solutions-page-generator, use-cases-page-generator, customer-stories-page-generator |\n| Developer product | \u002Fapi, \u002Fdocs, \u002Fstatus | api-page-generator, docs-page-generator, status-page-generator |\n| User feedback | Feedback, Roadmap | feedback-page-generator; External (Canny, FeatureBase) |\n| Plugins\u002FIntegrations | \u002Fintegrations, \u002Fplugins | integrations-page-generator, category-page-generator |\n| Giveaway\u002FContest | \u002Fgiveaway | contest-page-generator |\n\n## Domain Structure (Multiple Products)\n\nWhen planning for multiple products or brands, see **domain-architecture** for subfolder vs subdomain vs independent domain. This skill covers page structure within a single domain. For initial domain choice (Brand vs PMD vs EMD, TLD), see **domain-selection**.\n\n## Planning Workflow\n\n1. **Choose template**: Start from generic structure; map to [skills-reference §2](..\u002F..\u002F..\u002Fdocs\u002Fskills-reference.md#2-page-taxonomy) website types\n2. **Trim modules**: Remove irrelevant nodes (e.g. no API → drop \u002Fapi, \u002Fdocs)\n3. **Add specifics**: Industry pages, region, product variants\n4. **Assign URLs**: Per node; follow **url-structure** (lowercase, hyphens, short, keyword-rich)\n5. **Export list**: \"Page type + URL + Priority\" for dev scheduling\n6. **Tech stack**: Match page types to services (DNS, auth, CMS, status page, etc.)\n7. **Iterate**: Expand with new features, markets; keep structure clear\n\n## Structure Principles\n\n| Principle | Guideline |\n|-----------|-----------|\n| **Flat structure** | Max 4 clicks from homepage to any page; improves crawlability and weight distribution |\n| **Early planning** | Plan structure before growth; can start right after domain purchase |\n| **Sitelinks** | Good structure + TOC + authoritative internal links → natural sitelinks in SERP (cannot be forced via schema); see **serp-features** |\n| **Orphan prevention** | Every page needs internal links; see **site-crawlability** and **internal-links** |\n| **Features vs Use cases** | \u002Ffeatures = capability-first; \u002Fuse-cases = scenario-first; differentiate content angle, link between, avoid overlap; see **features-page-generator**, **use-cases-page-generator** |\n| **Clear navigation** | Clear hierarchy and nav improve task completion; users find what they need faster; see **navigation-menu-generator** |\n| **Pricing placement** | Marketing site: \u002Fpricing in main nav for prospects; in-app: Settings → Billing in sidebar for logged-in users (subscription management). Enterprise-only: \"Contact sales\" may replace public pricing page; see **pricing-page-generator** |\n\n## Homepage Module Reference\n\nSee **homepage-generator** for common modules (Headline, Subheadline, CTA, Benefits, Social Proof, etc.), navigation options, and **hero-generator** for hero design.\n\n## Output Format\n\n- **Page list** with priority (Must Have \u002F Great to Have \u002F Optional)\n- **URL structure** (paths per section)\n- **Website-type fit** (which pages apply per [skills-reference §2](..\u002F..\u002F..\u002Fdocs\u002Fskills-reference.md#2-page-taxonomy))\n- **Growth mapping** (which paths support which channels)\n- **Next steps**: url-structure for URL rules; xml-sitemap for submission; site-crawlability for audit\n\n## References\n\n- [Website structure SEO guide](https:\u002F\u002Falignify.co\u002Fzh\u002Fseo\u002Fwebsite-structure) — Alignify: structure importance, page priority, generic template, planning workflow, growth mapping, homepage modules\n- **[skills-reference §2](..\u002F..\u002F..\u002Fdocs\u002Fskills-reference.md#2-page-taxonomy)** — Full page types, website-type matrix, core vs extended; use for page selection\n\n## Related Skills\n\n- **seo-strategy**: SEO workflow order; structure planning fits before Technical phase\n- **domain-selection**: Initial domain choice; do before structure when choosing domain\n- **domain-architecture**: Subfolder vs subdomain vs independent; do before structure if domain decision pending\n- **url-structure**: URL optimization, hierarchy, slugs; apply after structure is defined\n- **site-crawlability**: Crawlability, orphan pages, redirects; audit existing structure\n- **internal-links**: Link strategy, hub-spoke; implement after pages exist\n- **xml-sitemap**: Sitemap creation; include planned URLs\n- **breadcrumb-generator**: Breadcrumb for hierarchy; large sites, e-commerce\n- **navigation-menu-generator**: Nav design; primary, footer, mobile\n- **content-strategy**: Content clusters, pillar pages; complements structure planning\n",{"name":5,"metadata":44,"description":7},{"version":45},"1.5.0","main","c7ec8d78e5dc37484c2cfe90ab04de163d97dd41","marketing-skills\u002Fstrategies\u002Fstructure\u002Fwebsite-structure",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 15:29:19",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add ariadoss\u002Fsuperskills --skill website-structure",{"tool":62,"command":63},"bunx","bunx skills add ariadoss\u002Fsuperskills --skill website-structure",{"tool":65,"command":66},"pnpm","pnpm dlx skills add ariadoss\u002Fsuperskills --skill website-structure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fstrategies\u002Fstructure\u002Fwebsite-structure\u002FSKILL.md",true,[],[71,98,121,140,169,185],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":82,"publishedAt":39},"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",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[73,83,84,85,86,87,88,89,90,24,91,92,93,94,95,34,96,97],"user","download","transcribe","write","transcript","video transcripts","Bash","URL","Captions","get","fetch","Video","read","subtitles","transcripts",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":39},"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",[],[105,106,86,107,108,109,110,111,112,24,113,114,115,116,117,26,118,119,29,120],"write plan","plan","dry","verification","review","tasks","code","you","auto","eng","coverage","complete","section","test plan","target","yagni",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":39},"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",[],[123,128,129,130,34,131,132,133,134,135,136,108,137,24,138,139],"implementation","workspace","with","plans","feature","isolation","git","directory","work","git worktrees","selection","Safety",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":149,"publishedAt":39},"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",[146],{"categoryNo":147,"categoryName":148,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000023","Skill与智能体开发",[150,151,152,153,154,155,156,157,158,24,159,160,161,162,163,164,165,166,167,168],"web","perf","web perf","resources","MCP","layout","optimize","documentation","caching","qa","knowledge","devtools","issues","render","re","performance","chrome devtools","vitals","never",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":39},"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",[],[171,116,176,177,136,108,178,179,24,180,34,181,182,183,184],"commands","about","claims","output","assertions","claim","prs","evidence","running",{"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":191,"publishedAt":39},"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",[],[192,193,194,195,196,197,198,24,199,34,200],"validate","idea","validate idea","framework","it","minimalist","test","business","before building"]