vscode-peacock
Copilot instructions1.2k starsChanged 2 months agoMITView on GitHub
VS Code extension written in TypeScript, bundled with Webpack, published to the VS Code Marketplace.
- Reads credentials
Trending
More talk lately.about the whole repository
Who's talking about johnpapa/vscode-peacock
- microsoft/vscode-remote-release“Remote: Iteration Plan for July 2019”GitHub · Jul 5, 2019 · 7 reactions
- A Hacker News story“Visual Studio Code: Peacock”Hacker News · May 3, 2021 · 4 points
- forem/forem“Embed GitHub Code”GitHub · Mar 12, 2019 · 4 reactions
- @hejchristian.com“Desperately needed to install this Peacock extension today, as I find myself with three different projects …”Bluesky · Mar 21, 2026 · 2 likes
- zed-industries/zed“Allow per-project (worktree) theme overrides for Peacock-style window tinting”GitHub · May 20, 2026 · 1 reactions
The biggest 5 of 18 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 18
Talked about on GitHub, Hacker News, Bluesky and Stack Overflow (18 times).
On GitHub · 15
- Jul 5, 2019Remote: Iteration Plan for July 2019 — microsoft/vscode-remote-release7 reactions
- Mar 12, 2019Embed GitHub Code — forem/forem4 reactions · 16 comments
- May 20, 2026Allow per-project (worktree) theme overrides for Peacock-style window tinting — zed-industries/zed1 reaction
- Oct 31, 2019Improve Onboarding — Kruemelkatze/vscode-dashboard1 reaction · 6 comments
- Oct 23, 2026Multiple BOBs when more than 1 window is open — EricKhmel/BobPet0 reactions
10 more on GitHub
- Sep 17, 2026Modern UI doesn't work with Peacock extension — posit-dev/positron0 reactions · 3 comments
- Aug 4, 2026ModernUI breaks custom theming — bojordan/ColorIdentity0 reactions
- Mar 21, 2026feat: Kunterbunt – automated workspace color extension for VS Code — martinus/vsode-extension-kunterbunt0 reactions
- Sep 13, 2023Add Code of conduct — thoroc/projen-typescript-git-hooks0 reactions
- Apr 19, 2023devcontainer creation fails when project is empty — microsoft/vscode-remote-release0 reactions · 2 comments
- Sep 22, 2020Peacock — coder/code-server0 reactions · 2 comments
- Nov 29, 2019Reach out to extensions to adopt new extension kind behaviour — microsoft/vscode0 reactions · 1 comment
- Nov 2, 2019https://github.com/johnpapa/vscode-peacock/commits — johnpapa/express-to-functions0 reactions · 2 comments
- Apr 30, 2019Integrate GitHub dependabot — SAP/spartacus0 reactions · 3 comments
- Mar 15, 2019Change Title Bar Color on Pair Swap — FordLabs/pairodoro0 reactions · 1 comment
On Hacker News · 1
- May 3, 2021Visual Studio Code: Peacock4 points
On Bluesky · 1
- Mar 21, 2026Desperately needed to install this Peacock extension today, as I find myself with three different projects open and no way to distinguish… — @hejchristian.com2 likes and reposts · 2 replies
On Stack Overflow · 1
- Dec 7, 2020VSCode different Theme setting for each project in a WorkSpace1 vote
The file
We split this copilot-instructions.md into the rules it gives an agent
12 rules. About 0 are common, 2 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use explicit types for function parameters and return values
- Very specific: line 11
Use import type for type-only imports
- Very specific: line 12
All source code lives in src/
- Very specific: line 16
Use vscode.commands.registerCommand() for command registration
- Very specific: line 17
Use vscode.workspace.getConfiguration('peacock') for reading settings
- Very specific: line 18
Use vscode.window.showQuickPick() and vscode.window.showInputBox() for user input
- Very specific: line 19
All commands must be declared in package.json under contributes.commands
- Very specific: line 20
All settings must be declared in package.json under contributes.configuration.properties
- Very specific: line 24
All color manipulation uses tinycolor2 via the helpers in src/color-library.ts
- Distinctive: line 25
Never manipulate hex strings directly — always go through the color library
- Very specific: line 32
Run unit tests: npm test
- Very specific: line 33
Run e2e tests: npm run test:e2e
≈ “Common” is an estimate: at least 1 in 5 of the 3,827 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Copilot Instructions — Peacock
Project Type
VS Code extension written in TypeScript, bundled with Webpack, published to the VS Code Marketplace.
TypeScript Conventions
- Strict mode enabled (
tsconfig.json) - Use explicit types for function parameters and return values
- Use
import typefor type-only imports - All source code lives in
src/
VS Code Extension Patterns
- Use
vscode.commands.registerCommand()for command registration - Use
vscode.workspace.getConfiguration('peacock')for reading settings - Use
vscode.window.showQuickPick()andvscode.window.showInputBox()for user input - All commands must be declared in
package.jsonundercontributes.commands - All settings must be declared in
package.jsonundercontributes.configuration.properties
Color Handling
- All color manipulation uses
tinycolor2via the helpers insrc/color-library.ts - Never manipulate hex strings directly — always go through the color library
- Colors are stored as hex strings (e.g.,
#ff0000) in VS Code configuration
Test Conventions
- Unit tests: Mocha + Sinon, located in
src/test/ - E2E tests: Playwright, located in
e2e/(primarily for docs screenshots) - Run unit tests:
npm test - Run e2e tests:
npm run test:e2e - Tests use
testworkspace/as the VS Code workspace - Every bug fix must include a regression test that fails without the fix and passes with it
- Every new feature must include unit tests covering the happy path and relevant edge cases
- Don't accept "this can't be tested" claims at face value. Grep
src/test/for the exactvscodeAPI/state the change depends on — if any existing suite already stubs it (host lane cansinon.stub(vscode.env, ...)), reuse that lane/pattern instead of skipping the test. See PR #757 for a worked example.
Code Style
- ESLint + Prettier (config in
.eslintrcand.prettierrc.js) - Husky pre-commit hook runs Prettier automatically
- Lint:
npm run lint - Fix:
npm run lint-fix
Maintenance Matrix
| When this changes... | Also update... |
| New command added | package.json (contributes.commands + menus), src/models/enums.ts (Commands enum), src/commands.ts, src/extension.ts (register), src/test/, docs/guide/, docs/changelog/README.md |
New StandardSettings setting added | package.json (contributes.configuration), src/models/enums.ts (StandardSettings enum), src/configuration/read-configuration.ts (add reader), src/test/, docs/guide/, docs/changelog/README.md |
New AffectedSettings setting added | package.json (contributes.configuration), src/models/enums.ts (AffectedSettings + ColorSettings enums), src/models/interfaces.ts (IPeacockAffectedElementSettings), src/configuration/read-configuration.ts (getAffectedElements + collect* function), src/configuration/update-configuration.ts (updateAffectedElements), src/test/suite/affected-elements.test.ts, docs/guide/, docs/changelog/README.md |
| Bug fix | src/test/ (add a regression test that fails without the fix), docs/changelog/README.md |
| Color application logic | src/apply-color.ts, src/color-library.ts, related unit tests |
| Live Share integration | src/live-share/, src/live-share/liveshare-commands.ts, package.json (vsls dependency), related tests, run npm run test-all |
| Remote features | src/remote/, related tests |
| Docs content | docs/ (update pages), docs/_sidebar.md (if new page), e2e/ (if screenshots change) |
| Dependencies updated | package.json, package-lock.json, verify webpack build, run full test suite |
| Version bump | package.json (version field only), docs/changelog/README.md |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

