97.4K+Download
Copilot OpenDesign

Design With
Copilot in
OpenDesign.

How to design interfaces with GitHub Copilot CLI in OpenDesign: a screenshot as the input, your repository’s components reused, one launch-page task from brief to reviewed file, and the limits to know before you start.

Download OpenDesign Go to setup
From brief to interface01 / Copilot
YOU BRING THE IDEA↗

“A launch page built from
the screenshot, with our components.”

Illustrative interface · not a captured product session

THREE WAYS INTO THIS COPILOT GUIDE

Choose Where to Start With Copilot

THIS GUIDE · UI DESIGN

Build a Product Interface With Copilot

This guide: brief, references, design rules and a reviewed HTML result.

Read this guide SETUP

Set Up Copilot From Zero

Here is the full path from a clean machine to a Copilot CLI that can build and verify UI.

Go to setup COMPARISON

Compare Copilot With Other Agents

How Copilot differs from Codex, Claude Code, Cursor for design work, and when to choose another workflow.

See the comparison
On This Page Example
  1. Example
  2. Fit
  3. Compatibility
  4. Setup
  5. Workflow
  6. Resources
  7. Limitations
  8. FAQ

One Complete Copilot Design Task

A Copilot Design Task, From Brief to Interface

A single task, shown end to end: the brief and constraints you hand over, the artifact that comes back, and the checks you still run before it is done. The interface below is an illustrative example built for this page, not a recorded Copilot run.

1Design Brief and Constraints

Brief

Design the launch landing page for a CLI product from the attached screenshot of a competitor page: hero with install command, three feature blocks and proof points. Reuse the repository’s components. Desktop and phone.

  • Design systemRepository components and tokens; Albert Sans, one green accent
  • Breakpoints1440px desktop and 390px mobile, no horizontal scroll
  • InteractionsCopy install command, primary and secondary CTA, anchor navigation
  • OutputOne self-contained HTML file with stable data-od-id hooks

2Division of Work: You, Copilot and OpenDesign

  • You

    Write the brief, select the design system and define the acceptance criteria.

  • Copilot

    Plans the layout, writes the HTML, CSS and JavaScript and revises it on request.

  • OpenDesign

    Provides the design system and skill, renders the preview and stores every version as a file in the project.

  • Review

    Visual hierarchy, spacing on the 8px grid, both breakpoints and every interaction are checked before handoff.

3Copilot Artifact: The Launch Page at 1440px and 390px

Copilot Artifact: The Launch Page at 1440px and 390px — Desktop
Illustrative example

4Review Before Handoff

Layout

Grid and Spacing

Hero, features and proof share the 8px grid; the art column never pushes the copy below the fold.

Hierarchy

Visual Hierarchy

Headline, install command, then features; the accent marks the install button only.

Responsive

Mobile Layout

Copy first, art second, features stacked; the install command stays copyable.

Interaction

Interaction Checks

Copy the command, follow both CTAs, jump to a feature anchor.

Fit

When Copilot Fits the Task, and When It Does Not

Copilot Fits When

  • Screenshot → UI. Pick a strong multimodal model and turn a reference image into responsive markup, then check the result against it.
  • Multi-model choice. Switch among frontier models from Anthropic, OpenAI, and Google per task with /model, all on your Copilot subscription.
  • Instructions + MCP. Custom instructions and AGENTS.md carry your conventions; the Figma MCP server brings real design context into code.
  • Deep GitHub integration. Built-in GitHub MCP server and access to your repos, issues, and PRs, authenticated with your existing GitHub account.

Choose Another Workflow When

  • You need editable vector files. The artifact is HTML, not an editable design document. Check a separate vector workflow for your required asset format.
  • You have no reference and no constraints. Without a design system or examples the output tends toward a generic look; write the brief first.
  • You do not have the credential this agent needs. Required: GitHub Copilot subscription. OpenDesign does not provide or proxy credentials.
  • Your team works in Codex or Claude Code. Those agents have their own pages; the workspace is the same, the setup differs. See related agents.

Compatibility

Copilot Requirements Before You Start

This guide covers Copilot as connected through the OpenDesign desktop app. Published references checked on 6 September 2026.

Tool ScopeCopilot, by GitHub

GitHub Copilot CLI is GitHub's terminal-native coding agent, powered by the same agentic harness as Copilot coding agent. It reads your codebase, edits files, runs commands, and works with your GitHub issues, PRs, and repositories. This page is about designing interfaces with Copilot through OpenDesign, not about Copilot’s own interface. OpenDesign’s setup notes list the available agents.

Accounts and AuthenticationGitHub Copilot subscription

GitHub Copilot subscription. Authenticate with your GitHub Copilot subscription — credentials stay on your machine. This page does not promise a quota or price.

System and VersionsDesktop app or source

Check the download page for desktop builds. The Node.js and pnpm requirements in the source quickstart apply to running from source, not to installing a desktop package. Minimum compatible Copilot version: not verified here.

Connection CheckThe success signal

Follow the connection instructions shown by your installed version, then run a small task. Confirm that Copilot handled it and that the artifact opens. A download alone does not establish a working connection.

Start with the desktop app

Copilot Setup in Three Steps

Download first, complete the Copilot setup for your installed version, then check a small result. You do not need to build OpenDesign from source to follow this path.

  1. 1

    Download the OpenDesign Desktop App

    Choose the package for your computer, install it and open the app.

    Download OpenDesign
    CHECKPOINT
    The desktop app opens. Already installed? Move to the next step; there is no need to download again.
  2. 2

    Prepare Your Copilot Connection

    Follow the Copilot instructions in your installed version. Authenticate with your GitHub Copilot subscription — credentials stay on your machine.

    Using GitHub Copilot CLI 
    # 1. Install Copilot CLI (Node.js required)
npm install -g @github/copilot

# 2. Start it in your project and authenticate on first run
cd your-project
copilot           # run /login and follow the prompts to sign in

    From the Copilot setup notes in the published guide; check the vendor documentation for the current command.

    CHECKPOINT
    Confirm the intended agent and account. If it is unavailable, check compatibility before trying a larger task.
  3. 3

    Run One Small Copilot Task

    Use a small brief so you can judge the whole loop, including one revision.

    Starter brief

    Build a settings screen with a profile form and a save confirmation. Use my design rules. Check it at desktop and mobile widths.

    CHECKPOINT
    Open the result, test the save state and request one specific change. A generated file is the beginning of review, not the end.

To run OpenDesign from source, follow the technical quickstart instead.

The Copilot design workflow

The Copilot Design Workflow in Five Steps

The same launch page task, followed from brief to verified file. Each step lists what you provide, what Copilot does, what OpenDesign contributes and what you check.

  1. 1

    Design Brief

    Plain language, three to six lines. Name the audience, the job of the screen and the platforms.

    • YouWrite the brief; attach a reference screenshot if you have one.
    • CopilotReads the brief and the project’s instruction file; asks when something is ambiguous.
    • OpenDesignProvides the project, the prompt surface and the skill for the artifact type.
    • CheckConfirm the brief states the acceptance criteria. Adding them now is cheaper than after generation.
  2. 2

    Design Constraints

    A design system and a few hard rules. This is what separates on-brand output from a generic look.

    • YouPick a design system; state breakpoints and any must-use components.
    • CopilotLoads the DESIGN.md tokens and posture rules into context before writing a line.
    • OpenDesignShips the design-system library and binds the chosen one into the skill template.
    • CheckThe tokens match your brand. One accent, the right fonts, the right radius.
  3. 3

    Generate the Interface

    Copilot writes a self-contained HTML file: layout, styles, interactions and stable hooks.

    • YouWait, or answer a clarifying question. Nothing to configure.
    • CopilotPlans the sections, writes the HTML, CSS and JavaScript, runs the file and fixes what fails.
    • OpenDesignSaves the artifact into the project folder and indexes it for preview.
    • CheckNothing yet. Judge the file after it is rendered, not from the source.
  4. 4

    Preview

    The file renders inside OpenDesign at the widths you asked for. This is where the design is judged.

    • YouSwitch widths, click through the interactions, leave comments on elements.
    • CopilotReads your comments on the preview and prepares the next revision.
    • OpenDesignRenders the preview, exposes data-od-id targets for comments and edits.
    • CheckHierarchy, contrast, overflow at 390px, focus states, and whether the accent is used sparingly.
  5. 5

    Revise and Verify

    Request changes by pointing at elements in the preview. Every revision is a new file; nothing is overwritten silently.

    • YouTurn comments into requests; decide when the task is done.
    • CopilotApplies the changes in place and re-runs the file.
    • OpenDesignKeeps versions side by side; exports an image or the HTML when you are done.
    • CheckRe-check only the area that changed, then the whole page once at each breakpoint.

Resources

Copilot Design Resources

Skills

Design Skills

The artifact types Copilot can produce in OpenDesign, one skill per type.

Browse skills Design systems

Design Systems

Brand tokens and components to bind before Copilot generates anything.

Browse systems Templates

Templates

Starting points for decks, landing pages and product screens.

Browse templates

Limitations

Copilot Limitations, Manual Checks and Fallbacks

  • ScopeIt reads custom instruction files and AGENTS.md automatically, and lets you switch among frontier models from Anthropic, OpenAI, and Google per task. This page covers Copilot as an agent connected to OpenDesign, not every Copilot feature.
  • Usage LimitsUsage limits and cost follow the credential you use (GitHub Copilot subscription). This page makes no claim about free quotas.
  • NetworkLocal project files do not mean offline inference. Review your agent’s provider settings and data policies before sharing sensitive inputs.
  • Output Is HTMLArtifacts are HTML files, not vector design files.
  • Manual ReviewAccessibility, real content, brand fit and interaction correctness are reviewed by you in the preview. Treat any self-check by the agent as a first pass.
  • FallbackIf the agent is unavailable or a task fails, check the installed version’s connection instructions and authentication. Preserve the error and the last working artifact before changing configuration.

FAQ

Common Questions About Copilot and OpenDesign

Can GitHub Copilot CLI Really Do Design Work?
Yes — with an aesthetic skill, a design system, and real reference images in context, Copilot CLI produces production-quality, responsive UI, and you can pick the model that verifies output best against references. Without that context it tends to default to a generic look, which is the gap OpenDesign fills.
Do I Need a Subscription to Design With Copilot CLI?
Yes — Copilot CLI runs on an active GitHub Copilot subscription (Pro, Pro+, Business, or Enterprise); it is not bring-your-own-key. You authenticate with your GitHub account. OpenDesign never proxies your credentials — your subscription is used directly by your agent.
What Makes Copilot CLI Good for Design Specifically?
Two things: it reads repository instructions and AGENTS.md automatically, so your design conventions travel with the repo; and it lets you switch among frontier models from Anthropic, OpenAI, and Google per task. Both help — but taste still comes from the design system, skill, and references you supply.
Copilot CLI or Claude Code for Frontend Design?
Both are strong. Claude Code is known for specific, codebase-aware design decisions; Copilot CLI's edge is model choice across providers and deep GitHub integration on a subscription you may already have. Many teams use both — OpenDesign lets you switch agents without changing your design workflow.
How Do I Connect Copilot CLI to Figma?
Add the Figma MCP server with the /mcp add command; settings are stored in mcp-config.json under ~/.copilot. Copilot can then pull real design context — components, variables, layout data — so the generated code matches the source instead of approximating it.

Start a First Design Task With Copilot

Start with a small task, judge the round trip, then bring the real brief. Choose the option that matches your setup; the page does not detect it.

Where are you in the setup?
Download OpenDesign See the setup checklist

OpenDesign Desktop

One design system. Every output unmistakably your brand

Inside the full Vibe Design Workspace, use the same brand rules across websites, slide decks, interactive prototypes, dashboards, images, and HTML video. Connect Codex, Claude Code, Cursor, and other coding agents already on your computer, then create locally for free.

  • Web, slides, prototypes, dashboards, images, and video
  • 140+ design systems, plus the full template and skill library
  • Connect local Codex and 21+ coding agents · Free to use
Download free

Available for macOS and Windows