WEBVTT

00:00:00.080 --> 00:00:03.200
So the app is essentially done here.

00:00:03.260 --> 00:00:06.760
You could always add more features,
change the styling,

00:00:06.800 --> 00:00:10.640
whatever,
but I'm quite happy with the current state

00:00:10.760 --> 00:00:14.520
of this app. And throughout this course,
we, of course, covered all these

00:00:14.620 --> 00:00:18.100
core features Cloud Code has to offer,
skills, agents,

00:00:18.140 --> 00:00:21.960
commands, how to write prompts, plan mode,
and so on.

00:00:21.980 --> 00:00:25.580
Now when it comes to skills, commands,
agents, but also

00:00:25.680 --> 00:00:29.620
MCP servers and a couple of other
features, you, of course,

00:00:29.680 --> 00:00:32.920
might not always want to set up all these
things on your

00:00:32.980 --> 00:00:36.740
own. It's not super complex, but,
of course, it does cost some

00:00:36.780 --> 00:00:40.640
time.
And that's why Cloud Code has this concept

00:00:40.690 --> 00:00:44.020
which you can access through the /plugin
command.

00:00:44.030 --> 00:00:46.740
And you can also build custom plugins.

00:00:46.780 --> 00:00:50.630
In case that's something you're interested
in, you find the official documentation

00:00:50.640 --> 00:00:54.540
on that attached. The more common use
is probably that you

00:00:54.580 --> 00:00:58.360
consume them though because the idea
behind plugins is, is that you

00:00:58.400 --> 00:01:02.120
can bundle up things like skills
and commands and MCP

00:01:02.200 --> 00:01:06.100
servers or whatever it is
and share them with others in an easy

00:01:06.180 --> 00:01:09.460
way. Because when using the /plugin

00:01:09.500 --> 00:01:12.740
command,
you'll open up the official plugin

00:01:13.080 --> 00:01:16.740
marketplace,
and you'll find a bunch of plugins in

00:01:16.820 --> 00:01:20.480
easily install without having to visit
other websites or copy

00:01:20.640 --> 00:01:24.500
files around.
You can also navigate between

00:01:24.540 --> 00:01:28.510
these tabs here with the arrow keys to
find a list of installed plugins, and

00:01:28.560 --> 00:01:32.320
you see the context7-mcp,
which I installed, is

00:01:32.380 --> 00:01:36.300
listed as a plugin there because MCPs
essentially count as plugins

00:01:36.440 --> 00:01:39.180
even though we did not install it through
the plugin

00:01:39.220 --> 00:01:43.120
marketplace. And there
is a marketplaces tab, and by

00:01:43.180 --> 00:01:47.040
default,
you got the official Cloud Code

00:01:47.100 --> 00:01:49.960
and maintained by Anthropic,
but you can also add new

00:01:50.040 --> 00:01:53.940
marketplaces.
So you could use a company internal

00:01:53.960 --> 00:01:57.700
for sharing the plugins
and it's called Marketplace,

00:01:57.760 --> 00:02:01.680
are free. Now, here on Discover,
you can then browse all the

00:02:01.700 --> 00:02:04.800
plugins off the marketplaces you got
installed and

00:02:05.080 --> 00:02:08.560
activated, and in my case,
that's the official plugins.

00:02:08.600 --> 00:02:12.580
You see the context7 plugin here,
for example, and there are

00:02:12.640 --> 00:02:16.340
other plugins as well. For example,
this TypeScript

00:02:16.440 --> 00:02:20.200
LSP plugin here could be interesting
because that

00:02:20.300 --> 00:02:23.960
adds extra capabilities to Cloud Code
that help

00:02:24.100 --> 00:02:27.360
it detect TypeScipt errors in an easier

00:02:27.420 --> 00:02:31.340
way. If I hit space, I therefore toggle

00:02:31.380 --> 00:02:35.220
this, and if I hit enter,
I can dive a bit deeper into

00:02:35.260 --> 00:02:39.080
this plugin.
I see more details about it

00:02:39.120 --> 00:02:42.790
it, either on my system globally so
that it's available

00:02:42.940 --> 00:02:46.840
across projects or in this project
or in this project

00:02:46.880 --> 00:02:49.180
without checking it into version control.

00:02:49.200 --> 00:02:53.060
So that are these three settings JSON
files you saw over and over

00:02:53.080 --> 00:02:56.660
again throughout this course.
But we can keep on

00:02:56.720 --> 00:03:00.640
browsing.
We could install the Playwright plugin to

00:03:00.680 --> 00:03:04.590
Cloud Code browser access, which
is something I'll get back to, so I will

00:03:04.620 --> 00:03:08.540
already install it here. And you can,
of course, in general install

00:03:08.640 --> 00:03:12.510
any plugins that sound helpful
or interesting to you, and obviously

00:03:12.560 --> 00:03:16.400
that list will change over time.
So here I'll install

00:03:16.440 --> 00:03:20.320
the Playwright plugin
and I'll install that globally, so user

00:03:20.400 --> 00:03:23.640
scope, hit enter, and for the

00:03:23.800 --> 00:03:27.700
TypeScript LSP here, I will install

00:03:27.720 --> 00:03:31.560
that in my project here with project
scope, not

00:03:31.620 --> 00:03:35.260
local scope.
I wanna have it checked into version

00:03:35.380 --> 00:03:39.320
won't install it globally because not all
my projects use TypeScript.

00:03:40.340 --> 00:03:44.060
Now with these two plugins installed,
you see the settings.json file

00:03:44.160 --> 00:03:47.920
was updated to enable this TypeScript
plugin for my local

00:03:48.000 --> 00:03:51.700
project.
The user JSON file will have been updated

00:03:51.780 --> 00:03:55.340
plugin. And if I now run /plugin

00:03:55.400 --> 00:03:59.329
again, under installed,
we can see those plugins.

00:03:59.360 --> 00:04:03.220
The Playwright plugin, for example,
in the end is another MCP

00:04:03.260 --> 00:04:07.180
server now just installed as a plugin,
but there also would've

00:04:07.220 --> 00:04:11.100
been a Playwright MCP server,
which you could have installed instead,

00:04:11.140 --> 00:04:13.680
installed the context7-mcp before.

00:04:13.700 --> 00:04:17.440
But now with that,
we added new capabilities to Cloud Code

00:04:17.500 --> 00:04:21.459
example,
help it understand TypeScrip a bit better

00:04:21.480 --> 00:04:24.659
browser access, which
is something we'll explore next.