3.3 KiB
Documentation map
Use the documentation site for user workflows, repository guides for engineering and operations, and source/tests for exact current behavior. Numbered design documents are not a chronological tutorial or a promise that every proposed feature is implemented.
Users and authors
| Task | 中文 | English |
|---|---|---|
| Install and use your first skill | 快速开始 | Quick Start |
| CLI authentication, install, upgrade and sync | CLI | CLI |
| Install and use a versioned collection | 技能套装 | Skill Suites |
| Upload a collection and member packages | Bundle 导入 | Bundle import |
| Publish skills and track versions | 发布 | Publishing |
| Manage access and review | 命名空间 · 审核 | Namespaces · Review |
| Troubleshoot | FAQ | FAQ |
Operators
- Docker deployment and upgrades / 中文
- Kubernetes / 中文
- Optional frontend analytics / 前端动作统计
- Deployment reference, object storage, SMTP and password reset
- Security scanning, observability, private SSO integration
Contributors and integrators
- Contributing, development workflow, engineering specs
- System architecture, domain model, API design
- Skill package protocol, lifecycle contract, Suite semantics, authoring drafts
- Runtime integration, OpenClaw, Hermes, DeepSeek Harness
Plans and historical evidence
Roadmaps, files titled plan, dated design proposals, research under research/, and test reports record decisions or evidence at a point in time. Check their implementation status against current code before treating them as supported features. Examples include the delivery roadmap, starter skills plan, and observability construction plan.
For documentation changes, update both language journeys and navigation, verify commands against the source, then run npm ci and npm run build from docs/skillhub. A documentation build checks rendering and links, not deployment or live registry behavior.