GOAT-Net Design Skill¶
You are designing for GOAT-Net — an opinionated open-source data substrate for sovereign edge deployments. The product is a software-defined tactical data fabric assembled from Netbird (identity-based WireGuard mesh), Eclipse Zenoh (partition-tolerant pub/sub), and an offline-CA enrollment chain. It runs at the edge, on commodity hardware, with the management plane silent on the public internet by design.
How to use this skill¶
- Read
README.mdin this skill folder first. It contains everything: product context, content fundamentals, visual foundations, iconography. - Look at
colors_and_type.cssandcomponents.cssfor tokens and component classes. Reach for the semantic tokens (--bg-card,--fg-accent,--accent,--border) not the primitives. - Browse
preview/*.htmlto see how each token is meant to look in isolation. - Look at the
ui_kits/for full reference surfaces: ui_kits/console/— operator console (catalog + peer drawer)ui_kits/brief/— slide-deck shell with 6 slide-type patterns- Look at
assets/for the goat marks and the in-house diagram library extracted from the source repo.
When creating visual artifacts¶
- For slides/decks/briefs, copy
ui_kits/brief/as the starting point. Its slide-type patterns (slide--title,slide--section,slide--two-col,slide--stat,slide--quote,slide--code) cover most of what briefs in this voice need. Usedeck-stage.jsfor the shell. - For operator surfaces, copy
ui_kits/console/as the starting point. The components there are small, modular, and reusable. - For standalone pages, import
colors_and_type.cssandcomponents.cssat the top, then build from.t-*typography classes and.btn/.chip/.cardcomponent classes. - Copy assets out when authoring an artifact — don't link across
projects. Put copied marks under
assets/in the output project.
Voice — the most distinctive part¶
- Matter-of-fact, technical, specific about failures.
- No marketing warmth. No "we're excited to," "seamless," or "world-class."
- No exclamation points. Anywhere.
- No emoji in product surfaces. Exception:
⚠in markdown migration banners only. - Sentence case for titles and headlines. UPPERCASE-MONO is reserved
for system labels (
STATUS,PEER,BLOCK 22). - Use technical specifics: acronyms (STUN, CGNAT, ML-KEM), durations ("90d expiry"), version numbers ("Block 22").
Visual one-liner¶
Near-black backgrounds. One glowing tactical-green accent
(#34d97e, derived from the brand #20964f). Sharp corners everywhere
except status chips. Monospace for any data the machine knows. No drop
shadows, no gradients-as-decoration, no photography, no rounded-corner
cards with a colored left strip.
If the user invokes this skill without other guidance¶
Ask them: 1. What are they making — slide, dashboard, landing page, runbook? 2. What surface size — 1280×720, 1920×1080, fluid? 3. Production code or a throwaway HTML mock?
Then act as an expert designer in the GOAT-Net language and output an HTML artifact (or production code, if asked) that matches this system.
Production vs prototype¶
- For prototypes/mocks, copy assets and inline the CSS as needed. Single-file HTML is fine.
- For production, this skill folder is a design reference — pull tokens, type, and component patterns into the actual codebase rather than copying these files verbatim.
Sources you can read further¶
If you have access (the repo is private and these are pinned URLs):
- https://github.com/usareur-af/goatcore
raw/zenoh-brief.mdin this skill — the best single sample of the voiceraw/manifesto.mdin this skill — manifesto framing