Is this the Over Powered AI Coding Workflow? (Yes for now)
October 8, 2024
Parker lays out an aggressive, multi-tool AI coding workflow built around Cursor, AER, and Claude Dev, plus a quick route to Vertex AI credits. It’s fast, modular, and designed to push from ticket to code with deliberate planning and execution separation.
Cursor: the editing backbone of the workflow#
- Core role: acts as the IDE with tabbing, autocomplete, next-action suggestions, inline editing, an AI panel, and documentation indexing.
- What it’s great at: editing, navigation, fast inline changes, and quick context access without leaving the editor.
- Limitations: Composer can be CPU-heavy and flaky; Parker relies on other tools for planning and more complex tasks.
- How he uses it: primarily for editing and drafting; for planning and heavy task setup he reaches for other tools.
- Tips to maximize efficiency:
- Customize with your own ignore/conventions to keep it lightweight.
- Use Cursor for the day-to-day editing while delegating new-task planning to AER or Claude Dev.
- If you’re curious how to tweak settings, Parker mentions a dedicated settings video on his channel.
AER: multi-agent orchestration and config#
- What it is: a powerful command-driven toolset that lets you run specialized agents (ad, architect, ask, chat, etc.) with fine-grained control.
- Why it shines: fast task execution with multipronged agent roles; you can separate planning from execution and assign different agents to different parts of a task.
- Key features Parker highlights:
- Rich initialization via a config file (AER conf.yaml) with conventions and project structure templates.
- Persistent context through readme-like conventions so you don’t rewrite structural rules.
- Built-in tests integration (workflow with Bun for running tests) to verify changes as you go.
- Puppeteer integration for context: it can scrape linked content so the agents have more background data.
- Autocommits and a robust workflow for continually integrating changes.
- Looping and planning: you can drive an “architect” flow to propose steps, then execute them with speed.
- Practical usage notes:
- Use AER to set up the task context and test scaffolding once, so every new task inherits your conventions.
- You can add files, folders, and patterns with simple commands; it’s designed to be fast and repeatable.
Claude Dev: task-centric automation and looped execution#
- Role in the workflow: highly task-centric, loop-driven automation that can read sites, run its own terminal, and perform iterative fixes.
- What it does well:
- Inspects the site and client-side state to surface issues that aren’t obvious from code alone.
- Runs a self-contained terminal to execute commands and read/write files.
- Keeps looping until the issue is resolved, with a focus on practical, hands-on fixes rather than just generating code.
- Supports conventional commits and task planning to keep the project history clean.
- Capable of auto-scraping and contextualizing errors via built-in site inspection and context gathering.
- When to reach for Claude Dev: for hands-on site-aware debugging, UI/client-side issues, and looping fixes that require repeating checks.
Planning vs execution: a practical workflow pattern#
- Core idea: separate planning (what to do) from execution (how to do it) and let the right tool handle each phase.
- How Parker mixes tools:
- Use Cursor for day-to-day editing and quick iterations.
- Bring in AER or Claude Dev when starting something new or when you need robust planning, site inspection, or automated looping.
- Use AER’s config and tests to lock in patterns, then let Claude Dev or Cursor carry out the work.
- Why this approach works:
- Faster throughput by avoiding “auto-writing code” fatigue.
- Clear boundaries between planning and execution reduce churn and errors.
- Multi-agent flows give you specialized brains for different parts of a task, improving reliability and speed.
Vertex AI credits: getting $300 in free usage#
- How to get the credits:
- Go to Vertex AI and choose to try Vertex AI for free.
- If you have an existing Google account, you may be asked for a credit card to access the full $300 credit; without a card you get $150.
- The goal is to unlock access to Anthropic models through Vertex AI.
- Quick setup notes:
- Enable the Anthropic family in Vertex AI and select the Gard model for chat-based tasks.
- Use the Vertex AI chat panel to interact with the model and experiment with your workflows.
- Parker mentions there’s more detail in another video—use that as a reference if you want a deeper setup walkthrough.
- Practical takeaway: the Vertex AI credits are a nice cushion for testing the integrated workflow with Claude/Anthropic models and other AI agents.
Takeaways and actionable tips#
- Leverage a three-tool stack: Cursor for editing, AER for planning/configs/tests, Claude Dev for site-aware task execution and looping.
- Don’t rely on a single tool for everything; parallel strengths yield faster, more reliable outcomes.
- Separate planning from execution to reduce cognitive load and keep your project structure consistent.
- Tweak your config early:
- Use AER conf.yaml to codify conventions and workflows.
- Bring in tests (bun) to catch regressions as you iterate.
- Use Puppeteer-enabled context in AER to give agents richer information about web contexts and errors.
- Vertex AI credits can significantly cut costs while you experiment with Anthropic models; set up the Gard model in Vertex AI and use the chat panel to prototype workflows.
Links#
Transcript
[Music] [Applause] right now we're in the middle of an AI programming War where everyone's trying to figure out what's going on there's a new feature dropped every single day but the real winners are those who keep up to date with it and understand how we can leverage them to get more per unit of work hour and how I take things from ticket to code push plus stick around at the end and I'll show you how you get $300 in free credits from vertex AI definitely going to be helpful especially if you use sunet 3.5 so first up is cursor everybody knows this one it's is the IDE of choice it basically has seven different core features if you don't know any of it at all you can check out the settings video that I have but what I use it for is actually just the IDE because it's tabbing it's got autocomplete it's got suggestion next actions where it'll try to guess what you want to do next has inline editing an AI panel the composer and indexing of documentation really good at all those things and there's some flexibility that an extension just can't get by actually having it be in the IDE there are replacements for it where you could use continue for inline editing but I primarily use cursor for tabbing the auto complete suggestion next actions inline edits everything except for the composer now that sounds wild but I found that the composer can actually be a little bit finicky um and it's very CPU heavy I find that the ID crashes a whole lot and it's not very consistent that's why I reach for other tools there so if you want to learn how I tweak all my cursor settings for the most efficient stuff and things like my you know cursor ignore file and how to kind of get the most out of it you can check out a different video that I have on my channel I Rely heavily on a lot of the kind of baked in features except for composer if you want to use cursor for planning I recommend using 01 preview as the model don't use it too much because it is 40 cents per request which is crazy and sunet 35 is still goed when it comes to actually executing code the way that I'm actually operating is I have cursor like I said kind of running the show but when I want to start something new let's say I pull up uh linear if I wanted to start something new I'm actually reaching for AER or Claud Dev and then using cursor to finish it and the reason why is there's things that you could do in ader that you just can't do in cursor and the same thing goes with there's things in Claud Dev that you can't do in cursor of Aer it's just fast it's not as userfriendly so this won't be for beginners it won't be for the people that are not familiar with using command line interfaces but I actually prefer to have more control so I really like to use AER so AER here's on the left and when you get it set up you basically have a bunch of command line uh operators you have these tools you have ad you have architect you have ask you have chat mode clear code all these different things and it gives you full fine control of how these agents are working and this is a concept that I found to be really helpful as I've been on my journey is multi- agentic flows they just are better these tools work differently you want to separate your tasks into planning and execution so having the ability to kind of pinpoint what type of agent and what type of actor you want to have executing these tasks for you is really helpful and that's why I like to reach for AER is because in just one command it can go be the architect for me in just one command I can ask questions on how to do something and there's a syntax that I use so in the case that I wanted to you know add this dot for an event I would say something to the tune of you know I could add those files that are relevant to it so I know it already has these in context because I did slad space um and then I could just say you know ask how would I Implement adding a DOT to the miniature and it's just going to run and it's going to figure out all the things that are relevant to that through and it'll just start figuring out what is it that needs to get done and it won't write any code and that's important because I feel like anytime you ask a question in cursor composer it just wants to just bore through and start writing code for you um this will never do that and the same thing goes with the amount ount of configuration and setup that you can do with ader is just mindblowing so they have this file the comp. it's an AER conf. vml this one's empty right now I haven't done a whole lot on it but what you can do is you can specify readon files so if you have you know this conventions file which is similar to the cursor uh rules you can set up conventions saying like this is how we should do it and this is the structure of the project this is how we deal with it this is where all the important stuff is you never have to write that again because it's always going to be in there it's always going to be read me it's never going to touch it that's really helpful that's something that separates this you can do that you can also there's a really nice workflow with AER by Indie Dev Dan which shout out to him because I'm trying to implement what he's done which is just having tests built in as you develop so you can set up a workflow where here's the test man that you want to run tests so he's using bun in this case and you can specify the things that you want to edit this means that these files will automatically be added to any instance when you run AER so it's always going to have those in there and that's really nice because then you can have it where every time that you add something it's going to test it and before it even t comes back and says what the tokens are it'll see if the test passed or not you can also have autoc commits that's really nice but that that's something that I think people are underestimating it's just the power of these AI assistants when it comes to the config files where you can set up these workflows another thing is it has Puppeteer integration so if you input something that has a link in it like an error or whatever it is it'll just go and scrape it and now it's part of the context so I find that really helpful now after I did the ask I would read through and see like how is this something like is this something that we want to do is it not something we want to do if I wanted to see like you know an architecture question I could say how does this fit into the grander picture of how we're doing things is this a better pattern should we use a you know a Constructor pattern or a wrapper pattern or whatever you could ask all these different questions and it's going to be in that mode and it won't leave it so that's why I like to lean on AER a lot it's also just really really fast um so that's why I like AER it might not have the Pol UI of cursor but when I want to move fast and handle tasks it's just awesome for that the next one I want to talk about is actually claw Dev and shout out to them because they're doing stuff that cursor does not do again all these tools have their own strengths and their own weaknesses and that's kind of the beauty of where we're at right now is you if you stay on top of it you can get better workflows and we're developing those patterns us the developers so the thing with this is it's very task Centric so it goes step by step and it's actually looping the whole time it has unique features where it can inspect the site for you that's something that a cursor doesn't have it can run its own terminal so in this case I said you know I want to get some dark mode stuff and it'll go through there and it'll ask if you want to edit the file and it has this whole toolkit underneath the hood that it's using where it can execute commands it can read files obviously it can write to files it can inspect the site which is what I mentioned and that's really really helpful where if you have something where it's got you know it seems to be okay in the code base but then there's a client side error it'll run inspect site it'll run its own uh terminal in here it'll pop up with you know a new looking terminal and it'll read that and it'll come back and it just keeps looping through until it fixes it and it'll read those types for you it has you know full access to the lnter by the end of it it'll say okay cool we completed that task and it can give you the uh ability to have it run conventional commits as well I think that's really helpful just like the fact that it can do run and Loops it can do screenshot snaps it can automatically find your tasks or your types and then it has task planning you know I think that that's just like a crazy capability so you can kind of see how I've how I've done this um and how I how I use it where I just hop around to different ones and then after I either use AER or Cloud Dev that's when I'll like go and refine I just find it a you know a better workflow I've used cursor a ton but this last week or so I've just found it more enjoyable frankly to be using this combo and so again it kind of like runs in this circle where it's like okay if I want to do something net new then I can do that another thing um with you know CLA Dev is all these tools have the same patterns where you can do at and you can add a folder you can add a file s that looks at the linter you can paste the URL to fetch the contents of that and then same thing with AER where if I do add space and I do like a regx on top of a file where I could do you know components Forge slash star and then it'll add all of that so that's really helpful as well I think you can't underestimate the benefits of treating planning and execution separately I think that that's really really helpful lastly if you do want to get those credits then you just literally just type in Tex uh AI Google and you go here and you'll just hit try vertex are free so if you already have an account with them just use a different account voila you have to enter a credit card to get the full 300 if you don't enter a credit card they give you 150 which is still crazy but the credit card just means that it's not a bot they won't charge you so go ahead and do that and then once you're in there you can just enable the anthropic family through the model Gard and then go to the chat panel it's really easy I can point to a video with more detail on that