So the app is essentially done here.
You could always add more features, change the styling,
whatever, but I'm quite happy with the current state
of this app. And throughout this course, we, of course, covered all these
core features Cloud Code has to offer, skills, agents,
commands, how to write prompts, plan mode, and so on.
Now when it comes to skills, commands, agents, but also
MCP servers and a couple of other features, you, of course,
might not always want to set up all these things on your
own. It's not super complex, but, of course, it does cost some
time. And that's why Cloud Code has this concept
which you can access through the /plugin command.
And you can also build custom plugins.
In case that's something you're interested in, you find the official documentation
on that attached. The more common use is probably that you
consume them though because the idea behind plugins is, is that you
can bundle up things like skills and commands and MCP
servers or whatever it is and share them with others in an easy
way. Because when using the /plugin
command, you'll open up the official plugin
marketplace, and you'll find a bunch of plugins in
easily install without having to visit other websites or copy
files around. You can also navigate between
these tabs here with the arrow keys to find a list of installed plugins, and
you see the context7-mcp, which I installed, is
listed as a plugin there because MCPs essentially count as plugins
even though we did not install it through the plugin
marketplace. And there is a marketplaces tab, and by
default, you got the official Cloud Code
and maintained by Anthropic, but you can also add new
marketplaces. So you could use a company internal
for sharing the plugins and it's called Marketplace,
are free. Now, here on Discover, you can then browse all the
plugins off the marketplaces you got installed and
activated, and in my case, that's the official plugins.
You see the context7 plugin here, for example, and there are
other plugins as well. For example, this TypeScript
LSP plugin here could be interesting because that
adds extra capabilities to Cloud Code that help
it detect TypeScipt errors in an easier
way. If I hit space, I therefore toggle
this, and if I hit enter, I can dive a bit deeper into
this plugin. I see more details about it
it, either on my system globally so that it's available
across projects or in this project or in this project
without checking it into version control.
So that are these three settings JSON files you saw over and over
again throughout this course. But we can keep on
browsing. We could install the Playwright plugin to
Cloud Code browser access, which is something I'll get back to, so I will
already install it here. And you can, of course, in general install
any plugins that sound helpful or interesting to you, and obviously
that list will change over time. So here I'll install
the Playwright plugin and I'll install that globally, so user
scope, hit enter, and for the
TypeScript LSP here, I will install
that in my project here with project scope, not
local scope. I wanna have it checked into version
won't install it globally because not all my projects use TypeScript.
Now with these two plugins installed, you see the settings.json file
was updated to enable this TypeScript plugin for my local
project. The user JSON file will have been updated
plugin. And if I now run /plugin
again, under installed, we can see those plugins.
The Playwright plugin, for example, in the end is another MCP
server now just installed as a plugin, but there also would've
been a Playwright MCP server, which you could have installed instead,
installed the context7-mcp before.
But now with that, we added new capabilities to Cloud Code
example, help it understand TypeScrip a bit better
browser access, which is something we'll explore next.