My PRD Thought Process to Create Better AI Coding Results
April 11, 2025
Parker breaks down how to craft effective PRDs for AI-assisted coding, how to run a focused planning session with a technical product mindset, and how to turn that plan into real, shippable tooling using a starter kit approach.
PRD fundamentals: what, why, how#
- Core idea: a modern PRD for coding with LLMs combines what you're building, why it matters, and how you’ll build it.
- The simplest version:
- What: the product or feature.
- Why: the customer/problem you're solving.
- How: the plan to implement (with real constraints and decisions).
- From problem to solution:
- Start with a clear problem statement (not a list of features).
- Define the solution at a high level, then identify no-go constraints and “nos” to avoid rabbit holes.
- Include open questions to capture missing context before coding starts.
- Roles to remember:
- Product Manager vs. Project Manager distinction matters for PRD quality; the PRD should drive what and why, while the architecture guides how.
Modern PRD with LLMs: process and collaboration#
- Two-people dynamic: mix of product thinking (what/why) with technical depth (how).
- The braintrust: a technical product manager plus a 10x engineer-like perspective to challenge assumptions and force corner cases.
- Structured thinking tools:
- Mental jousting sessions to surface landmines and edge cases.
- Five whys to keep asking why a feature is needed and what problem it truly solves.
- Domain-based architecture mindset:
- Start from data and domain needs, work up to UI.
- Gather data points, define data flows, then map to frontend components.
- How to run it:
- Build a PRD workshop, expand prompts to capture all details, then compress to the essentials for execution.
Turbo Kit: a practical starter kit for newbies#
- Goals: make it easy to go from training wheels to a real app with AI help.
- Stack concepts:
- Database: Supabase (DB + API layer).
- Data fetching and API patterns: simple Next.js approach (with options like TRPC).
- UI: ShadCN for rapid, consistent components.
- Practical add-ons:
- A chat bot in the PRD to answer questions and keep the team aligned.
- Clear scope management to avoid feature bloat or scope creep.
From idea to PRD: concrete structure and example#
- Typical PRD sections to fill:
- Introduction / pitch: a tight problem statement.
- Goals and success criteria: what “done” looks like.
- User stories: who gains value and how.
- Functional requirements: what the system must do.
- Nonfunctional requirements: performance, usability, compatibility, etc.
- Design considerations: UX and technical constraints.
- No-go / out-of-scope items: explicit boundaries.
- Open questions: what you still need to answer.
- Example: custom cursor feature
- Goals, user stories, and a concrete set of styles and hover behaviors.
- Asset handling: SVGs as reusable icons, with a plan to export and reference them cleanly.
- Implementation notes: how to wire icons into your components, how to pass className props, and how to store preferences (localStorage).
- Outcome: a PRD that not only describes the feature but also gives the AI a clear boundary and the questions to resolve.
Workflow: expanding prompts, compressing, and automating#
- Expand-to-brief workflow:
- Start with a big prompt describing the project, then expand into detailed PRD sections.
- Use an agent to answer questions and fill in the draft PRD.
- Compress to essentials:
- Drill down to the “juice” that actually guides implementation.
- Remove fluff so AI focuses on concrete tasks.
- Task execution with Taskmaster:
- Parse the PRD into actionable tasks via the Taskmaster CLI.
- Get a structured JSON of tasks, dependencies, and next steps.
- Practical payoff:
- You get a reproducible, automatable path from PRD to kickoff to delivery.
Real-time coding flow: building assets and integrating with the PRD#
- Asset work (example): creating and exporting SVG icons for the custom cursor.
- Component wiring:
- Export icons as React components, accept props for styling (className, SVG props).
- Centralize icons in a single module (icons.tsx) for reuse.
- Tailwind and globals:
- Plan to extend Tailwind config for custom cursor classes and map them to SVG assets.
- Use relative paths to keep PRD references portable.
- Outcome: a reusable, scalable cursor system that can be dropped into any page with minimal friction.
Energy, process discipline, and the path to automation#
- Musk’s five-step approach (adapted): do it manually, then cut steps, then go faster, then question steps, then automate.
- The current reality: push through the hard manual work first, then automate once the workflow is proven.
- Practical takeaway: don’t automate first; ensure the manual process is rock solid and repeatable.
Community, next steps, and calls to action#
- There’s a Discord community for rapid feedback and automations.
- For deeper dive, check the main channel’s content (the Cursor/PRD workflow is explored there).
- Expect a Turbo Kit update with deliverables, templates, and a ready-to-run starter.
Quick actionable takeaways#
- Always start with a sharp PRD: focus on problem, then solution, then explicit constraints.
- Use a structured, collaborative workshop with a technical mindset to surface edge cases early.
- Pick a minimal starter stack (Supabase + Next.js + Tailwind + ShadCN) and build a chat-assisted PRD to keep questions flowing.
- Convert PRD to tasks with Taskmaster to avoid scope drift and accelerate execution.
- Build reusable UI assets (SVG icons) as components with flexible styling to maximize reuse.
Links#
Transcript
in Parker Rex. I led tech for a start that sold for 23 million bucks. After that tried Airbnb for music, didn't work out. And then I went all in on programming. Then Chacht came out, changed everything. I've been doing it literally every single day, turning away all their opportunities to figure out how to leverage AI across programming, marketing, and business in general. So on this channel, doing a daily upload. And I just realized I'm not having as much fun as I was before. So, I'm like, whoa, wait, how do you make it fun? And I realized, oh, it's when I actually build stuff, not just like yap about what other people are doing because I don't want to do like a news channel. So, we're going to do some fun stuff. Let's rip it. We have uh this thing. What are you looking at? You're looking at tomorrow's video on the main channel. That's right. I have another channel and it went a little something like this. I made a bunch of content in like 2020 and it was all like product managery stuff and I don't know I got like really sick of it. But tomorrow we have how I made cursor 99% more effective. Taskmaster is goated in 2025. It's true. This thing is absurd. I was literally sitting eating a piece of toast trying not to get butter on my keyboard whilst this Taskmaster thing just cooked. And so I just wanted to call that out. In this video though, I want to talk about Turbo Kit. If you're not familiar, I told the audience that I was putting together a starter kit that would be really easy for noobs because I keep seeing this problem that happens where people go from the training wheels. Goodness gracious, what's going on? Oh, that's why they go from training wheel apps and it's it's not supposed to be a derogatory thing. It's just like I just call it that because you have to take the wheels off when you go to an IDE like cursor which still is like kind of training wheels if you think about it. It's not like Vim. But what I keep seeing happening is people go from Lovable or Bolt or now Firebase Studio, which by the way, check that out. It's nuts. They go from this and then when they try to get over to cursor or wind surf, they're used to seeing stuff like this where it's like they have like their chat and then it's just the app and it's like, whoa, this thing's sick. But then when they flip from one side to the other, when they click that button to see the code, they're like, "Oh my gosh, what's going on?" And so they're stuck here, right? And you got all these sad people. So anyways, I just keep seeing that happen. And I also spin up a lot of projects. So I wanted to cover the bases of it. A lot of the starters are tricky and this will include superbase which is DB a DB. You basically always need a DB, right? You need somewhere to store the info and then you need a data fetching pattern, right? Then you need probably API, but we're going to use superbase for that one. You could use TRPC. We're going to use just straight up next and like shad CNN. So, it's like super super simple, but the trick that I've been thinking about is how do you make it really awesome? And to me, you kind of have to put your shoes you have to put yourself in the shoes of total newbies where they don't really know anything. And so, I've just been thinking a lot about that where it's like, oh, we should definitely have like a little chat bot here that can answer all the questions. Like, that'd be cool. So, gonna add that. Um, but yeah, that kind of covers probably a majority of the questions that we've been getting is just people like all the comments basically are like, "Yo, this free thing help like people love free stuff. How does a taskmaster prdle API integrations off e-commerce for sale deploy etc. That's a good question, Kether Saturnis. It works really good. The thing is is you the skill that everyone needs to get beyond being competent in the stack that they're using is how to write really good PRDs. And PRDS when I go and I share a prompt with you, it's not like it deletes the whole skill. Like it doesn't take it away. It's not like I give you this thing and now you're like a pro. Unfortunately, why it's so easy for me to use these things is because I was a product manager for a long time and I was a designer for a long time and I've been a dev for a while. So, the f first P in PRD is product so product requirements document and the kind of the key ingredients with this and this will probably be a majority of the video is me just kind of explaining this. The key ingredients to a really good PRD if I boil it down to the simplest versions or the simplest version is what is it that you're building? Why are you building it? And then how. So typically if this is maybe even a year ago, but still at a lot of companies because no one's adapted just yet, you would have the what and the why would be dealt with by a PM. And again, like why are we talking about PMs? because product requirement doc that's the role and PM is product manager not project they're very different you actually do project management as a product manager and that's why the PRD so uh exclusively important when it comes to using any of the LLM is because you still have to explain to it what is it we're building and why now the key to getting the most out of the requirements and the documents the most like the whole package is then including the how. So this is where you use your technical chops and this was typically done by an architect. So myself and my buddy Kale, I would go off and I would write these docs and the docs came from me meeting with like hundreds of delivery drivers for a startup and I'd meet with like a hundred of them if we were building something like a driver app. and it would be on me to extract what is it that we're going to build and why. And a lot of times when you're coming up with a feature idea or a new product, you really do want to spend the time on this. Like I can't harp enough on it where I spend most of the time now leveraging the skills that I had before I even started programming. It's it's that and then the programming skills combined is the sauce. So the modern day PRD for use within coding is actually more like the product or the document that you get after these two meet. Right? So what I would do is I'd be over here and if we're again building something for drivers then I'd meet with all of them and then you come up with that piece of paper. But that's not enough because then if I just gave it that and I can give you kind of actual examples like a PRD when I would write it would start with a pitch which is narrow the problem. So what is the current issue we or the customer is facing? So that's kind of like where you start and that's the most important piece and that's actually what you're doing whenever you're making anything. You're trying to narrow down the problem and you shift from just thinking of features to thinking about problems because when you go and you try to sell something, they call it a vitamin. If you're not actually solving a big problem, you don't want to sell vitamins. People don't buy as many vitamins as they do painkillers. If you burn your hand, you're not grabbing a vitamin. like you're not. And so the bigger the problem, the more you can charge, the more likely you'll have success and typically the harder it will be to solve. So you'd start with that and again, we're over here. We're in step one and we're going to get there. I promise. You'd start with the problem and then you go into the solution. And the solution is not going to be like it used to be. Like I used to come up with the solution. It'd be like one to four lines and then maybe some rough sketches of like how it kind of work and then I'd go with meet with the architect and then we'd figure out where in the codebase it's going to work. But for the case of like V1 of pitch, it's just narrow the problem, figure out the solution, figure out the nos. So there might be things that are related where you're like well we're in there. Let's touch this. or we're adding something to the driver app that does location tracking so that we can better understand where they are so every driver can deliver more food, make more money. Because we're doing location tracking, why don't we surface that to customers? That'd be helpful. No, that's a no-go because of a constraint that you set, and that's the time box. So, you might say five days. I've tried bringing this into LLMs. It doesn't make sense. you. This is useless in an AI world, but I'm just saying in a human world when you're doing this, that was a big one. So then you had no goes and then you'd have rabbit holes. Rabbit holes are known things that if you touch it, oh, we're doing geo stuff. Like no, we're not like we're on Mapbox. We like Mapbox. It's Mapbox or or Bust. Like we're not going to Google. So that's how it used to be. And I'm just trying to provide context for you guys because you might find insights in here that can make this even better what I'm about to talk about. So the modern day PRD with LLMs now, well guess what? You can probably figure out what the difference is going to be because it is with someone that's deeply technical. It's the person who's responsible for how. That is the sauce when combined with the what and the why. So there were always two people involved at our company and we're the ones that figured everything out and it's awesome especially at scale because you get to see the thing that you created in your head like go out and impact things. But even when you're sitting alone at your house now if you can learn the what the why and the how then you can build anything and that's kind of magical. So let's talk about it. This meeting would consist of us doing a mental jousting session where you basically have a thought partner that knows how the system works and I'm coming in as a technical product manager knowing the stack, knowing how things work, understanding where landmines are from previous nightmare scenarios where you think something's going to be quick and then it's not or you have an outage and then you have to write an RCA and a postmortem. All those things can occur, but you still don't know everything. You're not as technical as you think you are until you've met with a 10x engineer. And you are lucky if you get to meet with one because they just will press you on things. They will think around corners that you did not know. And that comes to the problem because you might not be asking yourself like the five wise of why are we doing this? So, if I'm saying, "Hey, we need to add like I met with 100 drivers. We need to add their location so that our logistics system that's automatically dispatching them orders. We need to make it a little more accurate." Right now, it's only updating every four minutes. But if we brought that down, we could figure out how to make it efficient. Then, we can dish them orders quicker, get them more efficient. He might say, "Well, wait a second. Like, what about this thing that's going to work better?" So you really like nowaday press the LLM to think unorthodoxly like what is it that I'm not thinking of specific to this problem and then when it comes to the solution that's where it goes from this where it's like maybe some technicals and some rough ideas to like let's just grab it and after the technical meeting you have oops you just have a bunch more context. So like let's imagine that the blue is the technical stuff. It's just going to layer things in and add all the color that you need to figure out how to actually implement it because again architect is the how. It's the person that's typically the highest paid person on the engineering squad that isn't just a manager. In the case of bootstrap startups, you're typically managing and you're an IC, an individual contributor. So, all that said, you're looking at me and you're like, "Bro, why'd you give me all this context?" Well, you need to understand why this thing has value beyond just getting the prompt and being like, "Yo, make a $100,000 a month like I don't know, like the new calorie tracking app or something. If you actually put the thought in, it's so good." Like I spent a 40 minute session today recording going step by step as an example with a client project and that's kind of what we saw the top of the video this interface. So this is domainbased architecture which is okay what's the stuff that we're going to need for this project? What are the data points that we need because we're going to work from that level in the stack up to what is going to be seen in the front end. So this is what you end up with something like this. And the way then that you would operate on it is I would just come in and I'd think of that all myself. Like I'm coming up with the idea. I'm coming up with where in the project it is. And you should definitely definitely definitely check out the main channel tomorrow morning to go through all of it. But little things like grabbing a PRD and this is a really simple one, but I'm at least passing in like this is like the idea where you'd begin. And then I take this. Look at this. Oh, I have an error on here. I'm fighting with Versell over a bundle. I don't know if you can see that. But I would take something like this and I'd grab Oopsies. I would do Oops. exclamation point F1 and it would pop that open and then in the PRD instructions I could then rip through what it was. So I usually don't have like a gigabyte of images and I would just put it on Cloudflare but that was the issue I was running in into. But yeah, anyways you take the time sketch out the things and then grab the relative paths. So if you're saying hey we're going to use a shad CN button. Well just rightclick it grab the relative path put it into there. So that way when you paste it into your PRD instructions, it's going to have all the answers it needs. And this PRD actually leaves it to ask questions towards the end. So let's grab one from like down here. No, let me see. Oh, a custom cursor PRD. Here we go. So client wants custom cursors for on hover and just normal stuff. So I wanted to make a package out of it because I don't see anything in the React space and I've never rolled my own npm package. I think it sounded kind of fun. It's a good use case. So, what I did is I put in some basic instructions to say what I'm trying to do. So, they want this needs to do the following. And then you can see that I'm pasting in where the styles are. Just making it easy so that it doesn't have to spend any sort of compute or thought tokens doing it. And then you get a really good result. In the result, it gives you the introduction, the goals, the user stories. This is what you would do in the thing I was talking about before. Your functional requirements, your nonfunctional requirements. So those are typically around performance, usability, compatibility, and fallbacks. And then some design considerations. It also will call out the things that are the no-go. They're out of scope. And then it has open questions. So this one prompt mimics a lot of this and this. And because it is asking you to answer any open questions, if this part was missing, it's gonna be like, "Hello." Like in the video tomorrow, I think I had seven questions that I missed because I've put it to be like super duper specific so that all covers are bass. All bases are covered. I'm tired, man. I've kind of broke down on energy this week because I am doing 10 pieces of content instead of seven pieces a week. And my motto is to follow what Mr. Musk says, which is the five-step algorithm. And the fifth step is to automate. But basically like do the thing manually and then cut steps then go faster then question the steps and then automate finally. Don't automate first. I see a lot of people doing that on the internet. But I'm at the point now where I need to start automating things. And that's what we're going to do in the end of the video. So this might run a little long. That's cool because it's night time. But then I would take that and I would say, "Yo, we need to put it in this format." So I've done a kind of like in a an expansion prompt where I come in, big old prompt, it expands it and it brings everything in and then I'm going to compress it down to the juice. And so I would just pop into here and I'd stick it onto agent and I would answer these questions. So, I'd say, "Hey, I don't have those 10." I would either try to go and get them. So, I'd go get 10, stick them in there. Then, I'd answer the other questions, and then I'd say, "Here's the answers to the draft, finalize it, and then put the final draft into PRD. From there, you're flying." And you just say, "Yo, why don't I just do it?" Yeah, I probably go, I'm so tired. Sack up, Parker. Cursor PNG mouse. Let's get a few of these. Let's get a pack. Cursor pack. In this video, you're about to see someone who's tired as hell make an MPN package this summer. Parker Rex fights the icon duck as he tries to make it through to the end of a YouTube video. Will he make it? Five out of 10. Okay, this is about Oh, maybe we can do Adobe stock. Adobe stock. No, I don't want to buy stock, bro. I have an account. Come on, dog. What you doing? Oh my gosh. What's going What is going Oh, there we go. We're vectors. If you don't know what a vector is, it's a scalable image. It lets you draw the paths. We're going to get a uh cursor for your mouse. Get a nice hipster one. We need 10 of them. So, those are kind of cool. Hundreds of pages. Yikes. No. No. Yes. These are kind of cool. That's a cool one. What else? Yeah, vector. Vector bust. So, let's save that. That's a kind of cool one. That'd be the on click. Yeah, we're making it all happen in here. So, let's grab those. And of course, it's going to be absolutely awful when we try to bring these in as SVGs because it just never gets them the way you need them. But what we can do is we'll go into components and let's just I like using the keyboard, but I guess I'll have to click icons.tsx. It's so tough to have to click. Create a an array. Create a react. Actually, hang on. Let's do this. RFC. Cool. Create an array. create an array of SVG icons that can be exported such that when we're in another file, we can just reference them and also pass Tailwind utilities as props so we can style them. This is a good pattern. It basically just let you have them all in one spot. And because they're vectors, you can make them as big as a billboard. That was always a thing when I was designing. I didn't make a billboard, but like golf cart wraps and car wraps and you design those. It's like a giant sticker. So, you'd have someone send you like a PNG and you're just like, "Bro, what are you doing? What are you doing, bro? Send me the SVG." And they're like, "The SV what?" And you're like, "The SVG?" C lost my marbles. I hate Next. I love Next, but I hate it. There's like so many little things that I always run into. Don't understand why, but the grass is always greener somewhere. If I went and I picked up another framework, I'd be stuck in a hole for a while. So, be the expert. I was literally like looking at this thing like what? I had to do this. This is like a little tiny project. What? Thanks. You're so helpful. Let's grab this agent. Yeah. Cool. Okay. And then let's grab our icon. Let's go in here. Okay. You're doing a good job in there. I hope. Oh no, I got to export these. Dude, doing videos is nuts because I'm like flying through these hard drives worth of space. Two TVs per and I'm just like boom, boom, boom, boom, boom. They're just dropping like flies. Uh, do we want a retain? Yeah, sure. Okay, now let's grab these bad Jacksons. And uh, what are we going to do here? Need this one. No, no, no. We don't want the whole thing. We want just one. We want that one. We like that one. I don't know, fellas. Do we like that one? I think I think we want I think we want all of them. So, let's grab each individual one. Cool. And then we don't need the background. And then let's go like that. Oh, come on. Come on. Something's got to work. Grab that one. Let's call that click one. And then, you guessed it, click two. Click three. Click quetro. Now I'm Spanish. Yeah, didn't know that, did you? I'm actually Spanish. I tricked you, O. It's not, bro. I'm losing my noggin. Okay. One, two, three, four. I can count. No, just give me that. Thank you. Good job. And then we'll snag last one. Okay. Click six. Click five. Click seven. Click two. Click three. Okay. Now we want all of them as vectors. SVG. Okay. Seems decent. Save them to the desktop. Let's grab the other one. Yes. Oh yeah, we're so hip. We only have three, but mouse cursor one. So it's cursor and click. Click. Sorry. Cursor two. Cursor three. We need three more. It's only fair. Which one do we like? Three more on the Barbie. Those those are nice. Have those two and this this one. Great. Thank you. Want that. Come on. No. No. No. That plus. No. That plus that. Yeah, bro. No. Don't do this to me. How do we get those together? We do. Oh, man. I haven't used this in a while. You make a new layer out of that. Okay. And then put that under there. If anyone watches this, I will be blown away. You know what? You're not getting a background. Cursor four and cursor. We're getting five. That's plenty. Yeah. Done. Now we have all our cursors. We got our assets. Let's do this. We're going to pop that down. Get your evil girl. And then we're going to go into icon. We already are in there. D. Now the fun part begins. If you weren't having fun before, buckle your seats. Boom. Do something. No. I'm going to have to do this one at a time. Really? Come on. Be a good dog. Okay. Oh gosh. It's this G thing. What's going on? So, the paths we want. We don't need that. We don't need XML. The style tag we don't need either. And you you're going to notice like you're going to watch what's it called? Start crying. You're going to see an LLM cry. Okay. Add click one as an icon. watching an LLM cry. This thing is going to be crying in just a matter of moments. What we're going to do with this is we will pass it into a component. And so what I'm thinking with this is I have the PRD and the vision is something like this. So if you wanted to make something super reusable, then I don't really care about like where it is on my current site. It's more like what does it look like when it's on any site. So, we know that it needs the ability to show default. And this cursor thing, key caster, it's never gone away so fast. Did you see that? And also this thing. Sorry, fellas. And like the two girls. I got a girl. It's like a huge deal. How do I turn this thing off? Come on. Go away. Great. Okay. So, we know that it needs to show the default. We know that it needs to be able to select from other defaults. Default is just like the one that you see like see how my default right now is this little crosshair. So we have those two. And then same thing with like show hover and show all the others. I It's so funny when you're tired, your brain just chugs so slowly. your processor, it's like your compute, your LLM, you're getting half a TPS, you're getting like zero zero tokens per second, right? I don't know. It needs to do those things. And then obviously we need to store it in something. So maybe like local storage. Yeah, that's fine. So it's something like that. You have like the name of that one and then you'd see the cursor which was the one that's working and then you'd have like hover and under hover you'd have like some other one. That's fine. And this would be act access for me. I think it's gonna be like slinging a footer. It's like, yo, do you want to change this thing? Did you know you can change this? See if the cursor thing is done crying. I did it. Good job. That's the trick is you change the class name to pass class name as a prop. And then you spread all the other props. Tada. Cool. And it exports it. So now in any file, I can go and do that. So let's try it. Let's try just this one, which is gonna be funny because it's the click one. Actually, before we do it, let's get a normal one. So, we have a we have click one. Where's cursor one? Cursor four. Did I not properly? I can't can't leave you guys here just watching me dillydally. Let's just grab this. Sure. Sure. Oh my gosh. Rectangles. Oh, that's right. It's pixelated. Okay. Do the same with this one. Name it cursor one. Cool. Now, let's try to figure out where we would do this. I I really do like to know how these things work. It's not like I just want like have my brain be neutered by AI rather know it because competency is dope. But I believe it's going to be something to do with our globals. So, similar to how we have a global background, we'll probably have some sort of base thing with Tailwind. So, if I type in Tailwind docs cursor, tada. How about that? Cursor pointer cursor. Oh, I'm going to have to overwrite it. Cursor custom property. Yeah. So, this allows you to change the hover state. So, we're probably going to need this cursor space value custom value. URL hand curl pointer hand curve pointer syntax is set cursor based on a completely custom value or custom property. So maybe it looks like I'm not totally sure. I'm assuming that you would then do you'd set the SVG in line as custom property on your tail config. It's my guess. That is my guess. So did it. That one did not. Thank you. That is so helpful. No, I don't I don't want you to do that. No changes made, sir. You've done literally nothing. Literally nothing. So, we're going to cheat. Let's get rid of this. We're going to come in here and we're just going to go like this. Const cursor one icon react functional component. Look at me just raw dogging. Not even icon props equals. And then we got to pass in zip properties. So, we're passing in props so that we can manipulate things. We'll do an arrow function. So, that's when we get to work on the SVG. Oh my gosh. Fix my syntax, bro. Come on, bro. How you end these things? Oh no. How'd that get there? We don't need that. We don't need that. We want to delete this style tag and the deaths. Let's look at how this one's done. Mine. You're mine now. Thank you. Yo link. How does it end? CG g. So jump up. Jump up. Go here. Paste that there. Goodbye. Nice to know you. Format the sizing. That's going to be the challenge here. What was the styling? Let's do it is better than me because it's taking How's it doing the view box there? 7 by 7 by7. That's it. Can it be cheat again? Yeah, because this this viewbox matters a lot. This is what it puts itself inside. Update cursor one icon into the format that we currently have in icons.tsx with the style matching the example below. That should be decent. And then we grab this. It's important that we can export it and then pass tail end class names as a prop from another module. Okay, we're almost there. We're almost home. Come on, baby. Legitimately don't know. Oh my gosh, there it is. That bastard. There it is. It was there the whole time. Just didn't see it. Sounds like a really nerdy like movie. The end of a movie. You never appreciated me. I was here the whole time. Okay, now let's figure this part out. Tailwind, where you at? Tailwind docs cursor. Just download this for a sec. It's funny because I'm like doing this manually because I really don't want the AI to do it. I'm like I'm making progress. Let's go. We were in this. No. Where's our PRD? Okay. The Let's start with just one normal cursor and one hover cursor to prove that this can work. They're located in the source slashcomponents/icons.tsx. And we most likely need to modify our Tailwind config.ts based on the following docs and then target those in our globals, but I'm not sure. Have you ever made this rando rando watcher? I don't know. Let's do this. We got the docs. We're going to grab the relative path so it can be nice and smart. Copy. Copy relative path. Come on. Where's that? Config. Oh, didn't work. Oh, because it's in the route, of course. Okay. Yeah, that seems fine. We'll say hover icon is hover one icon. Normal cursor cursor one icon. think outline cursor one icon click one icon one icon click so that's there which specific designs from the set be precise behavior should it appear only on clickable items or when it's pressed down oh good question I think it's just number one number two so we're answering each question oh my gosh everything is just not happening for globals cool docs Yes. Cool. And then three would be on click the mouse stays as the cursor. Great. Four. How large should the previews be? 44 px because I think that's the human interface guidelines. So update the prd with these answers. Put that into ask. This is just chasing the oneshot, you know, for something I've never done. So, it's going to get all that stuff. And then finally, we're going to grab prd.ext. What's cool, though, is you probably if you just like spammed this thing, you'd spend twice as long. And like this, I'm learning how it works. I'm kind of piecing piecing it together. And then it just is going and executing on it. So then finally in scripts example PRD. Let's grab this. Okay. Okay, there's what is the exact mechanism to get the SVG from there into there. Separate SVGs might be easiest. One, if you need to, we can just pass them. And two, precise hotspot coordinates. Forget the 44 thing. Just do common mouse behavior. And then finally, update the draft in the format below. and then write the new draft into app prd. Cool. So, what this does is it's optimizing it for the output that taskmaster needs. And then we sit back and we drink our water, which I don't have. I'm going to die. I'm going to get a water while it's doing this. But it's going to basically replace this. And if it doesn't replace it, that's fine. Sometimes it doesn't, but it's right there. So, that's pretty cool. And then I'm gonna ask Taskmaster to parse this thing. It's nice making videos like this because I'm actually doing something versus like yapping about something I'm not like producing. Like it's like can you produce while also producing? That's what I want to do. Should probably save time and just do this. Cool. I just saved time. And now we are in agent and we're going to say use taskmaster cli to parse the prd.txt into tasks. And this, ladies and gentlemen, 46 minutes and 51 seconds later is the moment you've been waiting for. So if you're the 4% of the audience who's here still, good job. So that's what it's doing. It's running the CLI and I'm getting a water while it figures out what the heck to do in sequence. That's the magic of what we just did. We just did all this stuff for this one. Okay, now it parsed all of them into tasks. I have a big JSON that shows me all the stuff of what I need to do. Extracting this data. Determine the cursor hotspot coordinates. Analyze the SVG icons to determine the appropriate hotspot coordinates for precise interaction. Okay, it's by the top of it, right? Got to extend the Tailwind config. You know what's funny? Slash depressing is how do I make a custom cursor globally in my nextjs project using tailwind and an SVG? Gosh, this is fun. What's actually interesting is I could have done this same thing in Taskmaster. Oh my gosh. Well, there you go. I just did a perplexity. Oh, sorry. Wait. Use research to find out how to use a custom cursor in Tailwind in a next.js project. There we go, fellas. When I pass it use research, it's going to do what I just did in a browser. But right here, this is all a big heist so I can show you all these features. Isn't that just so fun? It's searching web. Okay, got the same thing. Cool. Okay, cool. Use taskmaster and begin. We're about to have the best cursor in history. Also, this video should probably rank pretty well for cursor, like the ID. So, I just keep saying the word cursor over and over and over again. And literally every video on YouTube is just transcribed. So, there's that fun fact. Hi. What are you recording or on the phone? I'm recording. Oh, nice. Hi. Hi, YouTube. That's a real live girl. Hi, YouTube. 50 minutes later. 50 minutes. Yeah. 5. Well, it's going to go do it. That's pretty exciting. So then let's see. Did we have any other questions? I think I answered one. I mean the rest of them is just people saying that they want the freebies. So there you go. I will drop all this stuff in the morning when I finish the turbo kit. I've been trying but I've hit this thing too hard. That's the method. If you want to see me actually kind of breeze through this when my brain's working because it's like late now is head over to the main channel. And uh also I'm going to be opening up the I I rolled out actually not open up I rolled out a Discord that I'm really pumped about. Where is it? I rolled out a Discord for community. It's going bananas. Having a lot of fun with it because you can build little automations in there. So like I'm doing these videos and I need to like know what's going on in AI news. So I'm like, wait a second, I can just have like Zapier that reaches out and like figures out what's going on on the newsrooms everywhere. That's been helpful. Then little voice channels. What I'm thinking of doing is this daily upload music playing. But in the daily upload channel, I'm thinking I could record it in there and there's a little whiteboard and then people like that are in here can come and ask questions while we're doing it. Task is this. [Music] Man, I beat the crap out of Gemini today. Well, that's the process. You're not going to see the huge payoff of the cursor, but there will be a package coming out. I wonder what I'll call it. It's going to be so cool. But thank you for the watching the whole thing. I need to fix my hair. Thanks for watching the whole thing and uh like the video and I'll see you tomorrow. He's