Amy’s weekly design updates
Amy’s weekly report is the best way to understand current status. It shows the development owner, recent decisions, useful links, and project history from July onward.
Product and engineering partners.
Core PM partners
Core engineering partners
Collaboration and prototyping.
How the team collaborates
- Work across time zones — Most of the team is based in Shanghai, so async Q&A and follow-up reviews help work move forward.
- Meet live when useful — Amy joins evening sessions for larger meetings, kickoffs, and design reviews.
How Amy creates prototypes
- Figma — Quick, small-scope features, early concepts, and fit-and-finish notes. VS Code · GitHub Copilot app.
- Main production repo — Small features, UI improvements, and fit-and-finish work that can merge directly into production. VS Code · GitHub Copilot app.
- Coded prototypes — Larger end-to-end flow explorations with more complex interactions and many variants. VS Code examples · GitHub Copilot app examples.
Key references.
WIP PM strategy for the rest of the year.
How planning works today.
Execution plan, ownership, status, and deadlines.
*Paulo is working on involving design earlier.
Foundry Toolkit for VS Code.
- Amy was the extension’s sole design support from 2025 through July 2026.
- Jaeyong joined the work in July 2026.
Two extensions became one.
The original language-agnostic VS Code toolkit reached general availability without Microsoft branding.
A separate extension added Foundry project and deployment workflows.
Single extension, shared repository
AI Toolkit and AI Foundry were packaged as one extension and brought into the same repository under the Foundry name.
The codebases still live in two large top-level folders, so this was repository consolidation rather than a full architectural merge.Copilot-Driven. Code-First. Built for Pro Devs.
Designing for VS Code extensions.
Why the UI system started.
The official toolkit was deprecated
VS Code extensions no longer had an official UI component system.
Two teams were solving the same problem separately
Because Fluent did not look like VS Code, each extension team built its own CSS overrides. Once packaged together, those separate approaches made the combined extension feel even less consistent.
Designing and coding a shared layer
Amy decided to design and code a component layer that makes Fluent feel native to VS Code, collaborating with Hui as the engineering reviewer.
Basic components are published
New extension features already use these components, and we have started replacing them in some older features.
The remaining legacy cleanup and system iteration will continue as resources allow.Resources
Published npm package.
Source repository.
Shared component specifications for vsc-ui-react.
VS Code resources.
Repositories
Send Kai Yang your GitHub ID to request Skylight access.
microsoft/SkylightPrivatePrimary production source. Access is required before implementation.
Packaged artifacts and releases, not the complete development source.
Design file
Primary VS Code design file for early exploration and fit-and-finish notes.
Prototypes
Foundry in the GitHub Copilot app.
- Work started in June 2026.
- Amy is the design owner.
Two canvas page examples so far.
Canvas uses Fluent as its design system.
Guided setup + Agent Playground
A guided setup view paired with a dynamic canvas for building and testing an agent.
Canvas could support more distinctive UI, such as an agent catalog.
GitHub Copilot app resources.
Repository
Send Kai Yang your GitHub ID to request Skylight access.
microsoft-foundry-canvasPrivateSource folder in Skylight.
Design file
Primary GitHub Copilot app design file.
Prototypes
Intent-driven creation and Managed Agent explorations.
Loading, skipped, resolve, resolved, and all-passed states.