design

Name: design
Author: moeru-ai

20stars2forks

How to install design?

moeru-ai/auv/design

$npx -y skills add moeru-ai/auv --skill design

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# AUV Design
2
3	Read `README.md` in this skill first — it establishes product context, content
4	fundamentals (the deliberately anti-marketing AUV voice), visual foundations,
5	and iconography rules.
6
7	Then explore the other files:
8
9	- `colors_and_type.css` — all design tokens (`--auv-*`).
10	- `assets/` — logo mark + wordmark.
11	- `preview/` — small reference cards for each system concept.
12	- `ui_kits/cli/` — `auv-cli` terminal output recreation.
13	- `ui_kits/viewer/` — speculative inspect-viewer mock (the browser viewer
14	described in `2026-05-19-trace-run-inspect-design.md`; not built yet in
15	the source repo).
16
17	## Operating principles for this brand
18
19	1. Honesty over polish. AUV documents what is `validated`,
20	`candidate`, and `not-validated` in JSON. Reflect that in every artifact.
21	Never invent a status not on the canonical list.
22	2. Monospace carries identity. IDs, paths, span names, and JSON keys
23	live in `JetBrains Mono`. Body prose lives in `Geist`.
24	3. No emoji. No gradients. No glassy overlays. This is forensic-grade UI.
25	4. Status pill is the smallest unit. Use `.auv-status--{validated,
26	candidate, boundary, frozen, running, failed}` everywhere a status is
27	shown — sidebars, lists, headers, terminal output, marketing.
28
29	## When the user invokes this skill
30
31	If creating visual artifacts (slides, mocks, throwaway prototypes), copy
32	assets out of this skill and produce static HTML the user can view. Reuse the
33	`<Terminal>` / `<SpanTree>` / `<Sidebar>` components from the UI kits when the
34	output is product-facing.
35
36	If working on production code (Rust CLI, future browser viewer, future docs
37	site), copy `colors_and_type.css` and `assets/logo-*.svg` into the project,
38	and follow the rules in `README.md` (sections Content Fundamentals and
39	Visual Foundations) to extend the system.
40
41	If invoked without other guidance, ask the user what they want to build —
42	typical asks are:
43	- a mock of `auv-cli` output for a docs page or social post
44	- a wireframe / mock of the inspect viewer
45	- a slide deck explaining a phase-1 boundary
46	- copy in the AUV voice (status report, freeze note, boundary callout)
47
48	Then act as an expert designer on the AUV brand and output HTML artifacts or
49	production code, depending on the need.

People who liked this also viewed

6 picks

Type

design

20stars2forks

View on GitHub

How to install design?

moeru-ai/auv/design

$npx -y skills add moeru-ai/auv --skill design

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# AUV Design
2
3	Read `README.md` in this skill first — it establishes product context, content
4	fundamentals (the deliberately anti-marketing AUV voice), visual foundations,
5	and iconography rules.
6
7	Then explore the other files:
8
9	- `colors_and_type.css` — all design tokens (`--auv-*`).
10	- `assets/` — logo mark + wordmark.
11	- `preview/` — small reference cards for each system concept.
12	- `ui_kits/cli/` — `auv-cli` terminal output recreation.
13	- `ui_kits/viewer/` — speculative inspect-viewer mock (the browser viewer
14	described in `2026-05-19-trace-run-inspect-design.md`; not built yet in
15	the source repo).
16
17	## Operating principles for this brand
18
19	1. Honesty over polish. AUV documents what is `validated`,
20	`candidate`, and `not-validated` in JSON. Reflect that in every artifact.
21	Never invent a status not on the canonical list.
22	2. Monospace carries identity. IDs, paths, span names, and JSON keys
23	live in `JetBrains Mono`. Body prose lives in `Geist`.
24	3. No emoji. No gradients. No glassy overlays. This is forensic-grade UI.
25	4. Status pill is the smallest unit. Use `.auv-status--{validated,
26	candidate, boundary, frozen, running, failed}` everywhere a status is
27	shown — sidebars, lists, headers, terminal output, marketing.
28
29	## When the user invokes this skill
30
31	If creating visual artifacts (slides, mocks, throwaway prototypes), copy
32	assets out of this skill and produce static HTML the user can view. Reuse the
33	`<Terminal>` / `<SpanTree>` / `<Sidebar>` components from the UI kits when the
34	output is product-facing.
35
36	If working on production code (Rust CLI, future browser viewer, future docs
37	site), copy `colors_and_type.css` and `assets/logo-*.svg` into the project,
38	and follow the rules in `README.md` (sections Content Fundamentals and
39	Visual Foundations) to extend the system.
40
41	If invoked without other guidance, ask the user what they want to build —
42	typical asks are:
43	- a mock of `auv-cli` output for a docs page or social post
44	- a wireframe / mock of the inspect viewer
45	- a slide deck explaining a phase-1 boundary
46	- copy in the AUV voice (status report, freeze note, boundary callout)
47
48	Then act as an expert designer on the AUV brand and output HTML artifacts or
49	production code, depending on the need.

People who liked this also viewed

6 picks

Type