[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71GNBZ6X6TRF8TF033ZVTPD":3,"skill-same:01M71GNBZ6X6TRF8TF033ZVTPD":84},{"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":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":6,"updatedAt":63,"install":64,"resources":77},"01M71GNBZ6X6TRF8TF033ZVTPD","doc-writer-doc-site",null,"Authors documentation-site pages and designs information architecture — navigation, sidebar taxonomy, page hierarchy, cross-linking strategy, doc-site generator conventions (Docusaurus, MkDocs, Nextra, VitePress, etc.). Pulled by the `doc-writer` specialist. TRIGGER: \"build out the docs site\", \"write the documentation site pages\", \"design the doc site navigation\", \"add a sidebar section for feature X\", \"write the docs for Y in our Docusaurus site\", \"set up the doc-site IA\", \"create a new section in MkDocs for Z\", \"update the doc-site nav\". DO NOT TRIGGER for: API reference tables or endpoint docs (use `technical-writer-api-docs`), changelogs or release notes pages (use `technical-writer-release-notes`), a project README (use `doc-writer-readme`), onboarding or CONTRIBUTING.md (use `doc-writer-onboarding-doc`), deploying or configuring the doc-site hosting infra (use devops specialist), marketing landing pages (use `copywriter-long-form`).","lookatitude\u002Fguild","lookatitude","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F524917?v=4","01M71GJ2KGXFSJZKAZC5P1ZXXM","Miguel Pinto","01M71GJ2MH4SH9WJKP8M7XZZ0P",8,"MIT","https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild\u002Fblob\u002Fmain\u002Fskills\u002Fspecialists\u002Fdoc-writer-doc-site\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"doc","doc writer","doc writer doc site","site","writer","api","architecture","when","information","release notes","new","design","nextra","up","api-docs","project","release-notes","user request","information architecture","SET","2026-11-10 10:12:30",false,"---\nname: doc-writer-doc-site\ndescription: \"Authors documentation-site pages and designs information architecture — navigation, sidebar taxonomy, page hierarchy, cross-linking strategy, doc-site generator conventions (Docusaurus, MkDocs, Nextra, VitePress, etc.). Pulled by the `doc-writer` specialist. TRIGGER: \\\"build out the docs site\\\", \\\"write the documentation site pages\\\", \\\"design the doc site navigation\\\", \\\"add a sidebar section for feature X\\\", \\\"write the docs for Y in our Docusaurus site\\\", \\\"set up the doc-site IA\\\", \\\"create a new section in MkDocs for Z\\\", \\\"update the doc-site nav\\\". DO NOT TRIGGER for: API reference tables or endpoint docs (use `technical-writer-api-docs`), changelogs or release notes pages (use `technical-writer-release-notes`), a project README (use `doc-writer-readme`), onboarding or CONTRIBUTING.md (use `doc-writer-onboarding-doc`), deploying or configuring the doc-site hosting infra (use devops specialist), marketing landing pages (use `copywriter-long-form`).\"\nwhen_to_use: The parent `doc-writer` specialist pulls this skill when the task involves doc-site page content, information architecture, navigation design, or doc-site generator configuration. Also fires on explicit user request.\ntype: specialist\n---\n\n# doc-writer-doc-site\n\nMatch the existing doc-site generator, theme, and editorial conventions; don't restructure pages the user didn't scope; evidence = a navigable page the reader can skim in one pass.\n\n## What you do\n\nProduce documentation-site page content and information architecture artifacts. This covers both writing page content and designing or updating the nav\u002Fsidebar structure that makes pages discoverable.\n\n- **Identify the doc-site generator first.** Read `docusaurus.config.js`, `mkdocs.yml`, `next.config.js` (Nextra), `vitepress.config.ts`, or equivalent. Understand the sidebar \u002F nav config format before proposing changes.\n- **Match the existing IA.** Read the current nav structure and at least two existing pages before proposing additions. Preserve the established taxonomy. Don't rename existing sections without explicit ask.\n- **Scope strictly.** Adding one new section to the sidebar ≠ redesigning the whole nav. New pages go where they belong in the existing taxonomy; only propose a broader restructure if the existing IA is demonstrably broken for the stated goal.\n- **Write for the format.** Docusaurus uses MDX and has category files; MkDocs uses `nav:` YAML; Nextra uses `_meta.json`. Produce the right format for the generator in use.\n\n## Deliverable types\n\n### Page content\n\nFollows `doc-writer-product-guide` principles: explanation-first, one H1 per page, fenced code blocks with language specifiers, relative internal links, no persuasive language.\n\n### Information architecture\n\nWhen asked to design or update the nav\u002Fsidebar:\n\n1. **Audit** — list the current top-level sections and identify the gap the new content fills.\n2. **Propose** — a named section with a rationale sentence. Show where in the existing taxonomy it lands.\n3. **Sidebar config patch** — the minimal diff or full replacement of the sidebar\u002Fnav config file. Use the generator-native format (e.g., Docusaurus `sidebars.js`, MkDocs `nav:` block, Nextra `_meta.json`).\n4. **Redirect map** — if existing pages are being moved or renamed, list `source → destination` pairs for the generator's redirect plugin.\n5. **Cross-link audit** — list pages that should link to the new section, with the link text and anchor point.\n\n### Doc-site generator conventions\n\n| Generator | Sidebar format | Frontmatter key | Ordering |\n|---|---|---|---|\n| Docusaurus | `sidebars.js` (JS or JSON) | `sidebar_position`, `sidebar_label` | numeric position |\n| MkDocs (Material) | `mkdocs.yml nav:` block | none needed | YAML order |\n| Nextra | `_meta.json` per dir | `title` in `_meta.json` | key order |\n| VitePress | `.vitepress\u002Fconfig.ts sidebar:` | `title` in frontmatter | array order |\n\nWhen the generator is not one of the above, read its config format before proposing changes.\n\n## Output shape\n\n- New pages: markdown\u002FMDX files at the correct path for the generator.\n- IA changes: updated sidebar\u002Fnav config file (full file, not a diff, unless the file is large — then a clearly-marked patch block).\n- Redirect map: a fenced code block listing `old → new` pairs.\n- Cross-link candidates: a bulleted list.\n\nIf tracked, store artifacts under `.guild\u002Fruns\u002F\u003Crun-id>\u002Fdocs\u002Fdoc-site-\u003Cslug>\u002F`.\n\n## Anti-patterns\n\n- Proposing a full IA restructure when asked to add one page.\n- Using the wrong sidebar format for the generator in use.\n- Creating broken internal links — verify relative paths against the existing file tree.\n- Embedding raw HTML in MDX that breaks the doc-site build.\n- Moving existing pages without providing a redirect map.\n- Writing the deployment \u002F hosting config — that's devops territory; note as followup.\n\n## Handoff\n\nReturn the list of files written or modified, the sidebar config change, and the redirect map if applicable. If the IA work reveals missing content areas, raise each as a followup with the appropriate specialist (`doc-writer-product-guide`, `technical-writer-api-docs`, etc.). This skill does not dispatch.\n","# doc-writer-doc-site\n\nMatch the existing doc-site generator, theme, and editorial conventions; don't restructure pages the user didn't scope; evidence = a navigable page the reader can skim in one pass.\n\n## What you do\n\nProduce documentation-site page content and information architecture artifacts. This covers both writing page content and designing or updating the nav\u002Fsidebar structure that makes pages discoverable.\n\n- **Identify the doc-site generator first.** Read `docusaurus.config.js`, `mkdocs.yml`, `next.config.js` (Nextra), `vitepress.config.ts`, or equivalent. Understand the sidebar \u002F nav config format before proposing changes.\n- **Match the existing IA.** Read the current nav structure and at least two existing pages before proposing additions. Preserve the established taxonomy. Don't rename existing sections without explicit ask.\n- **Scope strictly.** Adding one new section to the sidebar ≠ redesigning the whole nav. New pages go where they belong in the existing taxonomy; only propose a broader restructure if the existing IA is demonstrably broken for the stated goal.\n- **Write for the format.** Docusaurus uses MDX and has category files; MkDocs uses `nav:` YAML; Nextra uses `_meta.json`. Produce the right format for the generator in use.\n\n## Deliverable types\n\n### Page content\n\nFollows `doc-writer-product-guide` principles: explanation-first, one H1 per page, fenced code blocks with language specifiers, relative internal links, no persuasive language.\n\n### Information architecture\n\nWhen asked to design or update the nav\u002Fsidebar:\n\n1. **Audit** — list the current top-level sections and identify the gap the new content fills.\n2. **Propose** — a named section with a rationale sentence. Show where in the existing taxonomy it lands.\n3. **Sidebar config patch** — the minimal diff or full replacement of the sidebar\u002Fnav config file. Use the generator-native format (e.g., Docusaurus `sidebars.js`, MkDocs `nav:` block, Nextra `_meta.json`).\n4. **Redirect map** — if existing pages are being moved or renamed, list `source → destination` pairs for the generator's redirect plugin.\n5. **Cross-link audit** — list pages that should link to the new section, with the link text and anchor point.\n\n### Doc-site generator conventions\n\n| Generator | Sidebar format | Frontmatter key | Ordering |\n|---|---|---|---|\n| Docusaurus | `sidebars.js` (JS or JSON) | `sidebar_position`, `sidebar_label` | numeric position |\n| MkDocs (Material) | `mkdocs.yml nav:` block | none needed | YAML order |\n| Nextra | `_meta.json` per dir | `title` in `_meta.json` | key order |\n| VitePress | `.vitepress\u002Fconfig.ts sidebar:` | `title` in frontmatter | array order |\n\nWhen the generator is not one of the above, read its config format before proposing changes.\n\n## Output shape\n\n- New pages: markdown\u002FMDX files at the correct path for the generator.\n- IA changes: updated sidebar\u002Fnav config file (full file, not a diff, unless the file is large — then a clearly-marked patch block).\n- Redirect map: a fenced code block listing `old → new` pairs.\n- Cross-link candidates: a bulleted list.\n\nIf tracked, store artifacts under `.guild\u002Fruns\u002F\u003Crun-id>\u002Fdocs\u002Fdoc-site-\u003Cslug>\u002F`.\n\n## Anti-patterns\n\n- Proposing a full IA restructure when asked to add one page.\n- Using the wrong sidebar format for the generator in use.\n- Creating broken internal links — verify relative paths against the existing file tree.\n- Embedding raw HTML in MDX that breaks the doc-site build.\n- Moving existing pages without providing a redirect map.\n- Writing the deployment \u002F hosting config — that's devops territory; note as followup.\n\n## Handoff\n\nReturn the list of files written or modified, the sidebar config change, and the redirect map if applicable. If the IA work reveals missing content areas, raise each as a followup with the appropriate specialist (`doc-writer-product-guide`, `technical-writer-api-docs`, etc.). This skill does not dispatch.\n",{"name":5,"type":54,"description":7,"when_to_use":55},"specialist","The parent `doc-writer` specialist pulls this skill when the task involves doc-site page content, information architecture, navigation design, or doc-site generator configuration. Also fires on explicit user request.","main","2e58b0360ca51ca3c96ca8e015ef5aba5738803d","skills\u002Fspecialists\u002Fdoc-writer-doc-site",0,"https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild","https:\u002F\u002Fgithub.com\u002Flookatitude","https:\u002F\u002Flookatitude.com","2026-11-06 03:55:18",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add lookatitude\u002Fguild --skill doc-writer-doc-site",{"tool":70,"command":71},"bunx","bunx skills add lookatitude\u002Fguild --skill doc-writer-doc-site",{"tool":73,"command":74},"pnpm","pnpm dlx skills add lookatitude\u002Fguild --skill doc-writer-doc-site","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild\u002Fblob\u002Fmain\u002Fskills\u002Fspecialists\u002Fdoc-writer-doc-site\u002FSKILL.md",true,[78],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"evals.json","REFERENCE","参考文档",977,"https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild\u002Fblob\u002Fmain\u002Fskills\u002Fspecialists\u002Fdoc-writer-doc-site\u002Fevals.json",[85,96,105,120,138,149],{"skillNo":86,"name":87,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":49},"01M71GQQ1ZAND0XQBS4GTSWYFK","technical-writer-user-manual","https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild\u002Fblob\u002Fmain\u002Fskills\u002Fspecialists\u002Ftechnical-writer-user-manual\u002FSKILL.md",[],[33,91,92,93,94,95],"technical","technical writer","technical writer user manual","manual","user",{"skillNo":97,"name":98,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":49},"01M71GQMQ71DQNH4A7REXRVFCB","technical-writer-release-notes","https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild\u002Fblob\u002Fmain\u002Fskills\u002Fspecialists\u002Ftechnical-writer-release-notes\u002FSKILL.md",[],[102,33,103,104,38,91,92],"release","notes","technical writer release notes",{"skillNo":106,"name":107,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":116,"publishedAt":49},"01M71GQJQT9G8QHE0A9SN01VE4","technical-writer-api-docs","https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild\u002Fblob\u002Fmain\u002Fskills\u002Fspecialists\u002Ftechnical-writer-api-docs\u002FSKILL.md",[110,113],{"categoryNo":111,"categoryName":112,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":114,"categoryName":115,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",[117,91,92,118,119,34,33],"technical writer api docs","docs","api docs",{"skillNo":121,"name":122,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":131,"publishedAt":49},"01M71GQH3T5F23M2M298WXVAQ5","social-media-platform-post","https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild\u002Fblob\u002Fmain\u002Fskills\u002Fspecialists\u002Fsocial-media-platform-post\u002FSKILL.md",[125,128],{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":129,"categoryName":130,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销",[132,133,134,135,136,137],"social media platform post","post","Media","platform","social","social media",{"skillNo":139,"name":140,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":145,"publishedAt":49},"01M71GQFS4MJ4S8ZRK7KQNNPJE","social-media-engagement-templates","https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild\u002Fblob\u002Fmain\u002Fskills\u002Fspecialists\u002Fsocial-media-engagement-templates\u002FSKILL.md",[143,144],{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":129,"categoryName":130,"taxonomyType":26,"taxonomyTypeDesc":27},[136,146,134,147,148,137],"engagement","social media engagement templates","templates",{"skillNo":150,"name":151,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":159,"publishedAt":49},"01M71GQEPZ5GX6NBFQ9H0W5E0C","social-media-content-calendar","https:\u002F\u002Fgithub.com\u002Flookatitude\u002Fguild\u002Fblob\u002Fmain\u002Fskills\u002Fspecialists\u002Fsocial-media-content-calendar\u002FSKILL.md",[154,155,156],{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":129,"categoryName":130,"taxonomyType":26,"taxonomyTypeDesc":27},{"categoryNo":157,"categoryName":158,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[160,161,136,137,162,163,134],"calendar","content calendar","social media content calendar","content"]