I'm just kidding.
No, I'm not.
I'm just kidding.
And in summary, that's how you can make another 20%.
OK, let's move on to the next thing.
That's how his recording can start.
Yeah, I really appreciate it.
Thank you for the first half, Junauda.
But yeah, so we can go through like,
we put like a prep for prod skill in there,
which was a great one.
So like, not in here, but I think
it's in two other projects I'm working on.
If we go to, I think it's a Novo.
Just jump over here to the dashboard.
We have, I could probably, this is very much specific
to the project we have.
But under Claude, gosh, Chris and Macy just
keep coming in and out.
I'll make sure you guys don't get, OK, skills, prep for prod.
And so you could use this as a starting point.
But it basically goes through and like,
checks file size on stuff.
Like, it does code cleanup.
Checks the role-based access.
Like, hey, did I make sure like, I
didn't give certain people access to stuff
they're not supposed to have.
And I just run that skill right before I commit
or right before I merge.
And it doesn't need kind of like, hacks to it.
And so as I get better at it, I pass it.
And the way you set this up is like, I just gave it
this, I typically copy this entire skill,
paste it into Claude, and be like, hey,
customize this for the current project you're in.
And just like, let it figure out like, oh, this
is a Flutter project, not a JavaScript.
Like, it just kind of figures it out.
And it looks for like, best practices and stuff.
And that way, at least it's got like,
a little bit of a harness to when like, things come in,
they do the skill, and then they go through that.
And if something gets through, then we
can tweak the skill, obviously.
But that way, if like, we're all tweaking it,
let's say for Tribe, and Lucien finds it like,
a new thing we want to check for, or like, hey,
make sure the tests are written this way.
And I just run the skill.
I don't even know what he put in there last week.
I just run it.
And all of a sudden, like, now it's catching stuff, you know.
There is that kind of, yeah, off the recording,
I brought the idea of like, a shared company VPS runtime.
And kind of, and maybe like, we all just like,
we're developing on our machine and figuring out.
And like, this skill thing, like shared company skill,
and we're all like, tweaking your shared company,
it's kind of coming back to like,
we're building the assembly line.
It's like, it's a bit like, blurry.
Like, we each work in our own runtime,
but like, we use the company skills.
Then why not just put it like, on the like, rails,
and like, let it be in the runtime and with the skills.
And like, we're just tweaking the assembly line.
Like, we're not like, worried too much about the code.
Like, a little bit still, but folks could be more like,
we're developing skills now.
We're like, developing the skills and pipeline of Tribe
and another assembly line for like, Tribe Mobile.
So, something to consider.
Yeah, that's great.
I think that's smart.
But those are things just to, like,
I think having a client comms, I saw you sent me this,
we should definitely push this.
Yeah, that's easy lift.
We don't hear you anymore.
Cool.
Yes, we could put this into a skill.
It should be pretty easy.
But it's like, because I think what I'm trying to say is
like, okay, we know all the pieces now, all the ingredients.
Now we need to kind of like, systematize it a little better
and get really good at just like, okay, it's this,
it's this, it's this.
Okay, now it's this.
And we get into the routine.
Like, as soon as it feels like,
oh, I'm starting this project and I didn't make
the task grid or I'm actually kicking off a project
and I didn't even like, message the clients, right?
Like, these are things that we should be so in the habit
of like, oh, I'm starting to work
or I just got something really cool working.
It's always fun to like, share with each other.
But also it's kind of fun if there's certain things that
like, oh, we got this thing working.
Like, we're just constantly giving updates.
And I just got off like, a call.
One of my friends here in Franklin is like,
building an app that's like, a AI inventor app
that does NDAs and like, you can like, create a thing.
And then it's got a community platform.
It's this massive, massive platform.
And they have some developer team in like, Croatia.
They've hired.
And like, it was like 45 minutes of this guy walking
through like, the biggest Figma file you've ever seen.
It just was like, one wireframe after the other
of like, this entire process.
I mean, it's like, it's probably like, a year's worth
of work.
Like, if we were to like, work through something kind
of like, as extensive as like, an X tech
or just something pretty massive.
Um, and just so many different modules, so many different pieces.
And I was just like, man, I, I, this is, this is like how we used to build software
like 10 years ago.
Like there's just one guy, like, here's my designs.
Like, and it's like, he's just walking through it, like one thing after the
other.
And I was just like, Hey, can we like dig into that one screen?
Like there's probably like 50 rabbit holes that you just like threw in that one
screen that no one is talking about.
Like, oh, we'll just add this button and we'll do this thing and like this thing
and that thing.
And there's like hundreds and hundreds of screens that he just walked through
really quick in mobile.
And then he's like, well, I can show you the desktop too.
And he'd like done the whole thing again for desktop.
And I was like, oh gosh, like this is insane.
Um, and so all that to say, like, I think our process has massively improved.
Um, uh, so I just think like what, one of those things is make keeping it very
relational and everything everybody does is like Lucian does this phenomenal job
with Godline bars.
Ira, like everybody, like Veritas, uh, loves Ira more than any of us.
Um, and he can do no wrong.
Um, and same with Lucian and Godline bars.
So you guys have like, we've got really good relationships, I think with, with
the, with each of these teams and a high level of trust.
So I think just keeping that, this is not like we're doing it all wrong.
Let's start doing it right.
I just want to like, I kind of want to be able to like highlight that like, oh, you
guys are actually are doing that very well in this area, but then maybe like,
okay, where else could we be improving?
Like maybe this and this piece, um, and not to like weigh you down, but like to
be able to go a little bit faster.
So if we know like project checklist, we're just ripping through like each of
the pieces that have to happen.
Um, we can actually go a lot faster and know that we're not going to miss
anything.
Um, but I know like what also what I can see, I want to put a little bit of
protection because I think like Ira, a good example, uh, I forget the names of
which, which one it was.
The, the, um, the four, the three week or four week project you did, but like
actually it turned into like five weeks.
Uh, yeah, it was a, it was a project that we said was four weeks, but I don't know
why I decided to tell him it was three weeks and then took so many like changes
back and forth.
I'm hitting it like five weeks.
Yeah.
But like, so like, that's great that you just like took it and made it work, but
like one, there was more work that was actually, there's more delivered than what
we promised originally.
And whether we like knew the work was in there or not, like that's like a shaping
problem.
We didn't, and we, and this is the one I think Luch and you were involved with.
Oh, this is, yeah.
You helped me shape it when Ira was out.
Um, when we got in the conference room and we like did like that mass, that first
iteration of like all of the, um, sending a request for DBQ, things coming back,
providers doing stuff.
We went through like a two hour thing in person with, with Corbett, but that was
like one of the, one of the shaping sessions.
Um, but yeah, there was so much more.
And I think a lot of it could have happened with like you and Autumn or Autumn
sort of testing a feature and being like, oh yeah, but this doesn't exist.
And then you were like, I don't even know we had to solve for that thing.
Like, you know, like, and so trying to one, we can like put some guardrails where
like, oh, I feel like the scope's actually increasing.
We need to like, kind of come back and ask for more weeks.
Um, but also what's, what's actually happening there is you're just working so
efficiently and so fast that you're like, I'll just throw this extra thing in there
and they just get more.
Yeah.
The clients win, you know, this is great.
Ira's amazing.
And I was like doing five weeks of work and getting paid for four.
And at least being like, okay, well at least anyway, if there's a little more margin
where we bump everything up a little bit, cause you're still delivered it.
It's awesome.
But like, like, I mean, and then I had to make the video, why they asked me to do the
video?
I don't know.
I know, like, I could have, I would have happily made it, but you know, well, it's
fine.
I don't know if they, I don't know what they wanted.
Um, but Corbyn was very like insisting on me, you know, being the one to like go
through it.
And I tried to make it short and simple, but I had to go through it in a lot of
detail.
And the more I was going through this and maybe Lucian just for a good old, uh, good
time when you're, you know, having some tea or something you can go through and just
click through this thing.
Cause it's, it is a beast of a, um, and the more I was clicking through this and the
amount of iterations and like edge case things that could pop up, I was like, this
isn't like I tech, I messaged Ira.
I was like, this thing is insane that you built.
Like, there's just so many little edge cases every time, like a new little, you
know, dropdown would open.
And I was like, oh, but there's all these other cases where this could have different,
you know, implications anyway.
Um, it's amazing that you delivered it.
Um, and I think, uh, so I just want to make sure like, Hey, that was like a, we
deliver something insane.
Like there's a massive thing.
Like we should have something and we can still do some of this like retroactively.
I'm not against that.
But I was like, we just need to get a better system in place.
So we're not just like grinding
and just like getting through the weeks.
We can actually pick up speed.
But also I think having a little bit of a,
like a retroact, like a, what was it called?
Not a retroactive meeting?
It's like, yeah.
To like just look back and just have this thing.
You're like, oh yeah, it was four weeks,
but it turned into five.
Like kind of go back and see why it did.
And we kind of all knew it was a big project.
Like when we were staring at it,
we just sort of known like this feels big.
We should have been like, let's just make it bigger budget.
Like it's not, it's kind of hard.
Cause we were like, oh, we could squeeze it into four weeks
and make it nicely fit into March, you know?
But like maybe it is a fifth week
or maybe it's two projects.
We did at least pull the AI fields out.
I think two or three shaping sessions in,
we pulled that whole AI thing out.
So good job for everybody to identify that.
And we like kind of found there's like,
this is actually a complex little piece here.
Let's like pull this out and do this.
And is that a two week now?
Oh, it's a four week.
That's a four week.
Yeah, there was, because well, so it's-
I was like, yeah, it's a six week.
I thought it was one, now it's six.
It's three weeks of work,
but I know there's going to be this like iteration loop
with Autumn and I just want to plug in for that
instead of getting into a situation where I'm working.
Yeah, that's good.
And like, we will work stuff out.
I think even Corbett was like,
Corbett said something like,
oh wow, like four weeks or something like in your comments.
And that was great.
Like you, we finished the framing,
you sent him like a screenshot, like all that was great.
For some reason,
I just simply cannot get Corbett into the dashboard.
Like I have these, I have this super slick magic link thing
where it like sends an email.
You click approve, it's on the screen, pop-ups open.
All you do is hit the approve button.
It says like, Corbett has approved.
And he's like, he sends me like some random thing.
It's like, user data doesn't exist
or something I've never seen before.
And I was like, I'm on like my fourth attempt
to get him to use the dashboard,
but you sent the screenshot, so problem solved.
Yeah.
And he just needed to, and he, you know,
he was like, oh wow, like four weeks.
But I can, like they typically buy three
and they get an extra,
like we typically give them an extra week for free.
So that's like an easy thing from their side, it's free.
So yeah, I think, I just want to keep it moving.
I'm trying to not be in every project as well,
but I think the more you guys can do,
I like, I even, Lance is around again.
He's helping a little bit with some biz dev stuff.
And he's like, cool.
Like, let me know if I can jump in on a project.
And I was like, it's kind of awkward to like be like,
you know, now introduce a person to Veritas
or to God Behind Bars.
It's like, we already have like a pretty good thing
going with these clients.
So, and I, so he's going to just be around
to help with like making sure,
we have some big stuff coming for ProForm
and with Pando Media that could potentially be really big.
So we're trying to make sure we get prepped for that.
But I was like, I'd rather like, instead of having,
I don't think, what I don't think works
is having like a second person leading the project.
Because you guys really like own that project.
And we're doing that really well, I think.
To have like another person in there
who's like trying to project manage stuff,
I'd add that.
It sounds like, it sounds good,
but I'd rather have AI project manage it, honestly.
And you guys direct AI than to like have a person.
Because I think we just drop stuff
between the handoff of two people.
So, and I think that'd be true,
even if like Lucian and I were working on the same project.
It just makes it more complicated to figure out like,
oh, I thought you were doing this.
I thought you were doing that.
And then things get lost, so.
Anyway, those are all things I had on my mind
to talk with you guys about, but.
And the thing you're talking about is like the like comms
and like going over the schedule
that were things that we could improve on,
or that like, if we do like these three things,
we get like the 20%, like I understood
that it's like kind of like in a more consistent comms
and, you know, staying on the schedule,
or is there anything more there?
Yeah, so I think, so I think, you know,
it would be, this would be something
we could even frame potentially,
like everything's a frame now.
Like there's some problems, we're trying to get an outcome,
like where you guys like win with us,
because it's not just better for you if we do this.
Obviously the client, the clients actually,
the clients are very happy right now.
So there's no one, no one's like, let me just say that,
because like no one's like, hey, we were late on something,
or we went over on something,
or I didn't feel like we did a good job on comms.
I'm just trying to think.
Think of it as we think about scale and adding more clients or more projects or more bandwidth to this.
How can we have a system?
So because going late isn't a problem with the client.
In fact, they don't care. I don't really mind.
But it actually does eat into, let's say, and they're all for good reasons.
So I'll pick on the AI moderation stuff because we like when a group integration went over.
But this was like one of the coolest, biggest things we've ever done with Tribe.
So it was like, to me, worth it, right?
Like, I'm not worried about it and the clients are fine.
So I think, but then like now your first half of April is like pretty much eaten up with something we sold in March.
So now we're trying to like, well, how else can we fill that time?
So I feel like there is enough work to go around to where we could fill enough time.
But then it just sort of pushes things down and then it kind of has like a waterfall effect that kicks other things down.
If we had had like a full month and maybe part of it is we don't have a full month booked for you for April.
So like it was like, we'll just push this thing out from March to April.
Wasn't a big deal.
But like, luckily we didn't, we had the flexibility to just like push it into April and it didn't affect any other projects.
So trying to think of like how we do that.
And also I think in general, it's just having more margin.
Like the first time we told them the dates, we should have been like, it's going to be sometime middle of April.
And then if we like get to it earlier, just like surprise them with like, you know, that's it's those types of things.
It's not like really, you know, Lucian really like stick to your deadlines.
Like, it's not that it's like, let's just, Hey, let's just be smart about it because we have a bunch of stuff going on.
And also some wildcard stuff.
Like you're doing, I was in the Veritas, the AI stuff, and you already thought it was three.
We're throwing in a fourth week.
It could probably go, go more if it, you know, who knows?
We don't know.
It's just a lot of unknowns.
So like, let's not like add another project or two to, um, to, to April for him.
Um, and, and if you have like, you already do have, uh, AI fields and then potentially the like plan stuff as well.
They also want that at some point.
So I don't know if we get to that in April or what you're thinking, but we can talk about it.
Um,
One thing I was thinking is you also mentioned, uh, guardrails and one of the ways in which the guard, you mentioned, you know, getting these requests from
autumn.
And I think right, since we have the technology for it, we could make a Slack integration or something like that, that just monitors the, the client
channels for requests.
And when it gets a request, it can compare it to the project and, and determine, Hey, does this fit within the scope?
Or is this scope increase is the process of me doing that takes time, you know, of like, Hey, let me like digest what they said.
Let me look at the, the notion document again and figure out is the scope increase, or maybe it's not, or, you know, I'm not running on all
cylinders at all the time.
So maybe I overlook it and it's only two hours, but I am neglecting the fact that I did this like five times and, you know, uh, but yeah, I think
if, if, if that process could be automated in that way, it can, it can, it's just, it's a bit depersonalized.
So it, we can just communicate to the client, Hey, we have five new requests that, you know, are, have increased the scope to another week.
And maybe they just actually, Hey, we actually want to give this to Nick instead, you know, because we don't want to do the COVID or, or
whatever, or maybe they decide they want to purchase the extra week.
But, um, I think we have the technology to, to, um, manage the scope increase and maybe automate some guardrails.
I think that's kind of, it's a good, yes.
Guardrails for sure.
But like, this is something, and maybe, and I told Lance as well, like as he, he, or I are like in projects, I'm not, I'm not interested in me or
him getting that, like, I want to make sure like you guys are getting like the benefit of his three decades of like doing this project
management stuff, but like immediately when you're like, Oh, it's, we thought it was five.
And now there's like a seventh, you know, or eighth thing that's come in, like immediately, like kind of being able to pull that and being like, Hey,
there's these three things and kind of surfacing it to Corbett and kind of saying, Hey, budget was this, we've got these new things.
I think I can squeeze two of them in, but like this other one is like crazy.
You know, it's going to take another week just to do that, whatever.
Sometimes that's hard and it can feel a little bit like we're nickel and diming them.
But I think what is actually happening is our system is very efficient and it's so fast to just like throw one more thing in that it's like, Oh, that's just a
couple of prompts.
That's like one work session.
We could knock out that other thing.
So it just kind of gets absorbed into the project.
So like.
But then like, you're just doing more and more, like the same amount, that's like not
as sustainable either.
And I was just going to show you what I think does work and what these calls have really
been the last few weeks is just like, hey, here's what I'm doing, here's what Jannat
is doing, doing some stuff.
Claude has a great Slack integration.
This is actually on Perplexity, which is kind of like the open claw version, but I prompted
it with like, hey, what are some important Slack messages I should be aware of?
And then it came back to me with a pretty useful little thing here, like, hey, Autumn
is waiting for this video with a link right there to the chat.
Jannat has sent three DMs, he needs to like figure something out here.
There's high stakes, like I surfaced this thing, like, you know, and it's kind of like
summarized there, it said like, though the post call vibe was, could have been an email,
but the third party, like, it was pretty funny, like how it summarized it a little
bit.
Like you just have it, like, use your computer and look at your Slack.
So this one, you actually have a connector, but if you already are buying Claude, same
thing, just don't, just like connectors, Slack.
Now what's crazy about Slack is that Slack and Claude is pretty cool.
And you can see all the permissions you have here.
You can let it search things, or you can ask for approval.
Like you don't want it sending stuff on your behalf, like ask for approval.
I'm just like YOLO on the Slack.
I got to add some stuff because I played with it.
There's a bunch of like caveats.
First of all, it's like across your whole like Claude account, you know, so it's not
per workspace.
So if you're like working in inside of another workspace that you have, like another Slack
account, you want to connect to, it's like, just like everything Claude is going to be
using this.
If you use the connector.
Okay.
The other thing is like, if you use YOLO mode, these actually don't apply.
Like it's going to like bypass everything and send to the channels directly if it thinks
it should send.
And you said ask permissions or you said deny also, it's still going to send.
Yeah.
I haven't tested this.
Got it.
Okay.
Thank you.
Yes.
So it depends on how you're using it.
Test it.
Like you can send each other DMs or, you know, one thing you can do as well, which is kind
of cool is you can have it write a draft for a message.
So it's cool.
It like sketches it out and puts it in your input field of Slack formatted or whatever.
And then you can open it in Slack and just like tweak it and hit send.
Try that as well.
I don't know if you've tried that.
I have on occasion seen it do a draft when I actually wanted to send.
So I took Slack off of my phone for a quality of life upgrade.
You can do that too.
But my only thing, and I don't mind people like being inaccessible, just have one way
on the rare occasion that if we do need something, so Macy knows she can like text me if she
sees something crazy.
My phone number is in Slack anyway, so you guys can all text me in like worst case scenario,
something's gone down.
But I sent, I went to Claude on my phone and I was like, Hey, send Macy a message with
like this, this, this.
And I could have sent some of you guys messages like that where I'm out for a walk or something.
And I still want to just throw something to you guys.
But it's nice because it's all one way.
Like I can't see if you responded.
It's very, it's a very calm way.
It's kind of like sending an email.
It's just like you just send it into the abyss and you don't get that immediate dopamine
hit of like someone liking it or responding.
So it's actually kind of a cool, calmer way to like, it's just like putting the message
out there and then just not seeing the response and then I'll come in a few hours and check
it and see what you said back.
But yeah, that's, I was just showing you that, Ira, like perplexity, like I'm very impressed
with perplexity.
It's kind of the sweet spot.
I know we've gone in all these circles of like open claw, paperclip, my paperclip totally
had a meltdown over the weekend and I'm still, still not been able to revive it.
So yeah, you end up paying with time or money.
So like this one's been like the type of tasks.
So I also, I had a, if you guys remember Z who did the training with us when you guys
were here, I helped him set up, he was like, Oh, show me, show me like paperclip.
Like I was talking to him about it.
Like I talked to everybody about stuff.
He's like, he's like, I got, I can buy you coffee.
Like sit down, show me this thing.
Like I got to figure this out.
Like as a, as a business owner.
And I was like, there's no way I'm sitting on paperclip for him.
Like this is, I'm just like going to be a, his tech support now moving forward.
So we set up perplexity, it's 20 bucks a month.
And he like, he like totally rebuilt his website in like a pretty sick website that he came
up with.
His website was terrible.
like he had spent thousands of dollars getting it built
and he's been trying to change it
and he's trying to like hire this guy in Fiverr
to change something.
It's all in Squarespace.
He never did.
And he like, basically like vibe coded this in perplexity.
And he's like, cool, I got it finished.
Like, what do I do with it?
I was like, I was like, stop, why are you asking me
like what to do, like ask it what to do.
And he was like, he's like, it's saying
I need to set up a GitHub account.
I was like, do it, like go set up a GitHub account.
It's free.
And I was like, they're like,
it's telling me to set up a Netifly account.
I was like, well, use Vercel.
Like that one's free and I know it really well.
And I left him for like two hours
and then he like texted me the link.
He's like, it's live.
And I was like, I mean, this guy's not technical at all.
Like I showed him chat GPT initially.
I've showed him all the tech stuff.
And he like basically built a website,
got a GitHub account, hooked the GitHub to Vercel.
And now he's just, when he wants to make a change,
he just comes in here and like prompts it.
Like, hey, I'm launching a new product.
This is my new pricing.
Boom, boom, boom.
It like fills it all out, publishes to the web.
And he's like, and then, you know, he's prompted it.
And he's like, hey, fix my SEO.
Just like fixes SEO behind the scenes.
And it does things like I had it pull,
like I was like, I told it a little thing like,
hey, go and grab the transcript
from the latest live stream that we did here.
And like help me write some posts for it
that could go out on X.
So it went and like did a bunch of stuff
and then came back with like the key topics
that were covered.
It grabbed the text, you know, stuff.
So just sort of like figure stuff out
and goes out to the internet and does various things.
And yeah, I think that's pretty useful.
I connected zero.
So it's like all my accounting's in here.
You can connect your health app, like from Apple.
You can connect Superbase directly, Vercel.
I mean, it's insane like how much is just like one click
away from being set up.
So this is like the easy mode.
If I'm introducing someone to like sort of the agentic,
like automated sort of tools, like an open claw,
this is great to start.
It's still using Sonnet.
It's still using Opus, like in the backend.
This is, it is expensive though.
Like this is, you just rip through.
Oh, sorry.
My cat just tried to swipe my baby.
That was so, so fast.
Sorry.
No, you're good.
I would have done the same.
But you can see like how fast it,
you only get 4,000 credits for the month.
And this, this like, I only have 165 left
and I only use it for two days.
So you can bump to like the $200 a month plan,
but still, anyway, so it's more expensive basically.
And you can see how many tokens,
like what they call credits.
I don't know how this translates to tokens,
but you kind of, you pay the price for it to be in easy mode.
So anyway, they do have something different.
They have a thing called spaces.
So you can have like specific,
like something that's more private.
I don't know how this would affect what you're doing,
but I think you're saying on the Slack workspaces,
it's access to all Slack.
Is that what you're saying?
Yeah.
So, but we'll like, we'll keep tweaking the tools.
I think what I'm trying to say is like,
we're close enough where like,
with just a little bit of like processing refinement,
we can all just have these little like,
oh, let's do a client update in my day,
or let's do a client update before the meeting
and get into some like, just making it super easy.
Cause part of the thing is like, if we have an update,
like we're doing a call this afternoon
with a new client that Greg is working on.
And last night he sent me like a full demo
of like the whole feature working.
And then I was like, great,
can you send that to them this morning in a loom?
And so like, they're going to see it this morning.
They've already like thought about it, talked about it.
Now we're going to get on the call
and just talk like review some feedback
and then talk about the next project.
So we've kind of, we've made it so much less stressful
for me and for him, to be honest,
where he's going to basically come in as the hero,
like delivering something early.
So anyway, I think if we can get some of these things
working again, all this stuff is working pretty well.
I just want to like,
like I think we can put like a little edge to it
with all the AI stuff.
And then you guys can figure out whatever tools
you want to use to get there, right?
It doesn't have to be,
I don't know if we're going to necessarily build it
all into the dashboard yet.
I don't think we're quite there yet.
Like where there's one bot that's like reading updates
and just taking stuff and like sending it to the client.
I don't think that's going to happen just yet.
We're keeping the human very much in the loop
on all that stuff in the meantime.
So we just like keep adding like skills instead of,
cause I have like my own skills.
just I don't feel like like production ready. So we just
like, keep committing skills and like, update the committed
skills and use those as we go. I'd be like, yeah, energy,
however, you want to do it. I mean, I'd love I think it'd be
smart to share, share stuff. Like, if something's working, I
asked, like, what?
Jonathan was using one recently that was working really great
for comms. He says he was just using the case GPT. But I don't
believe him. I think he's got his own fancy skills for his
comm updates. But yeah, something like that, where we
can, there's some general ones, right, that are like, framing,
shaping, client updates, that kind of thing. But it'd be
great if you could import the skill for like client updates,
and I'll keep them in the repo. So like, I ran your Veritas repo
just have the skills. And one of those is called like a VR client
update skill. And it you can program it knows that it's
Corbett, and it's autumn. And it's like, these are the roles
is who's who and like, we know that knows we're meeting every
Tuesday. So whatever, it can like, be a little bit smarter,
like you can kind of customize it. But I've been really
reliant on these, these skills with Claude, to where it does
create a little bit more confidence just to like, and
it's so easy, like to just like, I'm doing a bunch of stuff. And
then I wanted to write a blog post or something with a new
feature, or if we wanted to send an update, the other thing, if
you have things in tasks, so if you're using the MCP stuff, and
you're pushing stuff into tasks, and then like, here's my task, I
bring it in, I work on it, and it updates the comments and
stuff. And then you have a project, you can just highlight
four different notion links. And you can give that to your at
whichever AI bot, and it will all say, hey, summarize these
like four tasks for me for a client update, and then it will
go and read all the like context of those four projects, those
four tasks, that you could use the task grid for that, or you
could use the the task in notion. So that's what I've
been, when I've been doing detailed work, I typically have
it set up the project, and then I use a project, then I'll have
it put tasks. And that way, I can kind of visually see the
Kanban board, but then sort of moving through the pipeline. And
then I'll just select them all, copy the links, and then paste
the links to cloud code, and it will use the MCP as far as, as
you know, because you know, the Innovo dashboard, MCP, the best,
could we make a skill that just tells it like, a get like
today's updates of the task grid, and today's updates of
the tasks, and the GitHub recent activity, the dashboard, MCP
expose those little properties?
It's just so the MCP is just API endpoints. So we could create a
MCP API that just says like recent progress or recent
activity. And it could be like, oh, like Luchin closed this
task, Bruce did this, this comment got left. That'd probably
be the easiest.
And you can do like, you know, variable, like, that could be a
query param, like, because the whole like last week, you've
been like, or like, just today, that could be like a good tool.
That's good. We'd like just commit in each like repo, like
this same skill or small differences.
Great. That's awesome. I'll make a note of that. I did do the
real time task.
I would use that all the time. I'm like making updates to
clients could be more.
You want to frame it as like, a recent activity or recent
progress?
Because I don't know how you store the like task grid
properties. Maybe the item is a row and has like a data. So
anyway,
yeah, would you would you frame it as like a recent activity?
Recent progress? Okay. Yeah, I think that's added.
It sounds even better, because that would take an account also
shaping like, oh, we clarified this scope, you know, we created
this
slide brain changed. Yeah. We every there's a massive log of
everything, of every MCP call and stuff that goes in for every
project right now. So I've kind of like overdone the the logging.
So, yeah, I think if we just took like a summary of that, and
it could just be like, you know, I think we frame it as
like activity, like, hey, here's what has changed, like, you know,
and maybe, or maybe it's got some status as well. Like, hey,
there were there were 10 tasks, Lucian's done seven of them, and
there's three remaining like that kind of split. I'll play
with that. That's, that's good.
Kind of like an, like a status or like an update.
Um, cause then we could probably standardize it.
I think that where you're headed is like, it can be a little bit less.
Yeah.
It's just like the one time thing, you know, like the, the data flowing of
the dashboard and then when just like each repo tweaks, it's on like
cloud scale updates, but, um, yeah, I guess the tasks, the smartest way to
do that would be to have the tasks in notion and you're working kind of
through each ticket like that, or you have them in the task grid, but of
course, if it doesn't have any of that, then it's just like flying blind.
But potentially it could be good enough to just have it pulled a
frame and task grid and commits.
And then it will know it just, I think probably that would be 99.
Good.
Yeah.
That would be like a combo of like dashboard MCP and then in the skill itself.
So.
Yeah.
I wrap we're about to dinner.
We're done.
We're just chatting at this point.
Yeah.
Just jamming.
Um, yeah, we don't.
So that's the thing is we don't have the, we don't have the commits or the GitHub.
Um,
No, no, no.
But you have it locally, like your cloud.
Oh, that's right.
Yeah.
Sorry.
That's right.
Yeah.
I've over-complicating it.
So yeah.
So we're just going to tool call the tasks, framing task grid stuff.
And then you would just use like, maybe, so one thing we can do is we can program
it to pull, um, whatever the local, like we can, because you can put a little
bit instructions in the MCP side.
So when it gets the status, it says like now for all gets use the project you're
in and use the repo or the branch that you're in, you know, just a little single
statement like that.
So it doesn't try to go and do more than it needs to.
Perhaps that's an interesting concept.
You put the, um, instructions like in both sides.
So it's kind of like, it's getting driven from both sides, like the local
skill and the dashboard MCP are telling it.
Oh yeah.
Cause you're saying there could be conflicts if like changes in one, but
it doesn't change in the other.
So I'm leaning more of like putting it only in the skill.
Like MCP just delivers the information is not prescriptive of how to use it.
Later.
Yeah.
Or yeah, if it's just in the MCP, cause then you can kind of just like take my
little MCP account to whatever project I want and it, and know that it's got
access to these, like a Novo skills that are sort of private.
Um, yeah, that's interesting.
Cause yeah.
You have a way to expose like the skills from the novel dashboard or it's my
mind.
It's just like per repo is the only possibility of like, it's.
Yeah.
I mean, it's in, um, it's in like, uh, there's like an MCP that I'd have to go
find it now, but like maybe it's in the, uh, maybe it's API.
I think it's API MCP.
Um, I've never like used the, the, uh, here it is.
Yeah.
Um, so there's just one file, I guess here, I guess it's pulling
from some other places.
Uh, but yeah, I never used the like GitHub UI.
This all looks so strange to me, but, um, I'll, I'll pull it up a bit
somewhere in here.
It basically has like the, the URL for that, um, like each of these little
tool calls and so that, yeah, you can wrap like some of the tools have, can
have like more, more with it.
Um, so I'll find out exactly where it is.
Oh, and then there's the CLI, which I've not really like, honestly, I haven't
used much.
Um, I haven't really found a use case for it.
I thought that was going to be like the thing that fixed everything, but I
haven't really,
Gennaro's thing was cool.
You know, his, uh, what was it?
Hermes.
Yeah.
Right.
That was cool.
Yeah.
And you can, I think Hermes is open source as well.
It's another like paperclip.
Yeah.
He, he forked it from a ant farm and that's open source, but then he
customized it.
Yeah, that's, that's cool.
It's, um, definitely does.
Uh, are you still using paperclip?
Uh, yeah.
I also had like my own little kind of meltdown.
It was like, it started getting to getting into like a loop of like, it's, it's
not deterministic.
Like when a task, you like create a task, it actually loads the paperclip skill.
And then like does an MCP call to like paperclip issues.
And it's like, at some point it got into a loop of like, Oh, my token.
doesn't work, let me go read the paperclip source code in order to see how to like, go
like takes like I measured it took like eight minutes to like actually start doing the task
work.
You know?
Yeah.
It was just like doing a paperclip.
Yeah.
It's too much tinkering.
Like mine, uh, I asked it, this is, and this is so dumb.
I was like, I tinker, it was fine.
And then I like played with it and I was like, Hey, I was just like in, I went VPS, like
Claude at the root.
And I was like, Hey, I've been running paperclip for awhile.
Can you just like make sure that like, I was like, just wanted to do like do a little audit,
make sure that things are like working as they should.
You know, I wanted to make sure we weren't like blowing up the CPU or whatever.
Or should I upgrade the CPU or whatever?
It comes back and it's like, Oh yeah, there's a, there's a process, a Claude session that's
been running for two weeks.
That's completely consuming a hundred percent of your, uh, CPU.
And I was like, what?
You know, I was like, and I was like, are you sure this is not, um, paperclip?
And it's like, no, this is like happy coder tool, which is like a, it's like terminus.
That's like a, like a symbol, like a, uh, app for coding from your phone.
And I was like, Oh, I tried it and deleted it.
And it's like, Oh no, this is like happy coder thing's been running for two weeks.
And I was like, Oh, kill that thing now.
So it kills it.
Then it was like, also you're, um, running off a dev build of paperclip.
Like it just did a little quick dev build to get it going.
And I've been, I was like, if you want to, we can like do a production build and this
thing will run a lot faster.
And I was like, well, yeah, for sure do that.
And so it does that, gets it running again.
And then it starts running into permission issues and it's like, Oh, you can't use like,
you know, dangerously, you know, permission thing as root that's like built into their
thing.
They don't want to let you do that.
I was like, no problem.
We'll just make a new user called paperclip.
And then like all the issues just opened up because like every single file that it touches
is now like needs to, has to have the permissions change to work with root and paperclip.
Oh, I got, I got the, the thing for that.
You just put them all in like the pseudo group and it's like pseudo, no password.
You're just like every day.
I mean, I, I should, it's gone in like it's, I've wasted so much time.
And then like this all happened on Monday morning and I get this text from Z and he's
like, Hey, do you think you can meet at 11 and show me like paperclip?
And I was like, no, like I'm not showing you this.
Like I don't want to, I don't want to see paperclip for a while.
So anyway.
But yeah, Jannat is like so on point, like this is the mental model of someone else.
Like they can debug it.
No problem.
Like they're like built into it in their way of thinking.
Like I, so I'm thinking I may use something like perplexity as like my like automation
stuff and then still have the MCP with the company.
And then I just, cause you have to like organize yourself first and automate what you're,
you're doing and then kind of plug into all the other stuff is kind of the flow.
I think we're not going to have like an Enovo paperclip that we all sign into and like do
stuff.
That's, that's never going to work.
Not for a while.
Yeah, for sure.
I think we're a ways from that.
But we could expose, I don't know, I just, I'm obsessed with this idea, like expose like
little like tools, you know, or like there's the, I found the droplet there.
It's called Claude Dev.
It's in the.
That's mine.
That's my.
All right.
That's, that's where my paperclip is.
Don't, don't follow that up.
You said it was called Enovo and I was like, it's not an Enovo.
It's yeah.
Claude Dev is my, is where my paperclips running and it's also my virtual, I do everything
on one.
It's my virtual.
I'll just move it from the tribe social project to the Enovo studio.
Is it not?
Oh, is it in tribe social?
Yeah.
Well, there we go.
So yeah, I, and that, that's been working great.
Like I, I pull stuff down.
It's got full GitHub, everything.
I do the run Claude dangerously on there.
Yeah.
On the VPS is great.
I'm learning that people do it like on like a Docker thing locally.
And so there's like stuff to explore also, but it's really nice to like dangerously skip
permissions.
Yeah.
So I, I like, I did the live task real time database thing with the tasks and it worked
in 15 minutes.
Like I started on perplexity.
I just like, I was like, Hey, can you go ahead and frame this up?
And I always have it like put it in the plan folder, put it in the, in a branch.
And then I just pull that up on my machine and I was like, could go execute this in dangerously
mode.
Perfect.
It worked.
It worked within 20 minutes.
I just left it for a while.
Came back.
I said, don't, don't stop until you're done.
I'll come back in the QA at the end.
Like just go, like go for it.
Worked perfectly.
Then I spent like an hour and a half just trying to get the like live editing things.
I was like, no, how cool would it be if like Lutron's editing this thing and I'm touching
this.
So then I could see like Lucian's editing this
and I'm editing that
and you can kind of see people like working on it.
I was like, that would be so cool.
And that's what took like so long.
It took me like an hour and a half to get
in circles for that, but it works.
I don't know if you've tried it.
It's supposed to work.
I just saw your GIF.
That looks awesome.
I didn't try it yet.
But like, if you go to like, I don't know,
April management.
So.
Status is wrong.
So they're ready.
In the test group right now.
Oh, that's cool.
There you go.
You can see a change on mine.
I like the logs, the MCP logs is going to be like,
Lucian added, what's up?
But this would be so cool if we're like on a, wait.
Yeah, y'all like for like collaborative sessions.
I think it just added it twice that it did.
I wrote second slice and it put it in there twice.
I like ship fast, break things, that sort of thing.
You know how it is.
But it's like, now.
Look at, I already broke it.
Do you see what's happening on my screen?
Yeah, yeah, I reported you like another like little issue
when in the, you know, when you create it.
That's weird things.
But now they're like agents do our task grid.
It's like, are we even gonna be collaborating in it live?
Yeah.
But what's, I think we do need, there's probably like,
we could probably flesh this out
because Notion has infinite amount of space to write things.
And this is so limited.
We almost need like, you know,
we've talked about each of these
becoming a Notion task as well
so that you could go a layer deeper
because it would be nice if like,
it kind of worked its way through these
because it needs more context than take,
go grab this slice of like set up off.
And this says like, set up Google off, set up super base.
You know, like these are going to be
very high level little tasks,
but each one has a lot of.
I'm gonna go back to like my,
cause I think that would be a great feature.
Just like allow like pasting link, you know,
how in Notion you can highlight a text,
paste a link there and it becomes like a link.
Yeah, we could do that.
Cause like some, otherwise like,
cause I use the like task view sometimes too.
If it will be like flooded, it will kind of.
We could, we also could have another thing
where if you just tap,
like if there'd be a little icon or something,
dropdown or something for this task,
that's just like open in Notion.
And it just like makes a new task in Notion
that's linked to this one.
Cause that's, they are the same thing in the database.
There's just one thing called task
and the task could be in a grid
or it could be in Notion or both.
It's a three way.
Right now your data models like task
is a thing with optional Notion ID.
Yeah.
Oh, then just plug the two that's.
Yeah, so I was thinking like,
but if you were in here and I wanted to be like set this
or when we click up here and you're like,
create these, all of these tasks,
like make, move this to Notion essentially.
So I could like move them all into like dev ready,
you know, take each of those as a new task.
And then it's kind of stupid though.
I don't know.
Like, I just want to give a weight for,
oh, so here's the crazy thing is,
okay, this is way too complicated.
We don't need Notion.
We don't need Notion at all necessarily.
Like the, this is a task
and tasks have a thing called content.
That's where all the stuff goes.
Like all the notes and all the comments go.
Those are all in super base.
It just also pushes it down to Notion.
When you use the MCP, it writes it all to the task
and the task pushes it back down to Notion as well.
So behind each of these little things right here
is a whole, the depth is there already.
Like the comment ability for comments,
the ability to assign this to someone,
the ability to put, like,
you could even have like click on this
and it could open up a little like modal
that has like the whole details of that task if you wanted.
So I'll play with that if we wanted to basically like,
the thing would be like adding detail,
like to a task or a task so that like,
you could put context for,
because then what you could do is you could build
a task grid and you could tell AI, like,
hey, go MCP, like go flesh these out,
like write instructions for each one of these tasks.
And then I could click through them
and watch them being done and be like,
okay, go execute on the whole of slice one,
you know, just rip through each one.
updates the status and it makes comments on each one as it goes.
I'm wondering, I'll be a bit, I would say black hat.
Like, do we run into like bottlenecks where this would help? Or are we kind of like
doing like solutions to? Well, the, my thing is like task grids are too
um, brief. They're not enough context for the AI to like see stuff. Notion's great because I can
create a task with like a lot of instructions in that one content. And so I could say like,
hey, I'm fixing this. Let's say a bug is a task. It's going to write all the instructions of what
it wants to do, execute on it. And then when it's done executing, it leaves a comment. So it's that
like bigger scope being captured. You're helping me see like another piece of it because
uh, usually it's, it's enough if I tell my cloud, like get the framing, get the task grid.
And I do like shaping and like system design pass, but then I save it to like a local file.
And our gap now is like our shaping is actually, our process is to do it like manually in like a
Figma. And that's not like really navigable. So maybe we can just add like that intermediary
step because I think the agents are like probably going to be more than competent
enough if they have like frame shape and task grid and you tell it like do the slice.
Yeah. We could try that. I think like, also it depends on the project. So like this is one
obviously this is just a bunch of dummy. And that's like my workflow. I'm kind of.
Yeah. So like I was doing this, which this is like kind of a monster project,
but I'm using a task grid for it. So like this was launching a new client. And so my
like a whole slice was just content migration for this client. Then me was building this whole
view. So like create a new directory, like mock up the library state, like create collection
components with API link, like conditional only for uplift, like anywhere where I ripped. And
these are all my notes as far as like how I thought it needed to get done. And then I kind of,
like you said, I pull all the context down and I would let it create a plan locally in the repo,
you know, for me to read. And then I would look through the plan and be like, yes, do it. And
then just go off. But if you're getting towards like the code factory thing where you're like,
having it create all the tasks and all the instructions at one thing, and then you can
kind of review all the instructions, you just like you put the whole stack of tasks like in the
dev ready, and it just starts to like process those top to bottom. That would be kind of cool.
Um, but I'm not quite there yet to where it's like, drag all these things over.
Yeah, the notion thing sounds more like for human navigability. Although I don't know if it's needed
like to be able to like, expand like a single task and take like a lot of notes. Let me write
like an escape hatch thing. I just like create a notion thing or like a local plan for a single
task. If it's like bigger. Yeah. Like shaping, like saving the shaping the system design.
It sounds like there's good use case to put it in the dashboard.
Yeah, I think I'll just see the the where the CLI stuff came from was the ability for like
one coding agent to spawn additional coding agents for each, you know, task or to work on
stuff in parallel. That's I'm not, I'm doing parallel and like the dumbest. I'm like literally
have like two or three, some I sometimes have three VS code, like windows open. And like each
one has two different cloud instances running. And I mean, it's kind of dumb because like you get you
get really bad. Like I was doing that I said an hour and a half like for the agent thing, but I
was working on the uplift webs thing at the same time. So we merged a map like a massive update
into that which worked great. Like we took everything Leon was doing with the AI. He just
left. But yeah, Leon stuff, all your group integration stuff. And then like all the
uplift things kind of all came together. Because they have this like custom home screen thing that
they wanted. And this custom AI stuff. So we did some pretty big upgrades to it. But
luckily, it all connected. Great. Like I was able to I kept pulling in your changes into my branch
and then fixing stuff. And I put my first
free, my first private feature out. And I was like, going back
to your video last night, I was like, I know Lucian send it
somewhere. And I was like, trying to like copy exactly. And
I was like, I added the thing added the flag in the, you know,
it was there was a required flag added it there in the database.
And it worked. Works fine. So it was great. And then the only
thing that was missing was like, there was not really a very
clear instructions of like how it got set up in the, in the
Flutter app, specifically. So I finally figured out like, where
because it was like, oh, I added it. And of course, it didn't
work. And then it was like, oh, there's actually like four
places you need to add it in like the bottom nav in the
whatever. So yeah, I added a skill that says create new
feature, create new tribe group feature or something. And so you
could use that skill. And then you just tell it like I need
this with whatever, and it just kind of makes the new skill.
What I should do is put that at like the master level, and then
I can do the CMS side and the thing at the same prompt. But
yeah, yeah, that's an interesting one day. Other
challenge, you know, like how to structure the
got to merge. Every call is gonna be
potentially that could be like super easy thing, you know,
a directory called CMS directory called Flutter.
Yeah, we're just like, what we have like tribe social right
now, just in there exactly that just one subdirectory called
like mobile.
I think it's great. I'm down with that.
One prompt away lotion, you could do it.
Break like
question of pride, I wouldn't even prompt I would just like
grab the thing, put it all in manually just to prove that it's
like a one shot.
Because the Yeah, I do think that's the right way. Leave the
CMS where it is. It's also cleaner. It's less, you know,
it's connected to more things as well. And then actually, it's
like a sub part of Yeah, you would go to Yeah, it makes
sense. And then you would go to like,
because I think having the skills merged now at the top is
perfect for this. We're like, I need to add some stuff to the
CMS, I need to add some stuff to the Flutter app. And also like,
we could have some skills that's like start my dev environment,
it could like spin up local here, spin up this and connect
the two, because that's also a pain to like, I have like dev
config. Yes, change it to local. I started doing something like
that. Because when I set up my VPS, I started thinking a lot
about like, how do we just like safely allow like YOLO mode. And
like emulator as the way like just like local Firebase thing,
like no Firebase project. Because right now, like if you
want to be developing, you get to connect to prod. And I made a
work on the on the VPS that seems seems to work fine. Maybe
I'll merge maybe I don't know if they'll break the the like code
magic thing, the deployment.
Yeah, I said, we just
but this is like the kind of thing that I feel like the team
should be like working together on this team is on it where you
and me right here. Let's decide it.
Okay, emulator. I vote. I say we do emulator for like local
dev.
Yeah, I haven't tried the emulator. I do think like things
we know we should do just need to like do is the like bring the
mobile app in mobile directory. That's like, I don't think
there's anything that would break anywhere. I think we go to
code magic and you update to where you know the repo that
it's pointed to. And that's it. Everything because it record
magic manages all the deployments everywhere as long
as you fix code magics reference. We're fine. And then
you know, we may have some steps. And then I think just
having some automations where like,
oh, the other so I think there's two big things like merging the
code is one big thing. The second thing I think is having
like all those century stuff set up. And then we can have like a
little bit more of like, peace of mind that like we just push
some stuff and then you know, it can catch it's not gonna say
that's the thing. It's not gonna really catch like the flutter
side. So it's one it's one sided.
Yeah, but that's that's like a deep thing. You know, like just
continually improving the harness. Yeah, like we run all
of the proper things before each commit.
I did do it for the dashboard. It was like maybe two hours. I
just prompted it to go and like it uses the century MCP. And
it just went back and forth and like checked stuff like oh, I
see you haven't even enabled back end stuff. Okay, you
haven't enabled this like you never know that. And it just
turned out I was like, let's turn everything on and give it
is because it did stuff like the slack tracing and all kinds of
stuff that it put into the code. And it's a very small
I mean, you have a lot of users, but I was like,
surely we could get more out of that.
So we'll see.
That's true.
I started going down out there and I was just like,
I started too many things.
I'm like, how do we like interface like God band bars,
like a flag environment thing?
And I was like, ah.
Yeah.
You'd have to like probably filter God band bars
on all of that.
I think we-
Yeah, yeah, for sure.
For sure.
Maybe just, I would just keep, yeah,
because I wanted to do like something smart,
like, okay, tell me like the dashboard issues only,
just like admins, but like skip the API.
So.