원클릭으로 Manus에서 모든 스킬 실행

시작하기

weftos-api-docs

스타85

포크6

업데이트2026년 4월 1일 00:54

Generate rustdoc API reference and deploy to weftos.weavelogic.ai/api

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

weave-logic-ai

weave-logic-ai/weftos

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

WeftOS API Docs Skill

Generate the Rust API reference from rustdoc and deploy it as part of the Fumadocs site.

How It Works

cargo doc --no-deps generates HTML for 8 publishable crates
scripts/generate-api-docs.sh copies output to docs/src/public/api/
Next.js serves the rustdoc HTML as static files at /api/
Vercel deploys on push to master

Generate API Docs

scripts/generate-api-docs.sh

This generates ~1,177 HTML pages (~42MB) covering:

weftos — product facade
clawft-kernel — kernel (process table, services, governance, mesh, ExoChain)
clawft-core — agent loop, pipeline, context, memory
clawft-types — shared types
clawft-platform — platform abstraction
clawft-plugin — plugin SDK
clawft-llm — LLM provider abstraction
exo-resource-tree — hierarchical resource namespace

Clean

scripts/generate-api-docs.sh --clean

Access

Local: http://localhost:3000/api/weftos/index.html
Production: https://weftos.weavelogic.ai/api/weftos/index.html
Fallback: https://docs.rs/weftos (auto-built by docs.rs from crates.io)

Key Details

Output goes to docs/src/public/api/ (gitignored — generated, not committed)
Source viewer is stripped to save ~11MB (users read source on GitHub)
/api/ redirects to /api/weftos/index.html
Rustdoc includes its own CSS/JS/fonts — no Fumadocs styling conflict
Search works within rustdoc pages (client-side, self-contained)

When to Regenerate

After any public API changes (new structs, functions, traits, doc comments)
Before a release that updates docs
After adding new publishable crates

For Vercel Deployment

The generate-api-docs.sh should run as a pre-build step. Add to docs/src/package.json:

"scripts": {
  "prebuild": "cd ../.. && scripts/generate-api-docs.sh",
  "build": "next build"
}

Or configure in Vercel dashboard: Build Command = cd ../.. && scripts/generate-api-docs.sh && cd docs/src && npm run build

이 저장소의 다른 Skills

같은 저장소

weftos-design

weave-logic-ai/weftos

Authoritative design discipline for WeftOS surfaces — tokens, composer-primitive usage, surface archetypes, empty/loading/offline contract, a11y floor, and OOB stock-desktop manifest. Use whenever creating, reviewing, or modifying a TOML surface fixture, the egui theming layer, or any user-visible WeftOS pane. Codifies docs/DESIGN.md and provides scaffold + audit scripts.

2026-05-0285

plane-workflow

weave-logic-ai/weftos

Authoritative Plane work-tracker discipline for WeftOS / clawft. Use whenever you create, claim, finish, or defer a meaningful unit of work, or when triaging audits / TODOs / FIXMEs / orphans into Plane work items. Codifies the lifecycle (Backlog → Todo → In Progress → Done | Cancelled), the cycle taxonomy (0.7.x must-ship, 0.8.x / 0.9.x / 1.0.x deferred), and the HTTP API workaround for the partially-broken MCP server.

2026-04-3085

weftos-docs-deploy

weave-logic-ai/weftos

Deploy Fumadocs site to Vercel at weftos.weavelogic.ai (always run after docs/src changes)

2026-04-0185

weftos-build-deploy

weave-logic-ai/weftos

Build, test, publish, and deploy WeftOS across all channels (GitHub Releases, crates.io, npm, Docker, Homebrew)

2026-04-0185

agent-dispatch

weave-logic-ai/weftos

Route tasks to external agents via MCP (preferred) or CLI fallback. LightLLM translation layer with intelligent routing based on task complexity, cost, and agent capabilities.

2026-03-0185

claude-flow

weave-logic-ai/weftos

Preferred development orchestration via claude-flow MCP. Full planning pipeline (business-requirements -> technical architecture -> development planning -> SPARC), multi-agent swarms, shared memory, self-learning hooks, and 150+ tools across 20 domains.

2026-03-0185

name	weftos-api-docs
description	Generate rustdoc API reference and deploy to weftos.weavelogic.ai/api
triggers	["api docs","rustdoc","generate api reference","update api docs"]

WeftOS API Docs Skill

Generate the Rust API reference from rustdoc and deploy it as part of the Fumadocs site.

How It Works

cargo doc --no-deps generates HTML for 8 publishable crates
scripts/generate-api-docs.sh copies output to docs/src/public/api/
Next.js serves the rustdoc HTML as static files at /api/
Vercel deploys on push to master

Generate API Docs

scripts/generate-api-docs.sh

This generates ~1,177 HTML pages (~42MB) covering:

weftos — product facade
clawft-kernel — kernel (process table, services, governance, mesh, ExoChain)
clawft-core — agent loop, pipeline, context, memory
clawft-types — shared types
clawft-platform — platform abstraction
clawft-plugin — plugin SDK
clawft-llm — LLM provider abstraction
exo-resource-tree — hierarchical resource namespace

Clean

scripts/generate-api-docs.sh --clean

Access

Local: http://localhost:3000/api/weftos/index.html
Production: https://weftos.weavelogic.ai/api/weftos/index.html
Fallback: https://docs.rs/weftos (auto-built by docs.rs from crates.io)

Key Details

Output goes to docs/src/public/api/ (gitignored — generated, not committed)
Source viewer is stripped to save ~11MB (users read source on GitHub)
/api/ redirects to /api/weftos/index.html
Rustdoc includes its own CSS/JS/fonts — no Fumadocs styling conflict
Search works within rustdoc pages (client-side, self-contained)

When to Regenerate

After any public API changes (new structs, functions, traits, doc comments)
Before a release that updates docs
After adding new publishable crates

For Vercel Deployment

The generate-api-docs.sh should run as a pre-build step. Add to docs/src/package.json:

"scripts": {
  "prebuild": "cd ../.. && scripts/generate-api-docs.sh",
  "build": "next build"
}

Or configure in Vercel dashboard: Build Command = cd ../.. && scripts/generate-api-docs.sh && cd docs/src && npm run build