How do I install the Open Design skill?

Run npx skillmds@latest add agentik-os/open-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 Open 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 Open 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 Open Design free to use?

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

Who published Open Design?

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

Open Design by agentik-os — Agent Skill

Name: Open Design
Author: agentik-os

Open Design

Drive Open Design (self-hosted nexu-io/open-design) to build design systems and generate brand visuals from OmegaOS. It turns an agent into a design engine: prototypes, dashboards, landing pages, decks, images and video, rendered from a brand contract (DESIGN.md) using 150+ built-in design systems (apple, airbnb, ant, agentic, …), 100+ functional skills and render templates. Results are viewable in the browser over Tailscale (the OmegaOS server surface), so the operator SEES the build, not just files. Use for: building or applying a design system, a brand kit, a UI prototype, a pitch deck, marketing creatives for the marketing machine, product screens, or any "make it look designed" artifact that should be viewable at a link. Triggers (EN): "design system", "brand kit", "build a prototype", "landing page design", "pitch deck", "generate a dashboard", "marketing creative", "open design", "make a deck/prototype I can view". Triggers (FR): "design system", "kit de marque", "construire un prototype", "maquette",

agentik-os 16c9d7b 2 files · 8.5 KB Updated Sep 17, 2026

File contents

Open Design — self-hosted design engine

Open Design runs as a local Docker daemon on the OmegaOS server and is served tailnet-only so the operator can open the build in a browser. It is the OmegaOS surface for design systems and brand visuals, including the marketing machine's creatives.

The one command you start from

omega-design status        # is it up? prints the view URL
omega-design url           # the tailnet link to hand the operator

If it is not running: omega-design up && omega-design serve. The view URL is https://<tailnet-host>:7456 (e.g. https://station.tail64d114.ts.net:7456).

How it works (the model)

Design systems (design-systems/*/DESIGN.md): a brand contract — tokens, type, color, voice. 150+ ship built in (omega-design systems). Pick one, or write a project's own DESIGN.md.
Skills + templates: functional skills (omega-design skills) and render templates (omega-design templates) produce decks, prototypes, dashboards, images and video against the chosen design system.
Daemon API: everything is /api/* on the daemon (omega-design api /api/health). The web UI and the CLI both call the same endpoints — the HTTP layer is the source of truth.

Drive it from a chat (MCP)

The Open Design MCP is wired into Claude and Codex (docker exec into the daemon). Tools: list_projects, create_project, list_skills (design research), start_run (commission a design), get_run. The full capability list (162 skills by mode + 151 design systems) is in references/od-catalog.md. Use these to research a design and generate a project straight from chat.

How an OmegaOS session drives it

Confirm it's live: omega-design status (start with omega-design up && omega-design serve).
Pick / write the brand contract: choose a built-in system (omega-design systems) or write a DESIGN.md for the project under agentic/design/ (tokens, type scale, color, tone).
Generate via the daemon API (omega-design api <path> -X POST -d '…') or the web UI; artifacts land in the daemon's project and render in the browser.
Hand back the link: give the operator omega-design url so they SEE it (per R-TGDELIVER, push the link to Telegram too when it's a deliverable).

Marketing machine

For OmegaOS marketing work (R-MARKETING / R-VISUAL-ID), use Open Design to build the visual system and viewable creatives (landing pages, decks, ad mocks) that the operator reviews at the link before anything is published through Zernio (R-ZERNIO). Open Design BUILDS + shows; Zernio DISTRIBUTES.

Boundaries

External dependency: the Docker image ghcr.io/nexu-io/od + a 503M clone at ~/.omega/repos/open-design (pinned in tools/open-design/README.md). Opt-in install, not auto-run by OmegaOS install.sh (same boundary as ZernFlow / higgsfield).
Token: ~/.omega/secrets/open-design.env (never the repo). Served tailnet-only (no Funnel); the tailnet is the trusted auth layer, so daemon token-auth is disabled behind it.
Live generation is not runtime-verifiable without the running daemon + the operator opening the link.

---name: open-designdescription: Drive Open Design (self-hosted nexu-io/open-design) to build design systems and generate brand visuals from OmegaOS. It turns an agent into a design engine: prototypes, dashboards, landing pages, decks, images and video, rendered from a brand contract (DESIGN.md) using 150+ built-in design systems (apple, airbnb, ant, agentic, …), 100+ functional skills and render templates. Results are viewable in the browser over Tailscale (the OmegaOS server surface), so the operator SEES the build, not just files. Use for: building or applying a design system, a brand kit, a UI prototype, a pitch deck, marketing creatives for the marketing machine, product screens, or any "make it look designed" artifact that should be viewable at a link. Triggers (EN): "design system", "brand kit", "build a prototype", "landing page design", "pitch deck", "generate a dashboard", "marketing creative", "open design", "make a deck/prototype I can view". Triggers (FR): "design system", "kit de marque", "construire un prototype", "maquette", ---# Open Design — self-hosted design engineOpen Design runs as a local Docker daemon on the OmegaOS server and is served **tailnet-only** sothe operator can open the build in a browser. It is the OmegaOS surface for design systems andbrand visuals, including the marketing machine's creatives.## The one command you start from```bashomega-design status # is it up? prints the view URLomega-design url # the tailnet link to hand the operator```If it is not running: `omega-design up && omega-design serve`. The view URL is`https://<tailnet-host>:7456` (e.g. `https://station.tail64d114.ts.net:7456`).## How it works (the model)- **Design systems** (`design-systems/*/DESIGN.md`): a brand contract — tokens, type, color, voice. 150+ ship built in (`omega-design systems`). Pick one, or write a project's own `DESIGN.md`.- **Skills + templates**: functional skills (`omega-design skills`) and render templates (`omega-design templates`) produce decks, prototypes, dashboards, images and video against the chosen design system.- **Daemon API**: everything is `/api/*` on the daemon (`omega-design api /api/health`). The web UI and the CLI both call the same endpoints — the HTTP layer is the source of truth.## Drive it from a chat (MCP)The Open Design MCP is wired into Claude and Codex (`docker exec` into the daemon). Tools:`list_projects`, `create_project`, `list_skills` (design research), `start_run` (commission adesign), `get_run`. The full capability list (162 skills by mode + 151 design systems) is in`references/od-catalog.md`. Use these to research a design and generate a project straight from chat.## How an OmegaOS session drives it1. **Confirm it's live**: `omega-design status` (start with `omega-design up && omega-design serve`).2. **Pick / write the brand contract**: choose a built-in system (`omega-design systems`) or write a `DESIGN.md` for the project under `agentic/design/` (tokens, type scale, color, tone).3. **Generate** via the daemon API (`omega-design api <path> -X POST -d '…'`) or the web UI; artifacts land in the daemon's project and render in the browser.4. **Hand back the link**: give the operator `omega-design url` so they SEE it (per R-TGDELIVER, push the link to Telegram too when it's a deliverable).## Marketing machineFor OmegaOS marketing work (R-MARKETING / R-VISUAL-ID), use Open Design to build the visual systemand viewable creatives (landing pages, decks, ad mocks) that the operator reviews at the link beforeanything is published through Zernio (R-ZERNIO). Open Design BUILDS + shows; Zernio DISTRIBUTES.## Boundaries- External dependency: the Docker image `ghcr.io/nexu-io/od` + a 503M clone at `~/.omega/repos/open-design` (pinned in `tools/open-design/README.md`). Opt-in install, not auto-run by OmegaOS install.sh (same boundary as ZernFlow / higgsfield).- Token: `~/.omega/secrets/open-design.env` (never the repo). Served tailnet-only (no Funnel); the tailnet is the trusted auth layer, so daemon token-auth is disabled behind it.- Live generation is not runtime-verifiable without the running daemon + the operator opening the link.

Frequently asked questions