generate-chat-background
Generate or design an image for the chat background in the Agents window. Use when the user asks for a generated chat background, wallpaper, pattern, or illustration to decorate their chat.
- License 许可
- MIT
- 所属仓库
- microsoft/vscode
- 最近更新
- 2026-11-11
- Stars
- ★ 20w
- Forks
- 4.4w
01 前言 Front Matter
- name
- generate-chat-background
- description
- Generate or design an image for the chat background in the Agents window. Use when the user asks for a generated chat background, wallpaper, pattern, or illustration to decorate their chat.
02 资源文件 3
- 参考文档agents/openai.yaml102 B
- 参考文档DEEPENING.md2.5 KB
- 参考文档DESIGN-IT-TWICE.md2.6 KB
03 SKILL.md 正文
<!-- Copyright (c) Microsoft Corporation. All rights reserved. Licensed under the MIT License. --> <!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. -->
Generate Chat Background
Generate an image and apply it as the chat background with setChatBackground. The user's requested subject, style, and colors take priority over the guidance below.
If the user only wants to apply an existing image, change the layout, use Codicons, or remove the background, call setChatBackground directly. Do not generate an image unless asked.
Generate and apply
- If
setChatBackgroundor an image-generation tool is unavailable, explain that rather than generating an image you cannot apply. - Call
getThemeColorsand use the palette as context for the image, not as a limit on the user's colors. - Design for the chat: messages and the input cover the center, so keep interesting detail toward the edges and keep contrast low enough for text to stay readable. For a pattern, generate a seamless tile with small, spaced motifs.
- Save the image to a file in your working or scratch directory and pass its path to
setChatBackground. If it fails, report the error and fix the input.
Choose the layout:
repeattiles the image at its original size. Resize the tile first if its motifs are too large or too small.stretchfills the chat but can distort the image.centerand the edge or corner layouts show the image once at its original size. An opaque image can show its own ground as a visible rectangle.
Check the result
After setChatBackground succeeds, call screenshotWindow and check that the subject is visible around the chat, the image blends in without seams or patches, motifs have a good size, and the conversation stays readable. Fix specific problems by adjusting the layout or tile size or by regenerating, for at most a couple of rounds.
The screenshot shows only the current view. Do not navigate the interface to capture other states, and do not comment on unrelated content in the screenshot.
If you could not check a screenshot, say that the result was not visually verified. High contrast themes hide chat backgrounds; mention this when it applies.
Tell the user what you applied and with which layout.
04 同仓库更多 Skills
sweeper-query
Answer natural-language questions about the VS Code Sweeper's published issue index (index-<name>.json for microsoft/vscode and the enrolled family repos) — which issues are agent-ready to implement or plan, what the sweeper proposed for an assignee or area, whether the sweeper knows a report as a duplicate, the highest-value open bugs in a lane — and, for one issue, the review's full record (evidence with file citations, fix brief, proposed comment). Use ONLY when the request explicitly names the sweeper — "sweeper", "vscodesweeper", "sweeper-query", a sweeper verdict, record, brief or index, an agent-ready issue — or asks what "the sweeper" found, proposed or knows. Do NOT use for general questions about issues, duplicates, priorities or ranking that do not mention the sweeper. Read-only; discovery only.
update-skills
Create or update repository skills and instructions when major learnings are discovered during a session. Use when the user says "learn!", when a significant pattern or pitfall is identified, or when reusable domain knowledge should be captured for future sessions.
update-pr
Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.
sync
Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.
sync-upstream
Update a stale session branch by rebasing onto the latest origin. Use when the upstream has moved significantly and the session needs to catch up, resolving conflicts by preserving upstream changes and adapting session work to fit.
merge
Merge changes from the topic branch to the merge base branch. Use when the user wants to merge their session's work back to the base branch.