Training course · GitHub Copilot · UX Design & Prototyping

GitHub Copilot for UX Designers

Use GitHub Copilot professionally: completions, chat, agent mode, the coding agent for issues and PRs, code review and enterprise policies.

Duration
2 days (14 hrs)
Format
Online or on-site
Language
German or English
Participants
open dates or exclusive for your team
Certificate
Certificate of attendance

Overview

“GitHub Copilot for UX Designers” is a hands-on course for roles such as UX and UI designers, Product designers and interaction designers and UX researchers who want to test variants quickly. Rather than learning GitHub Copilot in the abstract, you work on tasks from your daily routine – with examples, exercises and templates from UX Design & Prototyping.

GitHub Copilot has grown from simple code completion into a broad AI platform that supports the entire development lifecycle. In the editor you work with inline suggestions, next edit suggestions and Copilot Chat; in agent mode Copilot handles tasks across multiple files and runs commands. On GitHub itself, the coding agent picks up assigned issues and delivers pull requests. In this two-day course you will learn how to use each of these building blocks deliberately and fit them cleanly into your existing development process.

Beyond hands-on editor work, the course covers control and quality. Custom instructions and prompt files give Copilot the project knowledge it needs, MCP adds further tools, and Copilot code review complements human reviewers. For those responsible for teams and organisations, we look at policies at organisation and enterprise level, content exclusions, model availability and usage reporting. Together, these lay the groundwork for a secure, transparent and genuinely effective Copilot rollout across the entire company.

AI coding tools are shifting the boundary between design and development: UX designers can now build interactive prototypes in real code instead of only drawing clickable mock-ups. A screenshot, a sketch or a short description quickly becomes a working interface with real states, form logic and sample data that feels like a finished product in usability testing. AI assistants also translate design tokens, component libraries and accessibility checks straight into code. In this course you learn how vibe coding and AI agents take you from idea to testable prototype faster, how to hand results over cleanly to engineering teams and where the line runs between a prototype and production-ready software.

The course is delivered live – either online in a virtual classroom or on-site in our training rooms in Munich, Salzburg, Berlin, Augsburg, Hanover, Bremen, Stuttgart and Kaiserslautern. We can also run it exclusively for your team.

Who is this course for?

  • UX and UI designers
  • Product designers and interaction designers
  • UX researchers who want to test variants quickly
  • Product owners and product managers with design responsibility
  • Design system teams working closely with frontend engineering

Typical challenges we address

  • Static mock-ups barely capture interactions, states and real data
  • Hand-offs to engineering lose details, spacing and behavioural logic
  • Long waits for engineering capacity to run experiments and A/B variants
  • Accessibility is often considered late and incompletely

What you will be able to do

  • You use Copilot completions, chat and agent mode purposefully for your everyday development tasks.
  • You capture project knowledge in custom instructions and prompt files to improve output quality.
  • You delegate suitable issues to the coding agent and review its pull requests properly.
  • You integrate Copilot code review sensibly into your existing review process.
  • Build interactive, code-based prototypes with AI and test ideas with users much earlier.
  • Translate design systems and tokens into code and improve hand-offs to engineering teams.
  • Review prototypes systematically for accessibility and understand the line between prototype and production code.

Course outline

Day 1

Module 1 Copilot in the editor: completions and chat
  • Accepting, rejecting and steering inline and next edit suggestions efficiently
  • Using Copilot Chat for explanations, debugging and test generation
  • Setting context precisely with files, selections, workspace and chat variables
  • Model selection and differences between VS Code, Visual Studio and JetBrains IDEs
Module 2 Agent mode and extensions
  • Planning multi-step tasks in agent mode and executing them under control
  • Feeding terminal commands, test runs and error output into the agent loop
  • Connecting MCP servers for additional tools and data sources
  • Reviewing changes, accepting them partially or rolling them back
Module 3 Project knowledge through custom instructions
  • Writing repository-wide instructions on architecture, style and testing
  • Creating path-specific instructions and reusable prompt files
  • Combining personal and organisation-wide guidance sensibly
  • Refining instructions continuously based on output quality
Module 4 Coding agent and code review on GitHub
  • Writing issues the coding agent can implement reliably
  • Reviewing, commenting on and iterating over the agent’s pull requests
  • Using Copilot code review as an additional check in the PR process
  • Configuring the agent’s development environment with setup steps and Actions

Day 2

Module 5 Administration, policies and security
  • Licence assignment and policies at organisation and enterprise level
  • Content exclusions, model availability and public code filters
  • Using audit logs and usage metrics to steer adoption
  • Clarifying security risks, secrets and accountability for AI-generated code
Module 6 Practice lab: UX Design & Prototyping
  • Clickable prototypes in code
  • Generating test variants
  • Turning design tokens into code
  • Checking accessibility
  • Designing microinteractions
  • Synthesising research
Module 7 Data protection, quality & transfer to daily work
  • Prototypes often contain unreleased product ideas and research data from participants: you learn to pseudonymise interview notes in line with the GDPR, clarify rights to fonts, images and generated assets and plan early for the European Accessibility Act.
  • Ground rules for safe AI use in your team
  • Checking results: facts, sources, tests and the four-eyes principle
  • Personal action plan for the next 30 days
  • Open questions, outlook and resources for further learning

Practical scenarios from your field

Clickable prototypes in code

Turn sketches, wireframes or screenshots into working web prototypes with navigation, form validation, loading and error states and realistic sample data that can be tested directly in the browser.

Generating test variants

Produce several design variants of a flow in parallel, for example onboarding or checkout, and prepare them for usability tests or A/B experiments with minimal adjustments.

Turning design tokens into code

Structure colours, typography, spacing and radii from your design system as tokens and convert them into CSS variables, Tailwind configuration or theme files for component libraries.

Checking accessibility

Examine prototypes for contrast, semantic HTML, keyboard navigation, focus order and ARIA attributes and have concrete WCAG-based improvements applied directly in the code. Issues are fixed before reaching engineering.

Designing microinteractions

Describe transitions, animations and feedback states and implement them in CSS or JavaScript, so you can judge timing and effect early in the real medium rather than in a drawing tool.

Synthesising research

Cluster notes from interviews and usability tests, surface patterns and pain points and derive prioritised design hypotheses that feed straight into the next prototype iteration.

Possible hands-on projects

Onboarding prototype

A multi-step onboarding flow as a web app with a progress indicator, validation and saved inputs, ready for moderated usability testing.

Token converter

A small tool that reads exported design tokens and generates CSS variables, a colour palette with contrast ratios and a preview page.

Component playground

An overview page showing your design system’s buttons, forms and cards in every state, including light and dark mode. It doubles as a living reference.

Prerequisites

You develop software regularly, work with Git and GitHub issues and pull requests, and use a modern IDE. You have experience in UX or UI design and with common design tools; no programming skills are required, although a basic understanding of HTML and CSS helps.

Technical requirements

Your own laptop with VS Code or a JetBrains IDE, the Copilot extension installed and a GitHub account with an active Copilot licence; the coding agent requires a suitable plan.

Data protection & compliance

Prototypes often contain unreleased product ideas and research data from participants: you learn to pseudonymise interview notes in line with the GDPR, clarify rights to fonts, images and generated assets and plan early for the European Accessibility Act.

Suggested dates

All dates are suggestions – your preferred date is always possible.

  • Mon, 23 November 2026 – Tue, 24 November 2026 Online Request
  • Wed, 2 December 2026 – Thu, 3 December 2026 Kaiserslautern Request
  • Tue, 8 December 2026 – Wed, 9 December 2026 Online Request
  • Thu, 14 January 2027 – Fri, 15 January 2027 Augsburg Request
  • Wed, 27 January 2027 – Thu, 28 January 2027 Online Request
  • Tue, 9 February 2027 – Wed, 10 February 2027 Salzburg Request

Frequently asked questions

What is the difference between agent mode and the coding agent?

Agent mode runs inside your IDE: you work interactively with Copilot, see every step and approve commands. The coding agent, by contrast, works autonomously on GitHub once you assign it an issue, uses its own execution environment and opens a pull request that you then review just as you would a contribution from a colleague.

How can we make sure Copilot complies with our company policies?

At organisation and enterprise level you can enable or block specific features, models and extensions. Content exclusions keep sensitive files out of the context, and audit logs make usage traceable. During the course we show how to align these controls with data protection, information security requirements and your internal coding standards.

Is the course worthwhile if we already use Copilot?

Yes, especially then. Many teams rely on completions alone and barely touch chat, agent mode, custom instructions or the coding agent. The course shows how to use these features in a structured way, improve results with project knowledge and avoid common pitfalls. Experienced users benefit most from the sections on review and governance.

Do I need to know how to code as a designer?

No. You describe interfaces and behaviour in plain language, with sketches or screenshots, and the AI tool generates the code. It helps to understand basic terms such as component, state or CSS class so you can steer precisely. We cover these concepts hands-on in the course, so you can adapt and evolve prototypes on your own.

Can the engineering team reuse the prototype code?

Sometimes, but more often it serves as a precise specification. Prototypes are optimised for speed, not for security, performance or maintainability. If you use the same component library and tokens as the product from the outset, reuse becomes much more likely. In the course you work out how to design hand-offs that benefit both sides.

How much does “GitHub Copilot for UX Designers” cost?

The course costs a flat €949 plus VAT per participant – whether online or on-site. This includes 2 training day(s) with a live trainer, course materials, a lab environment and a certificate of attendance.

Can I suggest my own date?

Yes. Our suggested dates are just a guide. In the request form you can always describe your preferred date or period in free text – we check availability and confirm within one working day.

Is the course online or on-site?

Both are possible: live online in a virtual classroom or on-site in Munich, Salzburg, Berlin, Augsburg, Hanover, Bremen, Stuttgart or Kaiserslautern. We can also run the course exclusively for your team.

More courses for UX Designers

More GitHub Copilot courses

All 32 GitHub Copilot courses

GitHub Copilot · MunichGitHub Copilot · SalzburgGitHub Copilot · BerlinGitHub Copilot · AugsburgGitHub Copilot · HanoverGitHub Copilot · BremenGitHub Copilot · StuttgartGitHub Copilot · KaiserslauternGitHub Copilot · Online