How do I install the Auv Design skill?

Run npx skillmds@latest add moeru-ai/auv-design in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Auv Design safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Auv Design?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Auv Design free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Auv Design?

moeru-ai (@moeru-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Auv Design by moeru-ai — Agent Skill

Name: Auv Design
Author: moeru-ai

Auv Design

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.

moeru-ai Updated Sep 17, 2026

File contents

AUV Design

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).

Operating principles for this brand

Honesty over polish. AUV documents what is validated, candidate, and not-validated in JSON. Reflect that in every artifact. Never invent a status not on the canonical list.
Monospace carries identity. IDs, paths, span names, and JSON keys live in JetBrains Mono. Body prose lives in Geist.
No emoji. No gradients. No glassy overlays. This is forensic-grade UI.
Status pill is the smallest unit. Use .auv-status--{validated, candidate, boundary, frozen, running, failed} everywhere a status is shown — sidebars, lists, headers, terminal output, marketing.

When the user invokes this skill

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:

a mock of auv-cli output for a docs page or social post
a wireframe / mock of the inspect viewer
a slide deck explaining a phase-1 boundary
copy in the AUV voice (status report, freeze note, boundary callout)

Then act as an expert designer on the AUV brand and output HTML artifacts or production code, depending on the need.

---name: auv-designdescription: 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.---# AUV DesignRead `README.md` in this skill first — it establishes product context, contentfundamentals (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).## Operating principles for this brand1. **Honesty over polish.** AUV documents what is `validated`, `candidate`, and `not-validated` in JSON. Reflect that in every artifact. Never invent a status not on the canonical list.2. **Monospace carries identity.** IDs, paths, span names, and JSON keys live in `JetBrains Mono`. Body prose lives in `Geist`.3. **No emoji. No gradients. No glassy overlays.** This is forensic-grade UI.4. **Status pill is the smallest unit.** Use `.auv-status--{validated, candidate, boundary, frozen, running, failed}` everywhere a status is shown — sidebars, lists, headers, terminal output, marketing.## When the user invokes this skillIf creating visual artifacts (slides, mocks, throwaway prototypes), copyassets out of this skill and produce static HTML the user can view. Reuse the`<Terminal>` / `<SpanTree>` / `<Sidebar>` components from the UI kits when theoutput is product-facing.If working on production code (Rust CLI, future browser viewer, future docssite), 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:- a mock of `auv-cli` output for a docs page or social post- a wireframe / mock of the inspect viewer- a slide deck explaining a phase-1 boundary- copy in the AUV voice (status report, freeze note, boundary callout)Then act as an expert designer on the AUV brand and output HTML artifacts orproduction code, depending on the need.

Frequently asked questions