文档生成
- 作者仓库星标 0
- 作者更新于 实时读取
- 作者仓库 nano-core
- 领域
- 文档
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @0-CYBERDYNE-SYSTEMS-0 · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- macOS
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: docs
description: Generate professional software documentation with rigorous Generate stunning, professional softw…
category: 文档
runtime: 无特殊运行时
---
# docs 输出预览
## PART A: 任务判断
- 适用问题:PRD、RFC、README、项目说明或知识库整理。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“When to use this skill / When not to use this skill / Philosophy”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于PRD、RFC、README、项目说明或知识库整理,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“When to use this skill / When not to use this skill / Philosophy”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文没有稳定的斜杠命令要求。安装验证后通常全局生效,直接在对话里点名这个 Skill 并描述任务即可。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件。
先用一个小任务确认它会围绕“When to use this skill / When not to use this skill / Philosophy”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: docs
description: Generate professional software documentation with rigorous Generate stunning, professional softw…
category: 文档
source: 0-CYBERDYNE-SYSTEMS-0/nano-core
---
# docs
## 什么时候使用
- docs 是文档方向的技能,对外说明 适合处理README、PRD、RFC、教程和知识库文档,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤;通常不需要额外…
- 面向PRD、RFC、README、项目说明或知识库整理,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「When to use this skill / When not to use this skill / Philosophy」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "docs" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> When to use this skill / When not to use this skill / Philosophy
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} Docs Skill - Professional Software Documentation Generator
When to use this skill
- Use when the user request matches this skill's domain and capabilities.
- Use when this workflow or toolchain is explicitly requested.
When not to use this skill
- Do not use when another skill is a better direct match for the task.
- Do not use when the request is outside this skill's scope.
Generate stunning, professional software documentation that elevates your projects above the competition. This skill implements a rigorous 4-phase process powered by AI models for maximum impact.
Philosophy
This skill represents documentation excellence through:
- Rigorous Discovery - Comprehensive project analysis leaving no detail unexplored
- Kimi K2.5 Thinking - Advanced reasoning for optimal documentation architecture
- Gemini 3 Flash Design - Modern, cutting-edge visual design generation
- Unique Positioning - Documentation that differentiates your project
Rigorous Research Routine
Before generating any documentation, the skill performs exhaustive investigation:
Project Analysis
- Complete file tree traversal and categorization
- Language detection and version identification
- Dependency mapping and ecosystem analysis
- Architecture pattern recognition
- Code complexity and structure assessment
Ecosystem Investigation
- Framework and library detection
- Database and service integrations
- API patterns and contract analysis
- Build tool and deployment configuration
- Testing infrastructure mapping
Audience Research
- Target user persona analysis
- Use case pattern extraction
- Competitor documentation benchmarking
- Industry best practices integration
- SEO optimization for discoverability
Competitive Analysis
- Feature comparison and differentiation
- Unique selling proposition extraction
- Documentation style benchmarking
- Visual design trend integration
Kimi K2.5 Thinking Phase
The Kimi K2.5 model (via kimi-code/kimi-for-coding) powers deep reasoning for:
- Documentation Architecture: Optimal section structure and navigation
- Content Strategy: What to document, depth per section
- Example Selection: Best code snippets to showcase features
- User Journey Mapping: Logical flow from introduction to mastery
- Gap Analysis: Identifying undocumented areas
Thinking Process Outputs
- Documentation skeleton with prioritized sections
- Key messages and value propositions
- Recommended example scenarios
- Audience-appropriate technical depth
- SEO keywords and meta descriptions
Gemini 3 Flash Design Phase
Gemini 3 Flash generates modern, production-ready documentation designs:
Modern Design Features
- Swiss/Brutalist typography with strong grid alignment
- Monospace metadata blocks for AI agent parsing
- Semantic structure with clear hierarchy markers
- Minimal color - black, white, single accent
- High contrast - crisp edges, no blur effects
- Structured data blocks - JSON-LD ready, LLM-friendly
Design Trends (2025)
- Swiss precision - grid systems, asymmetric balance
- Brutalist clarity - raw typography, high contrast
- Monospace data - machine-readable blocks
- No gradients, no blur, no shadows
- One accent color - maximum impact
- Flowing prose for humans, structured blocks for AI
Usage
uv run {baseDir}/scripts/generate_docs.py --path "/path/to/project" --type "all"
Output Types
| Type | Description | Best For |
|---|---|---|
readme |
Comprehensive README with badges, setup, usage | GitHub repos |
api |
Complete API reference with examples | Libraries, SDKs |
guide |
User guides and tutorials | Onboarding, how-tos |
website |
Full static site (HTML/CSS/JS) | Documentation portals |
all |
Complete documentation suite | Full projects |
Options
| Option | Description |
|---|---|
--path, -p |
Project root path (required) |
--type, -t |
Documentation type: readme/api/guide/website/all |
--output, -o |
Output directory |
--theme |
Theme: brutalist/swiss/minimal/technical |
--title |
Project title (auto-detected if omitted) |
--tagline |
One-line description for hero section |
--audience |
Target: beginners/intermediate/experts |
--ai-think |
Enable Kimi K2.5 reasoning (default: auto) |
--ai-design |
Enable Gemini 3 Flash design (default: auto) |
Examples
# Full documentation suite with AI enhancement
uv run {baseDir}/scripts/generate_docs.py -p ~/myproject -t all --ai-think --ai-design
# README only with brutalist theme
uv run {baseDir}/scripts/generate_docs.py -p ~/myproject -t readme --theme brutalist \
--title "SuperTool" --tagline "The ultimate solution for modern workflows"
# Complete website documentation with swiss theme
uv run {baseDir}/scripts/generate_docs.py -p ~/project -t website \
--audience experts --title "Enterprise SDK" --theme swiss
# API documentation with technical theme
uv run {baseDir}/scripts/generate_docs.py -p ~/library -t api --theme technical
Model Configuration
Configure AI models for optimal performance:
{
"skills": {
"docs": {
"thinkModel": "kimi-code/kimi-for-coding",
"designModel": "gemini-2.0-flash",
"features": {
"reasoning": true,
"designGeneration": true,
"seoOptimization": true,
"interactiveExamples": true
}
}
}
}
Model Selection Guide
| Phase | Model | Purpose | When to Use |
|---|---|---|---|
| Thinking | Kimi K2.5 | Architecture, structure, content strategy | Complex projects, unique requirements |
| Design | Gemini 3 Flash | Visual design, modern layouts | All projects (fast and capable) |
| Fallback | MiniMax-M2.1 | General generation | When specialized models unavailable |
Best Practices Applied
Generated documentation includes:
Content Excellence
- Compelling hero section with clear value proposition
- Quick start guide for immediate productivity
- Comprehensive examples with real-world scenarios
- API reference with parameter tables
- Troubleshooting and FAQ sections
- Contributing guidelines with workflow diagrams
Visual Design
- Modern CSS with CSS custom properties
- Responsive grid layouts
- Accessible color schemes
- Print-friendly styles
- Syntax highlighting (via Prism.js ready structure)
- Copy-to-clipboard functionality
SEO & Discovery
- Semantic HTML structure
- Meta description optimization
- Open Graph tags for social sharing
- Sitemap-ready structure
- Canonical URLs
- Structured data (JSON-LD ready)
Performance
- Minimal CSS (under 10KB gzipped)
- No external dependencies (self-contained)
- Lazy loading for images
- Critical CSS inline
- Cache-friendly asset structure
Integration Points
GitHub Integration
- Shields.io badges ready
- Issue/PR templates auto-generated
- GitHub Pages deployment ready
- Actions workflow documentation
CI/CD Integration
- Documentation build in pipelines
- Automated API doc generation
- Version-based doc branching
- Deploy preview support
Troubleshooting
| Issue | Solution |
|---|---|
| Missing dependencies | Install: uv pip install -r requirements.txt |
| AI models unavailable | Fallback to template-based generation |
| Large projects | Use --type readme first, then expand |
| Custom themes | Place CSS in docs/theme.css for override |
Performance Tips
- For large monorepos: Generate docs per package with
--output - For frequent updates: Use
--type apifor incremental API docs - For release notes: Generate CHANGELOG.md alongside docs
- For multi-language: Generate docs per language with separate runs
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核