Plugins for Claude Code, GitHub Copilot CLI (also usable in VS Code's Copilot harness), and Antigravity CLI: skills, agents, and MCP servers you can install into any project. Claude Code and Copilot CLI share one catalog; Antigravity CLI installs each plugin from its folder here.
1. Add the marketplace (once, from inside Claude Code):
/plugin marketplace add j0hanz/j0hanz-marketplace
2. Install a plugin. One command per plugin, so pick only what you need:
/plugin install tutor@j0hanz-marketplace
/plugin install css@j0hanz-marketplace
/plugin install frontend@j0hanz-marketplace
/plugin install mcp-hub@j0hanz-marketplace
/plugin install filesystem-mcp@j0hanz-marketplace
/plugin install review@j0hanz-marketplace
/plugin install prompt@j0hanz-marketplace
/plugin install workbench@j0hanz-marketplace
/plugin install output-styles@j0hanz-marketplace
/plugin install nodejs@j0hanz-marketplace
/plugin install typescript-pro@j0hanz-marketplace
/plugin install writeup@j0hanz-marketplace
/plugin install groundwork@j0hanz-marketplace
/plugin install telltale@j0hanz-marketplace
3. Use it. Check MCP server connections with /mcp, or type an invocable skill as a slash command, namespaced by plugin:
/tutor:teach
/css:css-audit
/review:code-quality-review
Or browse everything installed with /plugin. To remove one:
/plugin uninstall tutor@j0hanz-marketplace
Copilot CLI reads the same catalog (.claude-plugin/marketplace.json). From a shell, add the marketplace once, then install what you need:
copilot plugin marketplace add j0hanz/j0hanz-marketplace
copilot plugin install tutor@j0hanz-marketplace
copilot plugin install css@j0hanz-marketplace
copilot plugin install frontend@j0hanz-marketplace
copilot plugin install mcp-hub@j0hanz-marketplace
copilot plugin install filesystem-mcp@j0hanz-marketplace
copilot plugin install review@j0hanz-marketplace
copilot plugin install prompt@j0hanz-marketplace
copilot plugin install workbench@j0hanz-marketplace
copilot plugin install nodejs@j0hanz-marketplace
copilot plugin install typescript-pro@j0hanz-marketplace
copilot plugin install writeup@j0hanz-marketplace
copilot plugin install groundwork@j0hanz-marketplace
Check with copilot plugin list, or /skills and /agent inside a session. Copilot lists plugin skills by bare name (css-audit, not css:css-audit). Remove one with copilot plugin uninstall <name>.
Copilot cloud agent. It installs no plugins by default. A repository opts in through .github/copilot/settings.json, which Copilot CLI also reads (same entry shape as Claude Code's extraKnownMarketplaces):
{
"extraKnownMarketplaces": {
"j0hanz-marketplace": { "source": { "source": "github", "repo": "j0hanz/j0hanz-marketplace" } }
},
"enabledPlugins": { "css@j0hanz-marketplace": true }
}What differs under Copilot
output-stylesis Claude Code only: Copilot has no output styles.- Hooks detect the client and answer in its shape. Stop-time notes that Claude shows as a system message surface as a hook warning in Copilot.
- The Claude
UserPromptExpansionevent does not exist in Copilot, so typed-slash-command briefs fire throughPreToolUseon the skill tool instead.
VS Code's Copilot harness can use plugins from this marketplace. In VS Code, open Chat: Open Customizations, choose Browse > Configure Marketplaces > Add Marketplace, and add j0hanz/j0hanz-marketplace. Then browse and install the plugins you want.
Alternatively, install plugins with GitHub Copilot CLI as above; VS Code discovers those CLI-installed plugins automatically. This is another way to use the existing Copilot support, not a separate marketplace integration. Plugin components can vary by agent harness, so verify them in the VS Code Copilot session where you plan to use them.
Antigravity CLI reads no third-party catalog, so there is no marketplace to add: each plugin installs straight from its folder in this repo. From a shell:
agy plugin install https://github.com/j0hanz/j0hanz-marketplace/tree/main/plugins/frontend
agy plugin install https://github.com/j0hanz/j0hanz-marketplace/tree/main/plugins/mcp-hub
agy plugin install https://github.com/j0hanz/j0hanz-marketplace/tree/main/plugins/filesystem-mcp
agy plugin install https://github.com/j0hanz/j0hanz-marketplace/tree/main/plugins/review
agy plugin install https://github.com/j0hanz/j0hanz-marketplace/tree/main/plugins/prompt
agy plugin install https://github.com/j0hanz/j0hanz-marketplace/tree/main/plugins/nodejs
agy plugin install https://github.com/j0hanz/j0hanz-marketplace/tree/main/plugins/typescript-pro
agy plugin install https://github.com/j0hanz/j0hanz-marketplace/tree/main/plugins/writeup
agy plugin install https://github.com/j0hanz/j0hanz-marketplace/tree/main/plugins/groundwork
Check with agy plugin list, or /plugin inside a session. Skills run as slash commands namespaced by plugin, as in Claude Code (/review:code-quality-review). Remove one with /plugin uninstall <name>.
What differs under Antigravity
- Only the plugins above install there so far. Antigravity reads hooks, MCP servers and agent tool lists in its own formats, so a plugin that ships any of them waits until they are ported.
- Antigravity has no switch that keeps the model from picking a skill on its own, so skills that wait for their slash command in Claude Code (
disable-model-invocation) can also load unasked.
Teach one topic across many sessions: workspace, spaced repetition, offline HTML lessons sealed behind a retrieval quiz
- Commands:
/tutor:teach - Hooks:
SessionStart,Stop
Stops agents wrecking your CSS: refuses writes carrying provable defects, advises on performance and accessibility failures
- Commands:
/css:css-audit,/css:css-craft,/css:motion-craft - Hooks:
PreToolUse,PostToolUse,Stop,SessionStart
Designs and reviews frontend UI: invents art-directed page direction from a brief, shapes perceived wait with the right loading pattern, and audits UI code against web interface guidelines
- Commands:
/frontend:design,/frontend:guidelines,/frontend:wait - Hooks:
Stop
MCP development skills for TypeScript SDK v2
- Commands:
/mcp-hub:mcp-auth,/mcp-hub:mcp-client,/mcp-hub:mcp-elicitation,/mcp-hub:mcp-migration,/mcp-hub:mcp-resources,/mcp-hub:mcp-tools,/mcp-hub:mcp-transport
Project-scoped filesystem MCP tools for batched reads, RE2 search, diffs, and edits. Requires Node.js 24+
- MCP servers:
filesystem(stdio)
One strict behavior-preserving review of a diff: how the code reads, and how it is shaped
- Commands:
/review:code-quality-review
Rewrites a rough, half-formed prompt into one that works on current Claude models
- Commands:
/prompt:prompting
Every tool for the job on one bench: decide, research, spec, plan, build test-first, debug, refactor, review, audit, verify — plus authoring the skills, hooks and QA docs you reach for next
- Commands:
/workbench:architecture-audit,/workbench:bug-hunt,/workbench:clean-code,/workbench:diagnose,/workbench:frontier,/workbench:grilling,/workbench:handoff,/workbench:ideation,/workbench:init,/workbench:plan-hunt,/workbench:prototype,/workbench:qc,/workbench:refactor,/workbench:research,/workbench:run-plan,/workbench:spec-hunt,/workbench:tdd,/workbench:verify-specs,/workbench:write-adr,/workbench:write-hooks,/workbench:write-plan,/workbench:write-qa,/workbench:write-skills,/workbench:write-specs - Hooks:
PreToolUse,SessionStart,UserPromptSubmit,UserPromptExpansion,Stop
Set a global output style — Concise, TL;DR, Diagram-first, or Schematic — with /set-style <style> (Claude Code only)
- Commands:
/output-styles:set-style - Hooks:
UserPromptExpansion
Node.js backend conventions and implementation patterns: framework selection, layered architecture, fail-fast validation, pooled transactions, a single error envelope, graceful drain, plus security and production hardening checklists
- Commands:
/nodejs:nodejs-backend-patterns,/nodejs:nodejs-best-practices
TypeScript type system skills: type-level utilities and type tests, .d.ts declaration contracts for packages and untyped APIs, JSDoc type-checking for plain .js files, and tsconfig selection by runtime
- Commands:
/typescript-pro:advanced-types,/typescript-pro:declaration-contracts,/typescript-pro:jsdoc-types,/typescript-pro:tsconfig
PR descriptions, commit messages, issues and review comments written for people: plain prose, structural diagrams, slop caught before it publishes.
- Commands:
/writeup:commit,/writeup:issue,/writeup:pr,/writeup:review,/writeup:show-me,/writeup:unslop - Hooks:
PreToolUse,PostToolUse
The thinking before the code: relentless grilling of a plan, a domain model kept in GLOSSARY.md and ADRs, deep-module design vocabulary, architecture reviews that surface deepening opportunities, throwaway prototypes that settle a logic or layout question, and research against primary sources.
- Commands:
/groundwork:codebase-design,/groundwork:domain-modeling,/groundwork:grill-with-docs,/groundwork:grilling,/groundwork:improve-codebase-architecture,/groundwork:prototype,/groundwork:research
See how Claude uses your skills and MCP servers: a receipt under each answer, a pane of every tool call with what Claude read back and did next, context cost per server and skill, per-turn JSONL logs. Observe-only, local files only (Claude Code only)
Claude Code, GitHub Copilot CLI or Antigravity CLI, and nothing else. Plugins install from this repo with no build step and no dependencies.