Menu
Slax 官网开发技能。当开发、维护 Slax 官网（Astro + Starlight monorepo）时使用，包括博客编写、文档维护、组件开发、SEO 配置等。
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | slax-home-developer |
| description | Slax 官网开发技能。当开发、维护 Slax 官网（Astro + Starlight monorepo）时使用，包括博客编写、文档维护、组件开发、SEO 配置等。 |
| user-invocable | true |
| disable-model-invocation | false |
你是 Slax 官网的开发助手。在进行任何开发工作前，请先阅读以下配套文件以了解完整规范：
CODE.md（同目录）：编码规范、Frontmatter 字段说明、Git 提交规范、构建检查清单、快速参考卡（网页内容/博客/落地页 MDX 结构）STYLE.md（同目录）：UI 色彩规范、圆角/阴影/间距/按钮/表单样式标准；落地页设计系统（各应用主题色、Starlight Token、动画规范、背景光球、组件规范 ProductCard/ProductGrid/FeatureCard/FeatureGrid/CallToAction/TextImage/Highlight、可访问性）Slax 官网是基于 Astro 6 + Starlight 的 pnpm monorepo，托管在 https://slax.com，包含三个子站：
| 子应用 | 路径 | 开发端口 | 说明 |
|---|---|---|---|
slax-home | / | 4321 | 主站 + 博客（Starlight + starlight-blog） |
reader-home | /reader | 4322 | Slax Reader 文档站 |
note-home | /note | 4323 | Slax Note 文档站 |
script/build.sh 合并三站输出到 dist/slax-home-page/
├── apps/
│ ├── slax-home/ # 主站
│ │ ├── astro.config.mjs
│ │ ├── src/
│ │ │ ├── content.config.ts # 内容集合（docsSchema + blogSchema）
│ │ │ ├── content/
│ │ │ │ ├── docs/ # 英文内容
│ │ │ │ │ ├── index.mdx
│ │ │ │ │ ├── blog/ # 博客文章
│ │ │ │ │ ├── guides/
│ │ │ │ │ └── reference/
│ │ │ │ └── i18n/
│ │ │ └── components/
│ │ │ └── Head.astro # 自定义 SEO Head（JSON-LD）
│ │ └── public/
│ │ ├── admin/ # CMS（TinaCMS）
│ │ └── robots.txt
│ ├── reader-home/
│ └── note-home/
├── public/skill/slax-home-developer/ # 本 Skill
├── script/build.sh # 合并构建脚本
├── package.json
├── pnpm-workspace.yaml
└── tsconfig.json
2026-03-30T00:00:00.000Zhttps://static-cdn.slax.com/...draft: true，生产自动排除CODE.mdsidebar 配置public/components 选项pnpm dev：并行启动三站pnpm build：构建并合并到 dist/pnpm preview：预览产物BlogPosting JSON-LD（含 datePublished）WebPage JSON-LDBreadcrumbListclient:* 指令content.config.ts + Zod 验证astro:assets 的 <Image> 组件Audit docs.warp.dev for agent-friendly documentation issues using the AFDocs scorecard. Checks llms.txt, markdown availability, content negotiation, page size, URL stability, and content structure. Use when asked to check agent readiness, run an AFDocs audit, improve the docs score, or verify llms.txt and markdown support.
Answer questions about Warp, Oz, agents, terminal features, billing, pricing, troubleshooting, privacy, skills, MCP, integrations, or any other Warp-related topic. Use when a user, support person, or engineer asks a question that can be answered from Warp's documentation. Searches the docs, synthesizes a comprehensive answer, and provides links to relevant doc pages.
Check the Warp Astro Starlight documentation for broken links by scanning source markdown files. Run the diagnostic script, review the output, fix broken links, and optionally notify Slack.
Create a pull request in the docs repository for the current branch. Use when the user mentions opening a PR, creating a pull request, submitting changes for review, or preparing documentation for merge.
Audit docs.warp.dev for SEO issues like duplicate titles, missing meta descriptions, title length problems, and H1 tag issues. Crawls the live sitemap, generates a report, and fixes issues in the source markdown. Use when asked to check SEO, fix duplicate titles, audit meta tags, improve search rankings, or run an SEO check on the docs site.
Draft a new conceptual documentation page or update an existing one. Use for pages that explain what something is, why it exists, and how it works — without step-by-step procedures. Examples include product overviews, architecture explanations, and design philosophy pages.