The Build-Off
Leap WeekSeason 4Episode 2March 27 2026Three builders. Three AI tools. One backend. Who can ship the best frontend in 30 minutes?
Speaker 0: What's up, everybody? It is great to see you, to meet you virtually here. My name is Matt. I'm on the marketing team here at Directus. And if you're watching this, you're in for a treat because we have quite the repertoire of guests here today, also from the Directus team, and we're gonna be doing something pretty fun.
But first, let me introduce each guest. You know him. You love him. You've seen his face all over the place. It's John Daniels.
Speaker 1: John Daniels.
Speaker 2: What's up? Glad that you
Speaker 0: started with me.
Speaker 2: I was worried you were gonna say Brian. So hello.
Speaker 1: Your face is all over the place right here.
Speaker 0: I don't think anybody really knows who Bryant is. So, no. No. No. No.
Of course, we have the man himself, mister Bry. Bryant Gillespie, who's one of our esteemed developer advocate type folks, I guess, on the team. You know? He kinda does everything.
Speaker 1: Type folks? Yes. Happy to be here. Very excited for this. Look.
I'm just gonna start this off with saying whatever we're doing in this competition, I'm gonna mop the floor with you guys. That's it.
Speaker 0: Strong start. I was gonna do this not in the spirit of competition, but in Oh. In in friendliness, but I guess that's what we're gonna do now. Alright. And if anybody doesn't know, John is one of our AEs here at Directus, so the most competitive of of everyone here.
So I'm sure pretty sure that'll awaken a fire in a moment. So, yeah. Brian, what are we doing today? I
Speaker 1: this is your show, my friend. You tell me what we're doing. Clearly, it's something to do with an AI skills directory because that is what's on the screen.
Speaker 0: That is what's on the screen. Alright. I'll give you the brief rundown. So today, we are gonna have a build off. Everybody's been talking about front ends and UIs, and the errors are shifting.
And there's so many tools out there. I'm a user of Cloud Code for a lot of the marketing stuff that we do here at Directus, including building the Leap Week landing page. Our team uses codex. Our team uses a lot of the out of the box, like, harnesses, like cursor. And we also use things like Lovable.
So it's a good mix of things, but that's a lot of subscriptions add up. So we thought, why not put the skills to the test and see which we can use best for building the front end on a Directus back end, which would be a skills directory. And one of the reasons we wanna do a skills directory is because there's a lot of shady skills directories out there and there's a lot of mistrust in a lot of them. So our developer team has a lot of, skills that they share, that we thought would be cool to build something along with that, as well as our go to market team uses a lot of things too. So, yeah, that's really the gist.
Did I
Speaker 1: What are the what are the stipulations for this, man? We're building a skills directory front end. We're gonna need a back end for that, which we'll do, but what are the rules?
Speaker 0: There are no rules. There's only one rule. And that is
Speaker 1: that's details?
Speaker 0: Yeah. There's gonna be one rule where we have to create the back end and direct us. And then whatever tool we're gonna use, we are going to use the same back end for that front end. So running down the list of tools that we will use, I will be using Lovable. It's something I've used in the past.
I've I've not actually used it in quite a bit, because I've been using, Cloud Code. But, Brian, what are you gonna be using?
Speaker 1: I'm gonna be using Cloud Code.
Speaker 0: Alright. John, what you got?
Speaker 2: I use my old dependable cursor.
Speaker 0: Yeah. Is cursor what you built? The, garage inventory?
Speaker 2: It is. Yeah. Yeah. And I already have a I already have an idea.
Speaker 0: Oh, boy. Oh, no.
Speaker 2: Retro. It's a lot yeah.
Speaker 1: Front end directory.
Speaker 2: It's a long
Speaker 1: Here we go.
Speaker 0: I'm doing that maybe more than, like, moving forward in my chair.
Speaker 1: Cool.
Speaker 0: Yeah. Well So Right. To kick things off, I'm assuming we'll kick we've started.
Speaker 1: We we got a totally blank data model here. We'll just call it skills directory. Right? John is just banging on the keyboard, man. Alright.
Totally empty. It's like you know, we'll we'll do this 100 app style. Like, what what what do we even need on a skills directory? Right? You're gonna need some skills, but what what is the what are the other stuff that you're planning on tracking here?
What do you need for the back end?
Speaker 0: Yeah. That's a good question. When you say skills, what does that encompass? Is that like the title and the description and the actual I mean, skills are basically just a fancy word for markdown files. Right?
Speaker 1: Yeah. I mean, that's, yeah, that's the the funny thing about all of this stuff to me is it's all just markdown. Like, been been dealing with markdown since I was 12. A week ago. Yeah.
So we got a name, a description for the skill. You've got the, what, the actual skill content. I don't I don't
Speaker 0: know.
Speaker 1: Are you I'm assuming you're gonna have, like, users who submit the skills?
Speaker 0: Mhmm. We'll have I think, at some point, if we wanna
Speaker 1: Submit a bug.
Speaker 0: Public facing, but for our internal team makes sense. You probably want, some sort of, like, tagging system. So if it's engineering skill or if it's
Speaker 1: So the tag name. Okay. What else you got?
Speaker 0: Option for an image, if you wanna add that to the front end potentially.
Speaker 1: Image? Okay. You're getting away from the markdown stuff now. I'm gonna just draw the arrows for fun here
Speaker 0: at this point. Here we go.
Speaker 1: Boom. Alright. So you got skills. You got tags. What else do you need?
Speaker 0: I mean,
Speaker 1: I Repository. GitHub repository. Is that where they're coming from?
Speaker 0: Could you just host it within Directus itself, like, as a file?
Speaker 1: I mean, we can. Yeah. Like, do you want it linked to somewhere?
Speaker 2: I think
Speaker 0: I wanna keep it, like, self like, contained within the one
Speaker 1: thing. Okay. Alright. Cool. Is this anything else?
Or is it we're just gonna roll with this.
Speaker 0: Just keep it simple. Unless you got anything to do. Wait.
Speaker 2: No. Keep it simple, stupid.
Speaker 1: Which one is stupid, man?
Speaker 2: You probably said it.
Speaker 0: Alright.
Speaker 1: I've got this. So, hopefully, I've got some secret sauce here. Been working on a CLI tool. So I'm gonna tell Claude code here. Can you guys see this?
Should I zoom way in? Alright. Run d six s agents. It's our CLI for connecting to direct us.
Speaker 0: D six s. It's the first time seeing the CLI in action right here.
Speaker 1: Very nerdy. You know, the Kubernetes deal. What is this thing doing? Why is it not running this command? It's reading four files, which d success.
Just run the command, dude. What are you doing?
Speaker 2: Chose the wrong tool. Maybe cursor's been
Speaker 1: Maybe you chose the wrong tool. Yeah. There it is. Okay. So, basically, that command gives it a little context about this.
Cool. And now this thing should be primed to go. Agents. Right. Cool.
Alright. So now we're gonna kick it over into plan mode. I'm gonna paste that image that I had. Right? And we're just gonna say, hey.
We're building an AI skills directory. Here's a screenshot of a data model I'm competing with John and Matt. We need the back end in Directus first before we build the front end. Can you plan out the Directus back end?
Speaker 0: Yeah. Alright.
Speaker 1: I've been using Let's see what happens here. Okay. Right here. Alright. It is going to alright.
This is where I tell you to do as I say, not as I do, because I'm just gonna turn this thing loose. Right? I should have actually set dangerously set permissions here. But
Speaker 2: I don't even have it ask for permission anymore. I just let it go.
Speaker 1: Go, baby. Go.
Speaker 0: I have to leave this a lot. That's probably why.
Speaker 1: If you can't leave that out, security infraction.
Speaker 2: Security. Spent hundreds of dollars in tokens last month.
Speaker 1: Alright. It's going to write this plan. Are you so are are you not using cloud code at all? You're still using cursor every day?
Speaker 2: I use both. Depends on what I'm doing.
Speaker 0: So what so what you're you're basically just doing what the MCP used to do just from the terminal
Speaker 1: So is the why the CLI? Right? Well, the reason why is because context. The context window. So MCP uses up a lot of context, for comparison.
Right? Like, if you have all the tools enabled, MCP or our AI assistant right now could use up to thirty, forty thousand tokens to have all the tools enabled. The CLI, by default, doesn't load anything into the context, and the agent is or like CloudCo, these agent harnesses are pretty good at navigating, like, CLIs just because they're they're trained on a lot of bash scripts and stuff like that. So, you know, it basically you keep the context window clean until you need it, and, yeah, you follow this progressive discovery pattern. I'm yeah.
I've been talking. I'm not even looking at this plan. Hopefully, this thing actually does what we wanted to do. We shall see. Right?
Actually, use recipes. D success recipes. This is should be a shorthand. Again, this is all highly experimental, so failed to log the plug in, so it's not gonna use that at all. Plug ins.
Index. Oh, good. Alright. Well, just push forward. We may be kicking back to the MCP for this.
Speaker 0: Hey.
Speaker 2: Alright. Is what I when I type in the when it when MCP goes wrong for me, I say, just do it, and it'll it'll figure it out.
Speaker 1: Just do it. Figure it out funny, man.
Speaker 0: Turn off permissions and just go.
Speaker 1: What is this thing doing? Your token doesn't have admin access. I do have admin access.
Speaker 0: No. You're wrong. You said, highly experimental. Correct?
Speaker 1: I mean, it it was working well. Works on my machine until you start recording. Right? Right. So we'll just go back to the old tried and true here.
Both collections exist, but I have no schema. Oh my gosh. This thing is hopelessly lost.
Speaker 2: Lost. Hey. There's two collections in there now.
Speaker 1: Yep. They're actually just folder collections because they don't exist. Alright. Skills. When I say tried and true, I mean me.
Alright. What do we have there? We have name, description, content. Name.
Speaker 0: I've never seen anyone move this fast inside of the.
Speaker 1: Content. Just markdown. It's just markdown. There you go. Alright.
You got tags. Yeah?
Speaker 0: Mhmm.
Speaker 1: Cool. Tags. I have a name for the tags. Tag name. Cool.
And then we need a skill tags. We need a junction table. Cool. I'm taking the long way around here. Skills.
Now I'm gonna go to the mini mini relationship inside directions. It's been a minute since I've done this, man. Don't you miss it? Always I do miss it. Yeah.
It took me an hour to do half of this stuff that I could now do in, like, five minutes using the AI tools when they work, mind you. Skills ID, tags ID. Let's just call it skill. Let's call it tag. Skills.
Cool. Give it a sort field. Boom. Boom. Boom.
Speaker 0: Boom. You know, it's worth that messing up to watch you do this. It's like watching Boom.
Speaker 1: That's it. There's the back end. You're good. Golden. Very simple.
Very easy. Now what?
Speaker 2: Now we need some data.
Speaker 1: Mhmm. Maybe it can do that. Look, I I set it all up. Nice. Thanks for nothing.
Now I need you to create some sample data for us, though. I mean, I'm a make sure you rub it in the face of the thing. Right? Talk to me well, I this might take a minute, but,
Speaker 2: like, what are you guys Like, when you
Speaker 1: are are we supposed to talk about what we're gonna build? Like, how the front end is gonna look, or is this gonna be, like, a secret thing?
Speaker 0: We'll talk about, you know, how things are going. I'm still I'm between a couple ideas on what I want this front end to look like. I I want it to not look like a generic directory because there's, like, directories of directories out there. I already
Speaker 2: have an idea, so don't even don't even worry about Wait.
Speaker 0: Alright. Was it one that we talked about earlier, or is this one this is completely new?
Speaker 2: I got a new idea.
Speaker 0: Interesting. Okay. I think I'll have an idea.
Speaker 1: You think you'll have an idea? Alright. Well, it's got there's eight tags. There's six skills. Let's add 10 more skills.
Create a few sample users as well, give them a different role. Just the ability to view skills and update the ones they've uploaded. Alright. So now we're gonna move to the the front end stuff. Yeah?
Speaker 0: Yeah. I think so. So we're all operating off of the same direct us back end, and you just created a few users. I'm assuming that's to give us access to that data.
Speaker 1: Yep. So you guys have your own users in there. Looks like it's created
Speaker 2: Only one guy cares about a photo.
Speaker 1: Yeah. Oh my gosh. Alright, dude. Fine. Fine.
Fine. Fine.
Speaker 0: Yeah. Boom. I'll update my You
Speaker 1: look you look rather young in that one,
Speaker 2: John. Thanks.
Speaker 1: Alright. So what do I dig at all.
Speaker 0: Thank you. Alright. So each of us is gonna have our own role, and you will provide that role
Speaker 1: to us.
Speaker 2: If you refresh real quick. Sorry. Refresh bright. There.
Speaker 0: Of course.
Speaker 1: Yeah. We're reading we're watching this. You're certainly not watching this on Saint Patrick's Day. We're recording it on Saint Patrick's Day, though.
Speaker 2: Yeah. Yeah. Yeah. Well done.
Speaker 0: Yeah. That one.
Speaker 2: Sorry. Continue, Matt.
Speaker 0: How do you have access to this already? I
Speaker 1: I already gave him access. I put it in the chat. I sent you guys up already. Your direct us email and your password. What's the password?
The password is Password. Now, hopefully, one of us will remember to have removed that by the time this recording goes live.
Speaker 2: I'll tell him how to change
Speaker 0: it. In the chat. Must be what is this
Speaker 1: thing doing. Okay. I was creating, like, 35. Why can't I not just accept all here? Good lord.
Speaker 0: Shoot me the shoot me the URL in the chat. I don't see it in there.
Speaker 1: It's a imigos.directus.app.
Speaker 0: Got it now. Alright. Alright. I'm in.
Speaker 1: Alright. Alright. Alright. Alright. Invalid input.
Sarah Chen. Why does it keep trying to I don't know. It really likes the name Sarah for whatever reason.
Speaker 0: Hey. I got a crush.
Speaker 1: Marcus, Priya, Sarah. Those are the folks who are uploading the other skills. Alright. So we're good then. Yeah.
There's gonna be some skills that populate in there, and then everybody is jamming on the back end. How long are we do we have on the back or on the front end? Right?
Speaker 0: I set a timer. We have, like, two minutes now, but, if we wanna take ten minutes, you know, and
Speaker 1: do what we Ten minutes to do a whole back end or a front end?
Speaker 0: Yeah, man. I mean, it's the UI error is changing, so they say.
Speaker 1: I at least, like, 15. Yeah?
Speaker 0: 20 to 30.
Speaker 1: We could do, like, a supercut.
Speaker 0: We'll extend this session a little bit. We've got some time.
Speaker 1: Do a supercut. Yeah. Alright. Twenty minutes then. That's it.
Twenty minutes. No more. No less.
Speaker 0: I think You
Speaker 1: guys better not be starting with the back end already or front end already.
Speaker 0: Sure John's already done. I've been Yeah.
Speaker 1: He's already done. Hearing him. Alright.
Speaker 2: I'm just right now, I'm just setting up the m I'm setting up my MCP and cursor.
Speaker 1: Alright. Well, you guys just tell me when you're ready to go.
Speaker 0: I'm I'm pretty confident
Speaker 1: in my skills.
Speaker 0: Let's say we're using, like, you know, lovable or something. I've got my user here. I create It's got admin policy, create a new token, save said token, and should be good to pull data from that directly.
Speaker 1: Yeah. And just lovable have FCP?
Speaker 0: I don't know. It's a good question.
Speaker 1: Personal connectors. There you go, dude.
Speaker 0: I see it. I sees it.
Speaker 1: Here's the directisio docs. I'm gonna just point you in the right direction there. Connect AI, AI, MCP server. This is the page that you need from the documentation. I'm gonna paste that in the chat.
Good luck to you, sir. You guys just all the skill the back end is done. The back end is locked. Don't even think about changing the back end.
Speaker 2: Alright.
Speaker 1: When you guys say go, I'm gonna hit go. Hit go. There it is. Alright. Twenty minutes, boys.
Speaker 0: I'm I've gotta upgrade my lovable account because, apparently, Lovable doesn't allow custom MCPs unless it's It
Speaker 2: sounds like an excuse, bro.
Speaker 1: Already an excuse.
Speaker 0: Alright. One pro. I'm gonna spend this whole time setting up my custom MCP.
Speaker 1: Oh, no. Why can't I see the text here? Oh, that's not good. I'm going react on this one. Why can't I see this, though?
I just got this new Mac, man. Still, if you guys beat me, that will be b y since we're just throwing excuses out there.
Speaker 0: I am still signing a still I'm still going there by a sign up for a year.
Speaker 1: I can't even get the I can't get the tan stack start script here from the their website.
Speaker 2: Start.
Speaker 0: Connection failed. Gotta love it. Alright. Well, mobile mobile is not really communicating with me right now. I'm having trouble.
I hope you guys are having fun. I'm having a blast.
Speaker 2: Matt, is your keyboard connected yet?
Speaker 0: Yes, John.
Speaker 2: Alright. Let's see. I got my build plan ready. Let's see if this looks good.
Speaker 0: No. I don't think Lovable's gonna be the the move. Not great, Lovable. Not great.
Speaker 2: Alright, guys. I've clicked build. We're gonna we're gonna get v one running. What if we finish in ten minutes? Does that give us bonus points?
Speaker 0: I should be done setting up my MCB by then. So
Speaker 2: Matt, why don't you have a rabbit in your background? Brian and I both have a rabbit in the background.
Speaker 1: I have several.
Speaker 0: Because I like to have my rabbits in my point of view. So not in the background. Alright. Well, local's not gonna work with me on the MCP, so I'm gonna have to roll.
Speaker 1: You just just gonna have to roll. Can I just copy, Jace? You could just tell it to use the SDK. I think you
Speaker 2: can copy.
Speaker 1: I think
Speaker 2: you can also just give it your API token and just give it access. I think I've done that before. You'd be like, hey. I'm an API token. Didn't know we'd get excuses so quick out the gate, though.
Speaker 0: You know, usually, I'm using, like, whisper for this. Go for it. Okay. Then we
Speaker 1: know what you're gonna build. Right?
Speaker 2: Just meet your just meet yourself while you mouth it and then unmute.
Speaker 1: I need a front end that looks great. Make no mistakes.
Speaker 2: Make it look beautiful.
Speaker 1: I I hope John's idea is something that looked like a pot of gold and a leprechaun.
Speaker 2: No. But that would have been good. Dang. I think mine'll be good, though.
Speaker 0: I I have no idea what this output of this prompt is gonna mean. I'm actually kind of terrified. I
Speaker 1: know. I'm just reading my typing, and it's freaking terrible.
Speaker 0: That's why he's was
Speaker 2: The good news is AI doesn't care about typos.
Speaker 0: What were the tags we put in here, by the way?
Speaker 1: Research writing, design, automation, productivity, coding, marketing, and data analysis.
Speaker 2: We should upload these to to, like, Vercel or Netlify or something afterwards so people can play with them, the front ends.
Speaker 1: That should be that should be solid.
Speaker 2: Here's the file being created right now. It's called bang effect dot JSX.
Speaker 1: Bang effect. You may win this, man. I think you guys had more time to think about the ideas here.
Speaker 2: Don't
Speaker 0: yeah. I
Speaker 1: don't have a solid idea.
Speaker 0: Lost trying to set up the MCP server in Lovable.
Speaker 1: Oh, that's a risky run. You've got what what did we got on the clock? Thirteen twenty one.
Speaker 0: Plenty of time.
Speaker 1: Just just come on, Claude. Don't film me now. I like you, dawg. We got this. We got this.
Speaker 2: Oh, first preview. It looks good.
Speaker 0: Did you one shot it? Oh,
Speaker 2: damn. This is okay. You guys are gonna lose.
Speaker 1: He's blowing smoke. I know.
Speaker 0: He's he doesn't have anything. It's just a blank screen.
Speaker 2: I wish you guys could see this. No.
Speaker 0: I'm trusting lovable with my lunch.
Speaker 2: The sound effects are amazing.
Speaker 1: You have sound effects?
Speaker 2: The only problem is I can tell the words are backwards. I'm like, why are these words backwards?
Speaker 0: What, wait. Tags. One, two, three.
Speaker 2: I like how there's, like, duplicate tags.
Speaker 0: Lovable has gotten a lot better on the user interface since all of us use it. Like, it quite looks nice, except for the whole connecting and MCP thing.
Speaker 2: I wish you guys could hear these sound effects.
Speaker 1: I think I can hear a few.
Speaker 0: Did you do freaking lasers?
Speaker 2: Oh, it's looking so much better now. Oh my gosh. This looks so good.
Speaker 0: It's a risk. It's poker face.
Speaker 2: No. You know it's a good a good project when you are playing the game that you've built.
Speaker 1: I'm still waiting for dependencies to resign. Alright. You know me, Ben. If you enjoy watching people slide by on the skin of their teeth, please tune in to Directus TV for where yours truly embarrasses himself twenty four seven by trying to build apps. Oh god.
This is going horribly wrong. I should not have should not have done React that is using way outdated stuff. We're just I I don't know. Tam, if you watch this, man, I don't know what happened to the website today when I was recording this, but
Speaker 0: I think this is gonna be
Speaker 1: Oh, there it is. Finally. It's okay.
Speaker 0: You got something?
Speaker 1: Must have been I the site must have been broken, man. I don't I don't know.
Speaker 2: Okay. Now now it's playing its playing its game on its own. This is where where it's fun to watch Cursor play its own game.
Speaker 0: You got your AI playing an AI? K. What are you doing over there?
Speaker 2: Who? Me? Just kicking ass?
Speaker 0: I'm gonna have to rely on a one shot here.
Speaker 2: I think I might have this with a one shot. We'll see. It's still it's finishing up the build.
Speaker 0: This is building out the comp I'm building the character select and move list UI right now, so we're gonna have to wait a a second. Did you create an RPG, John?
Speaker 2: No. I created a a video game. Do you wanna know what its theme theme is?
Speaker 0: I wanna wait and see.
Speaker 2: Okay.
Speaker 1: Leprechauns?
Speaker 2: No.
Speaker 0: Pecauns. I think I you know, if I had more time, it would be cool to do, like, an RPG style directory where you have to, like, level up to get the better prompts. I wonder if anybody would spend time or not. Probably not.
Speaker 1: I've been looking at this thing, and I'm just like, I don't even know.
Speaker 0: Do you have anything? Do you have a UI at all, Brian?
Speaker 1: I I have nothing on the screen.
Speaker 0: That's not good. How much time do we have left?
Speaker 1: Six minutes. Oh, man.
Speaker 2: Guys, this you might as well just stop. I'm telling you, you're gonna lose. I know Matt basically has nothing. He's gonna show a white screen. It's gonna be like index.html.
Speaker 0: We're gonna wait and ask I
Speaker 1: have a header.
Speaker 0: You have a header?
Speaker 1: I have a header.
Speaker 2: Match this line to us.
Speaker 0: Have have I been in the roost this whole time? Who knows?
Speaker 1: I feel like I do miss the old days where I just good old fashioned handwriting code. I probably yeah. On a 100 apps, hundred hours, like, the days of all, I woulda had something already that looked nice. I'm not super happy with what I've got here.
Speaker 0: I do only have a white screen.
Speaker 2: K. I put in one more prompt. I I'm three shotting it, and I think three shots might be it.
Speaker 0: I think my idea was here, but the execution is lacking.
Speaker 2: Oh, it even gave it a little tab icon. Nice.
Speaker 0: Alright. I think we got something.
Speaker 2: Matt, are you past the home page yet? Did you get logged in yet?
Speaker 0: Been spending all this time on the initial
Speaker 2: You spent fifteen minutes of the twenty minutes just upgrading to pro. I did.
Speaker 0: I might have credit card information floating out there, so remind me to cancel my cards. Alright. We got something working. Yeah. Without the MCP, I'm I'm not really able to pull the.
Speaker 2: Here's what here's what my cursor just said so you know what it's doing. The buttons are noticeably bigger now. Let me shoot a couple skills first, then test the collected view and detail pop up. That's a little hit into what I've built.
Speaker 0: Are we talking legend of Zelda or something? What? Dangerous to go
Speaker 1: alone. Sweet mother.
Speaker 0: He's still in there, or is that going too?
Speaker 1: I still got it. Started off on the wrong foot, man. Should not have, should not have tried to go React. Should just you gotta stick with what you know, man.
Speaker 0: Talk with what you know. Why did you go with React? You were trying to get fancy?
Speaker 1: I I've been using, I I got a project, a personal project where I've used, TanStack start lately. I'm trying to learn a little more about React so that I'm not one dimensional. Mhmm. Did not pay off today. Did not pay off today.
Mhmm. Thirty seconds. Yeah.
Speaker 0: This is I've just spent all the time troubleshooting. Lovable doesn't seem to really work well with custom MCPs, so if anybody's curious.
Speaker 1: Fifteen, fourteen, 13. Who are you who's who gets to go first?
Speaker 0: Well, I
Speaker 1: mean, clearly, it sounds like John.
Speaker 0: Like, John's face means that
Speaker 1: he may have something really good. He might have. Yeah. Time's up.
Speaker 2: Yeah. Time's up. It's just finishing it's just finishing its build, but I've just been I only needed three prompts to get it to some pretty amazing.
Speaker 0: Okay. I mean, I've got something. It's not,
Speaker 2: Sounds like you have nothing.
Speaker 1: It's basically You go then. Me?
Speaker 0: Let me it's still finishing this moment. The junction table I faced. Alright. I just refreshed. We'll see.
Speaker 1: I I think that is I'll go then. I'll go.
Speaker 0: Yeah. Let's see what you got, Bryant. I'm excited to see this
Speaker 1: header. Screen. I didn't have time to work on the design. We have a skills directory. I was going for, like, the brutalist theme.
It didn't really get. I I had literally no time to worry on the design. So the the tags do work, which is nice. We can search. So we search for SEO.
That works. We can load up the skill. We see it being loaded here. You know, you got the nice little subtle detail, the little arrows instead of the standard bullet points. You got the the fake install.
And then the coup d'etat. Is that what the I don't know. I don't know. Matt has surely lost.
Speaker 2: Nice.
Speaker 1: Stakes. Pretty badly.
Speaker 0: Oh, so you can submit skills from the front. That's pretty good. Pretty good.
Speaker 1: Oh. No.
Speaker 0: Failure.
Speaker 1: Yeah. I did get a chance to to fix that. If I had, like, two more minutes, like, whatever it is that you're doing right now while I'm demoing mine.
Speaker 2: I'm not doing anything.
Speaker 1: This looks good. I mean talking to Matt.
Speaker 0: Design wise? What like, I mean, I think it looks solid. I would probably call it
Speaker 1: I I wouldn't have gone, like, the dark mode design. Right? I would have gone light mode, and I would've, like, just had it be very in your face. Would have been nice to have, like, the login to be able to submit this, but, again,
Speaker 0: just good
Speaker 1: to me. Wrestle with it too much.
Speaker 2: It's more than I was expecting. It's it looks good.
Speaker 0: Yeah. Call it Hill Skills. And
Speaker 1: it's got,
Speaker 0: like, kind of a nineties vibe to it. I dig it. Alright. I guess I'll go next. We'll see what happens here.
But, alright. This is called, AI skills pro skater presented by AI Amigos. So the concept
Speaker 2: I wanna say I'm impressed that you have something. I thought you were gonna show us nothing.
Speaker 0: Maybe maybe I was in Parker Face the whole time. But, anyways, the concept here is you start by tag. So you pick your, it's not really skateboarding, but the concept was Tony Hawk's Pro Skater. But, it was supposed to be whoever like, I wanted to do it by people in an organization. So engineers would wanna probably see the engineering skills, marketers, that sort of thing.
So starting with tags, which is something I haven't seen before. And then in true Tony Hawk fashion, ideally, what I was trying to get was to unlock the skill, you have to do the, like, combo thing with the keyboard. And, it would do a little trick sort of thing. If I had more time, this would be like a full Tony Hawk style game where you can unlock skills that way. But, have all of the ones here.
It just randomly put some, like, easy hard sick, grade on here, but I still pulled in all the overview platform tips and stuff. Not as nice as I was, like, hoping to get, but
Speaker 1: Where's the skateboards?
Speaker 0: I know. There is no skateboards.
Speaker 2: I was I I
Speaker 0: I was disappointed.
Speaker 2: I think you've got the beginnings of something. I think this is cool. I think this is a good idea. I think it's cool.
Speaker 0: Yeah. I was trying to go for the most non directory directory type, but, yeah. That's what that's what I
Speaker 1: That's cool. Yeah. This part, I like, man. This looks this looks super nice.
Speaker 2: It's totally
Speaker 1: It's even got the
Speaker 2: Like, I like that they're even floating.
Speaker 1: It's like the the CRT Yeah. Tube TV effect to it. Mhmm. Yeah. I've been lately.
Speaker 0: But yeah. So that's the end. That's AI skills for a skater.
Speaker 1: Yeah. I think it's for a skater.
Speaker 0: Alright, John.
Speaker 1: Alright. Let's see what you got, John boy.
Speaker 2: Alright. Let's do this. I went you know, if you've if anyone's followed me on LinkedIn, I did the whole Nintendo theme garage inventory. So I kinda kept it Nintendo themed, and I went with Duck Hunt, although Skills Hunt. So you come here and you you shoot the little you you can't hear it or maybe you can't.
There's little noises. There's a little creature down there, and then you can you can view the collections that you've got. You've got a little the only thing I would do is make the fonts bigger. You can see all of these things here. But you can go back to the game and you shoot the little you shoot the skills that you want.
Speaker 1: The dog is So there there
Speaker 2: is noises. I don't think you can hear them, but maybe the recording will show them. But there is noises when you're shooting things, and that's what I did. You got your skills there on the right that you've collected. You've got your skills here, and then you can view what those skills are.
Speaker 0: Alright.
Speaker 2: So, yeah, shoot for
Speaker 1: ask questions later.
Speaker 2: Actual game I already got that one. Damn. I need a new skill. There we go. Bang.
Speaker 0: I love gamifying the skills. Yeah. You can't just get the skills. You gotta work.
Speaker 2: You gotta work for it, man. Anyways, that's what I
Speaker 1: know. Alright.
Speaker 0: I mean, all skill one. Honestly, I think way better than all of us anticipated, at least for for me.
Speaker 2: I mean, we did all of those Friday It's a working game. Twenty minutes.
Speaker 1: Yeah. Very nice.
Speaker 0: Yeah. It was twenty minutes on the clock and mostly fighting with my, connection and react, and John was his master of vibes over there. So
Speaker 2: Master of vibes.
Speaker 0: I mean, if
Speaker 1: I had to speak Does this go to a vote between us,
Speaker 0: or does it does it go to the audience? I mean, I I think it's a good question. Right.
Speaker 2: I think we all know who won this one here internally.
Speaker 0: Yeah. Yeah. Yeah. Yeah.
Speaker 1: As much as it pains me to
Speaker 0: say it, very creative. Very creative. Mhmm. I like shoes.
Speaker 2: I think they're all good. I think they're
Speaker 1: all
Speaker 2: great, dare I say. They need all they all need adjustments, obviously, if you were to move this to production, but I think they were all great ideas in different manners.
Speaker 0: Yeah. And then you combine them all. And that's I mean, I think the best thing is that, like, I'm imagining you have, like, a full team of folks operating off the same like, you like, at companies I've worked at, they've they've always been hackathons. But, like, opening up a hackathon to the entire team to be able to work off the same base set of data, I think, is just the really cool thing here. It's, like, everybody can bring ideas to the table now.
But, yeah, overall, pretty cool.
Speaker 1: Well, cool, guys. I think that's
Speaker 0: about it for this session. I appreciate everybody hanging in there with us. It sounded like if you're just listening to this, it was awful, but, you know, the end result has been solid.