Public-facing entry point for learning-with-court workshops. Provides @setup-workshop to clone a workshop's project codebase via the locally-installed `lwc` CLI, infers and confirms a workshop pace (slow/balanced/quick), then writes a per-clone config. Requires the CLI to be installed first (one-line installer at https://workshop.institute/install.sh).
npx claudepluginhub learning-with-court/learning-with-court --plugin learning-with-courtLive survey of all repos, feature backlog, and API health. Use at the start of a working session or any time you want the full project picture.
Use this when the user wants to start a learning-with-court workshop they don't have set up yet — phrases like "I'd like to learn how to build an MCP server", "I want to learn MCP", "teach me MCP", "help me get started", "set up a workshop", "start a workshop", "let's start the mcp workshop", "begin the lwc workshop", or any "I'd like to learn <topic>" / "I want to learn how to <build X>" phrasing where <topic> matches an available workshop. Drives the clone of the workshop's project codebase via the @learning-with-court/cli into a folder under the user's working directory (or `~/learning-with-court/` by default) and tells the user how to start a fresh session there. Do NOT use this if the user is already inside a workshop project (look for a .mcp.json with an `lwc-*` server entry — they're already set up).
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimPermanent coding companion for Claude Code — survives any update. MCP-based terminal pet with ASCII art, stats, reactions, and personality.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
UI/UX design intelligence. 67 styles, 161 palettes, 57 font pairings, 25 charts, 15 stacks (React, Next.js, Vue, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Nuxt, Jetpack Compose). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
This skill should be used when users need to generate ideas, explore creative solutions, or systematically brainstorm approaches to problems. Use when users request help with ideation, content planning, product features, marketing campaigns, strategic planning, creative writing, or any task requiring structured idea generation. The skill provides 30+ research-validated prompt patterns across 14 categories with exact templates, success metrics, and domain-specific applications.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Comprehensive startup business analysis with market sizing (TAM/SAM/SOM), financial modeling, team planning, and strategic research
Hosted-MCP workshops driven by Claude Code.
Start here: https://workshop.institute — sign up free, then come back for the install steps below.
0. Open a terminal in a folder you want to use for workshops, e.g.:
macOS / Linux / WSL: mkdir -p ~/workshops && cd ~/workshops
Windows PowerShell: mkdir $HOME\workshops; cd $HOME\workshops
Any folder works — this becomes the parent for everything you install.
1. Start Claude Code there: claude
2. Type: /plugin marketplace add learning-with-court/learning-with-court
3. Type: /plugin install learning-with-court@learning-with-court
4. Type: /reload-plugins
5. Tell Claude: set up the mcp workshop
That's the whole guide. Claude takes it from there — checks your tools, runs npx @learning-with-court/cli setup mcp-workshop --dir <your-folder>/mcp-workshop, opens a browser for one-time sign-in, clones the workshop into <your-folder>/mcp-workshop/ (or ~/learning-with-court/mcp-workshop/ if you skipped step 0), and hands you off to a fresh Claude Code session inside.
The plugin installs at user scope by default, so once you've done steps 1-4 you don't need to do them again — additional workshops only need step 5.
npx and git. Use nvm if you need to upgrade.That's it. No gh CLI, no GitHub account, no pnpm install up front. The CLI handles everything; first run prompts a browser sign-in.
| Workshop | What you build |
|---|---|
| mcp-workshop | Build a real MCP server. 13 lessons across 3 phases (A: stdio basics; B: auth + HTTP; C: AWS deploy). |
Workshop project repos are private and gated by your workshop.institute sign-in — the CLI handles cloning via short-lived GitHub App tokens. More workshops land here over time.
The marketplace plugin is Claude Code-specific, but the underlying CLI is agent-agnostic. From any terminal:
npx -y @learning-with-court/cli@latest setup mcp-workshop
Add --dir <path> if you want it somewhere specific. Then cd into the cloned folder (the CLI prints the exact path) and open it in your agent. The cloned .mcp.json wires up the workshop server identically for any MCP-capable agent.
The first time you run claude inside a workshop project and the workshop tries to do anything, Claude Code will open a browser to sign you in. You'll either sign into an existing workshop.institute account or create one (sign-up is free).
After sign-in, your JWT is cached locally. Subsequent sessions skip the browser dance until the token expires (typically hours-to-days). If a session needs to re-authenticate, you'll see the browser open again — that's expected.
Your authenticated identity keys your workshop progress on the server. Sign in on a different machine with the same workshop.institute account, and your progress is preserved.
pnpm install yourself once you cd in. Claude Code's auto-mode classifier blocks pnpm install from any context (lifecycle scripts run arbitrary code).plugin/ — the Claude Code plugin. Provides @setup-workshop..claude-plugin/marketplace.json — marketplace metadata.docs/ — design docs (VISION, ARCHITECTURE, REFERENCE_PROJECTS, ROADMAP). Not required reading to start a workshop.A workshop is split in two: content (lessons, walker prose, rubrics) lives on a deployed MCP server we host; code (the codebase you edit) lives in a per-workshop project repo you clone once. The plugin in this repo handles the clone-and-wire-up step. The project ships with its own .mcp.json and .claude/settings.json, so once you cd into it and run claude, the workshop greets you and walks the lessons. Server-side state means your progress survives across machines and sessions.
Live. One workshop in the catalog (mcp-workshop). Both dev and prod environments are deployed:
| Env | Workshop API | Landing |
|---|---|---|
| Prod | mcp.workshop.institute | workshop.institute |
| Dev | mcp-dev.workshop.institute | dev.workshop.institute |
Clerk auth is live on both envs — multi-tenant, per-user identity keying server-side progress. The project repo's .mcp.json defaults to prod. E2E content validation (walking lesson 1 as a real learner) is the next open item.