Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Read, write, search, and manage Feishu (Lark) cloud documents and knowledge bases via the feishu-docs CLI. Use this skill whenever the user mentions Feishu docs, Lark docs, knowledge bases (wiki spaces), or wants to interact with Feishu cloud documents in any way — reading, creating, updating, deleting, searching, sharing, or browsing wiki structure. Also trigger when the user pastes a Feishu or Lark URL, or mentions feishu-docs-cli. This skill covers both Chinese (飞书) and international (Lark) platforms.
RESTful API design best practices including resource naming, HTTP methods, status codes, filtering, pagination, authentication, and OpenAPI documentation. Use when designing or reviewing REST APIs, web APIs, or API endpoints.
Use when researching what the vault knows about a topic — performs graph + semantic exploration with gap analysis to map existing knowledge and find missing connections. Primarily used via the vault-explorer agent. Not for routine session-start context loading (hooks handle that).
Answer "how does X work?" questions using scope docs and evidence links — the SMARTEST way to understand code
Use when conducting a thorough code review for governed skill, prompt, and agent-configuration repositories. Focus on routing correctness, contract drift, installer safety, portability, and docs/tests/catalog consistency. Produces a structured review with risk register and prioritized action items. Use when user mentions review skill config, review agent config, routing review, installer review, or skill repository review.
Comprehensive project architecture blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks and architectural patterns, generates visual diagrams, documents implementation patterns, and provides extensible blueprints for maintaining architectural consistency and guiding new development.
AI-generated documentation for GitHub repositories
为任何项目创建完整的文档网站。当被要求时使用此技能： "创建文档", "添加文档", "建立文档网站", "生成文档", "文档化项目", "编写文档", "初始化文档", "添加文档文件夹", "创建文档网站"。生成基于 Movk Nuxt Docs 的网站 包含搜索、深色模式、MCP 服务器和 llms.txt 集成。 --- # 创建文档 为任何项目生成完整的、生产就绪的文档网站。 ## 工作流程 1. **分析** - 检测包管理器、monorepo 结构、读取上下文 2. **初始化** - 使用正确的设置创建文档目录 3. **生成** - 使用模板编写文档页面 4. **配置** - 设置 AI 集成（MCP、llms.txt） 5. **最终化** - 提供后续步骤和正确的命令 --- ## 包管理器参考 从 lock 文件检测，如果未找到则默认使用 npm： | Lock 文件 | PM | 安装 | 运行 | 添加 | |-----------|------|---------|-----|-----| | `pnpm-lock.yaml` | pnpm | `pnpm install` | `pnpm run` | `pnpm add` | | `package-lock.json` | npm | `npm install` | `npm run` | `npm install` | | `yarn.lock` | yarn | `yarn install` | `yarn` | `yarn add` | | `bun.lockb` | bun | `bun install` | `bun run` | `bun add` | 在下面的命令中使用 `[pm]` 作为占位符。 --- ## 步骤 1：分析项目 ### 检测项目结构 ``` 检查： ├── pnpm-workspace.yaml → pnpm monorepo ├── turbo.json → Turborepo monorepo ├── lerna.json → Lerna monorepo ├── nx.json → Nx monorepo ├── apps/ → Apps 目录（monorepo） ├── packages/ → Packages 目录（monorepo） ├── docs/ → 现有文档（避免覆盖） ├── README.md → 主文档源 └── src/ 或 lib/ → 源代码位置 ``` ### 确定文档位置 | 项目类型 | 目标目录 | Workspace 项目 | |--------------|------------------|-----------------| | 标准项目 | `./docs` | N/A | | Monorepo with `apps/` | `./apps/docs` | `apps/docs` | | Monorepo with `packages/` | `./docs` | `docs` | | 现有 `docs/` 文件夹 | 询问用户或 `./documentation` | — | ### 读取上下文文件 | 文件 | 提取 | |------|---------| | `README.md` | 项目名称、描述、功能、使用示例 | | `package.json` | 名称、描述、依赖、仓库 URL | | `src/` 或 `lib/` | 导出的函数、可组合项用于 API 文档 | --- ## 步骤 2：初始化文档 ### 创建目录结构 ```bash # 完整模板
Browser automation via agent-browser CLI. Use when you need to navigate websites, verify deployed UI, test web apps, read online documentation, scrape data, fill forms, capture baseline screenshots before design work, or inspect current page state. Triggers on "check the page", "verify UI", "test the site", "read docs at", "look up API", "visit URL", "browse", "screenshot", "scrape", "e2e test", "login flow", "capture baseline", "see how it looks", "inspect current", "before redesign".
