WEBVTT

00:00:00.220 --> 00:00:03.650
As a developer,
using AI efficiently can be quite

00:00:03.660 --> 00:00:07.440
got a bit easier because you can safely
ignore MCP, the Model Context

00:00:07.520 --> 00:00:09.120
Protocol, now, and I'll explain why.

00:00:09.140 --> 00:00:13.040
The Model Context Protocol
was already introduced in 2024

00:00:13.060 --> 00:00:16.760
behind it sounds pretty good. The idea
is that large language

00:00:16.840 --> 00:00:20.530
models on their own are dumb.
They're just producing tokens,

00:00:20.580 --> 00:00:22.970
always will. So they're producing tokens.

00:00:23.000 --> 00:00:26.990
They don't know anything.
And the reason why ChatGPT, for example,

00:00:27.020 --> 00:00:30.780
now much better than it was when it
was initially released is not only

00:00:30.800 --> 00:00:34.410
because models got smarter or better
but mostly

00:00:34.460 --> 00:00:37.880
because ChatGPT now has tools included,
like web

00:00:38.000 --> 00:00:41.240
search or the capability to execute code.

00:00:41.250 --> 00:00:44.940
And the idea behind MCP simply
was to make it easier to expose new

00:00:45.000 --> 00:00:48.589
tools to large language models.
Sounds like it makes sense, right?

00:00:48.620 --> 00:00:52.560
Yeah, sounds like it does
but it doesn't unfortunately because one

00:00:52.640 --> 00:00:55.780
is,
or two big problems with MCP actually are

00:00:55.880 --> 00:00:59.500
that you can't give them a lot of tools.

00:00:59.720 --> 00:01:03.520
If you start adding,
like dozens of MCP servers to your

00:01:03.560 --> 00:01:07.280
AI application, chances are
that it will just

00:01:07.420 --> 00:01:10.980
not use any of these tools
or use them in the wrong way because

00:01:11.020 --> 00:01:14.760
polluting that context with all
that MCP information because all these

00:01:14.860 --> 00:01:18.780
MCP servers, of course,
need to expose information about the tools

00:01:19.260 --> 00:01:23.120
they provide and about the resources they
provide and that can quickly lead to a

00:01:23.180 --> 00:01:26.820
situation where you're making your AI
application dumber

00:01:26.900 --> 00:01:28.840
instead of smarter. So that's one problem.

00:01:28.850 --> 00:01:32.720
Another problem is
that you have to hope that the AI uses

00:01:32.760 --> 00:01:36.560
certain tools or you have to kind of tell
it, "Hey, please use that MCP

00:01:36.620 --> 00:01:40.510
server to get a certain task done," which,
eh, works but

00:01:40.600 --> 00:01:44.440
is not really ideal
and then there's another maybe even

00:01:44.460 --> 00:01:48.030
bigger problem when it comes to MCP
and development,

00:01:48.080 --> 00:01:52.040
on here. As a developer
when it comes to tools like Cursor there

00:01:52.100 --> 00:01:56.040
only so many things you want your AI to
do.

00:01:56.080 --> 00:01:59.220
That might be spinning up a browser
looking at the website.

00:01:59.240 --> 00:02:03.120
That might be querying a database to see
if some data has been

00:02:03.180 --> 00:02:06.870
inserted.
That might be to reach out to some

00:02:06.900 --> 00:02:10.580
documentation. Maybe there also
is some Git-related stuff and

00:02:10.979 --> 00:02:14.960
that's it then.
Now the bad news for the MCP fans are

00:02:15.120 --> 00:02:18.860
you don't need MCP for any of that.
Cursor and all these other AI

00:02:18.920 --> 00:02:22.400
coding tools already have web search built
in or the

00:02:23.000 --> 00:02:26.740
capability to send a request to some
website and fetch the

00:02:26.780 --> 00:02:29.930
content to read it so they can already
visit websites.

00:02:29.980 --> 00:02:33.560
No MCP needed for that.
They already have browser use

00:02:33.660 --> 00:02:35.460
implemented. Cursor has at least.

00:02:35.480 --> 00:02:39.360
It can spin up a browser and view it
and work with it and

00:02:39.460 --> 00:02:43.420
navigate it for you.
They can use the command line

00:02:43.460 --> 00:02:47.100
interact with Git
which allows them to interact with a

00:02:47.180 --> 00:02:50.760
can do all these things already
and that's the reason why

00:02:50.780 --> 00:02:54.750
I don't really use any MCPs
and never felt like

00:02:54.800 --> 00:02:57.810
anything's missing except for one thing.

00:02:57.880 --> 00:03:01.460
One problem I do have as a developer
is providing the

00:03:01.540 --> 00:03:05.030
right context or it's not a problem
but it's the most

00:03:05.080 --> 00:03:08.860
difficult and important thing.
For example, I know that there are a lot

00:03:08.900 --> 00:03:12.870
of modern browser APIs
and CSS features I would like to use in my

00:03:12.900 --> 00:03:16.800
project.
I don't want to write CSS code like it's

00:03:16.820 --> 00:03:20.340
but that's what AI typically does as a
default and I don't want that

00:03:20.560 --> 00:03:24.420
so I typically remind AI to please use
relative

00:03:24.460 --> 00:03:28.400
colors, for example,
or please use the pop-over API and that's,

00:03:28.420 --> 00:03:32.410
course,
annoying but that's something where I

00:03:32.440 --> 00:03:36.329
this new Skills standard which
is emerging and evolving.

00:03:36.360 --> 00:03:40.300
The idea behind Skills is
that in your project you can add

00:03:40.680 --> 00:03:44.240
a Skill folder and right now where you add
that

00:03:44.280 --> 00:03:47.630
folder still kind of depends on
which tool you're using.

00:03:47.660 --> 00:03:51.440
Cloud code,
you would have a Skills folder in the

00:03:51.900 --> 00:03:55.800
and then for each skill you would add a
subfolder in that Skills folder

00:03:56.060 --> 00:03:59.360
and add a skill.md file. That
is the bare minimum.

00:03:59.380 --> 00:04:01.480
Now what goes into that skill.md file?

00:04:01.540 --> 00:04:04.300
In the end just some context,
just a prompt you could say.

00:04:04.380 --> 00:04:06.760
This is simply how such a skill.md file
could look like.

00:04:06.780 --> 00:04:10.720
You have some metadata which
is just the name and description a- as

00:04:10.780 --> 00:04:14.620
a minimum and the description
is the part that will help the AI decide

00:04:14.640 --> 00:04:18.070
whether to use the skill because the idea
behind these Skills

00:04:18.180 --> 00:04:21.980
is that the coding agent essentially loads
all

00:04:22.000 --> 00:04:25.820
these names and descriptions into its
context whenever you

00:04:25.940 --> 00:04:29.820
start a new chat and that's obviously just
a few tokens so that's no problem.

00:04:29.840 --> 00:04:33.220
It's not polluting your context
but it has all that

00:04:33.260 --> 00:04:37.070
information. It has a system prompt,
of course, that makes sure that this

00:04:37.120 --> 00:04:41.040
is prominently embedded and
that it considers all

00:04:41.080 --> 00:04:44.860
these skills whenever tackling a task
and it would then

00:04:45.020 --> 00:04:48.560
take a look at the entire file, open
that entire file but only then

00:04:48.960 --> 00:04:52.700
and then it therefore gets the rest of
this content which is

00:04:52.780 --> 00:04:56.400
just an extra prompt,
just some extra context that's loaded

00:04:56.800 --> 00:04:59.180
on demand and that's the important part.

00:04:59.220 --> 00:05:02.680
Now a Skill can be more than that.
You can add subfolders to each

00:05:02.740 --> 00:05:06.640
skill to even add scripts so your own code
that should be

00:05:06.660 --> 00:05:10.540
executable so that you can add your own
tools in the end connected to

00:05:10.550 --> 00:05:14.400
a skill that can be used so for example
you could add code that opens and

00:05:14.440 --> 00:05:18.380
reads a PDF document so
that you have your own parsing logic in

00:05:18.420 --> 00:05:22.340
place.
You can add extra references like extra

00:05:22.380 --> 00:05:26.180
you could therefore, for example,
build a skill that helps the AI write

00:05:26.260 --> 00:05:30.180
better React components by making it aware
of the fact that it might

00:05:30.250 --> 00:05:34.080
not need useEffect because AIs love to use
useEffect

00:05:34.560 --> 00:05:38.260
but they might not need to. There
is a full article on the official docs

00:05:38.300 --> 00:05:42.120
that you might not need an effect.
You can put that into your references,

00:05:42.220 --> 00:05:45.960
skill related to that,
maybe also add some other React component

00:05:46.020 --> 00:05:49.840
related information in there
and then whenever you ask the AI

00:05:49.950 --> 00:05:53.840
to do something that's related to a React
component there's a high chance

00:05:53.880 --> 00:05:57.800
of it loading that skill and using
that extra knowledge and context

00:05:57.810 --> 00:06:01.640
so that you don't constantly have to
repeat yourself or hope

00:06:01.650 --> 00:06:05.530
that the AI does things the way you want
it to do and that's why I

00:06:05.560 --> 00:06:09.450
find this Skill spec quite interesting
and why I'm using Skills in

00:06:09.460 --> 00:06:13.420
my projects to make AI aware of all the
modern syntax I'd

00:06:13.440 --> 00:06:16.840
like it to use and why I personally don't
find MCP super

00:06:16.940 --> 00:06:19.820
interesting when it comes to development
with AI.