菜单
Use this skill to generate well-branded interfaces and assets for AUV (the Moeru AI command-replay / inspect runtime), either for production or throwaway prototypes/mocks. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/moeru-ai/auv --skill auv-design命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Design, change, and review Protobuf schemas used as gRPC contracts, streaming protocols, typed data models, grpc-gateway REST APIs, OpenAPI specifications, or generated SDK inputs. Use for .proto files, RPC request/response design, oneof stream events, validation annotations, API versioning, schema evolution, generated package layout, and avoiding weak Struct or Any payloads.
Select, pin, configure, install, build, and troubleshoot Buf code-generation plugins across remote BSR and local execution. Use for buf.gen.yaml plugin entries, protoc-gen-* tools, generated Go/Python/TypeScript/OpenAPI outputs, offline generation, BSR connectivity or rate-limit failures, OCI-packaged plugin wrappers, or reproducing plugins from bufbuild/plugins.
Configure, inspect, update, validate, and troubleshoot Buf workspaces and modules. Use when working with buf.yaml, buf.lock, buf.gen.yaml or domain-specific Buf generation templates; managing BSR dependencies; formatting, linting, generating, detecting breaking Protobuf changes; locating dependency schemas; or diagnosing missing types and generation failures.
基于 SOC 职业分类
正在显示 SKILL.md
| name | auv-design |
| description | Use this skill to generate well-branded interfaces and assets for AUV (the Moeru AI command-replay / inspect runtime), either for production or throwaway prototypes/mocks. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping. |
| user-invocable | true |
Read README.md in this skill first — it establishes product context, content
fundamentals (the deliberately anti-marketing AUV voice), visual foundations,
and iconography rules.
Then explore the other files:
colors_and_type.css — all design tokens (--auv-*).assets/ — logo mark + wordmark.preview/ — small reference cards for each system concept.ui_kits/cli/ — auv-cli terminal output recreation.ui_kits/viewer/ — speculative inspect-viewer mock (the browser viewer
described in 2026-05-19-trace-run-inspect-design.md; not built yet in
the source repo).validated,
candidate, and not-validated in JSON. Reflect that in every artifact.
Never invent a status not on the canonical list.JetBrains Mono. Body prose lives in Geist..auv-status--{validated, candidate, boundary, frozen, running, failed} everywhere a status is
shown — sidebars, lists, headers, terminal output, marketing.If creating visual artifacts (slides, mocks, throwaway prototypes), copy
assets out of this skill and produce static HTML the user can view. Reuse the
<Terminal> / <SpanTree> / <Sidebar> components from the UI kits when the
output is product-facing.
If working on production code (Rust CLI, future browser viewer, future docs
site), copy colors_and_type.css and assets/logo-*.svg into the project,
and follow the rules in README.md (sections Content Fundamentals and
Visual Foundations) to extend the system.
If invoked without other guidance, ask the user what they want to build — typical asks are:
auv-cli output for a docs page or social postThen act as an expert designer on the AUV brand and output HTML artifacts or production code, depending on the need.