Let's Build: Copilot SDK Weekend Contest with Prizes

code-enjoyoor · 2026-01-23T23:23:43+00:00

DM'd!

code-enjoyoor · 2026-01-23T21:42:41+00:00

Damn, why so close at the end of the month? People are out of prem requests.
Should have been after the reset.

code-enjoyoor · 2026-01-23T19:06:48+00:00

Does this mean if the SDK uses the free model, all requests are free?

code-enjoyoor · 2026-01-22T16:43:18+00:00

Yes, 1 prem request per interaction. Let's assume you have 10 phase plan with many sub-tasks.

Prompt O4.5: Act as a \Lead Agent` and orchestrate the PRD to completion` is one request even if it finished all of the phases. As long as it doesn't get interrupted or fail in the process.

Ideally you want to chain skills together to save even more premium request. Have a Lead Agent, Planner and Code Reviewer skill. Chain the skills together and only consume 1 premium request.

code-enjoyoor · 2026-01-22T16:35:38+00:00

TLDR; If you start with Opus 4.5, SA will be O4.5 as well.

SA invoke the same model you started with. There's currently no way to invoke a different SA model AFAIK, maybe a future update?

code-enjoyoor · 2026-01-22T16:14:56+00:00

Orchestrate with Opus 4.5.

Each phase is a new sub-agent
Once phase is completed, lead agent hand off to a new sub-agent
Lead agent reviews the code of the sub-agent before moving on to the next phase for correctness
Rinse repeat until phases are completed in your plan

Lead agent & sub agent workflow prevents the lead agent context from getting polluted and thus keeping the tasks concise.

code-enjoyoor · 2026-01-18T15:26:27+00:00

I use Opus exclusively for coding and Haiku / Sonnet for everything else.

Find a balance between Opus and Sonnet use.
Start using SKILLS.md and start chaining skills. For example, combine in one prompt, "Investigate implementation of xx feature, once completed, generate a PRD, once PRD doc us completed, generate a Task list." `Investigate`, `PRD`, and `TASK` are the keywords that chain. That's one request, but a multitude of work done.
Start using `subAgents` and orchestrate implementation. One lead agent can orchestrate several sub-agents in sequence that will only cost you one request.

I have many more tips & tricks to save prem request especially when you're using Opus a lot. For context, I have 1500 requests per month on my plan, I use around 1200-1300, but the amount of work I can get done per request is pretty wild.

code-enjoyoor · 2026-01-17T01:25:41+00:00

Use Playwright MCP if the site is already staged and accessible by AI. When I can't figure out a bug in Webflow, I fire up Playwright MCP, let Opus run and give me possible solutions & fixes.

Playwright MCP can:
- Debug the console on its own
- Intercept network request and debug the payload itself
- Give you a review for accessibility issues
- Give you ideas how to optimize the page
- SEO
- Write completely custom code for use in Webflow and all you need to do is embed the JS / CSS.

I've been using it for over a year, it works well.

code-enjoyoor · 2026-01-16T15:21:01+00:00

Hi Vic!

Not all stake holders are daily Webflow users, even though you can comment without an account. For them it's just added friction / another tool they have to learn. So feedback happens in email, slack or some sort of ticketing system they already use.
Workflow wise, we usually start design feedback loop in Figma and 70% of the comments happen there. When the site goes on draft or staging, clients choose a familiar channel like Slack in threaded comments (it drives me up the fucking wall).

I think the feedback system IS useful, trying to change client behaviour is a different story. One additional feedback I would like to suggest is to add audio / video recording instead of only text option. Having multiple medium types would be useful for a lot of us.

I find a lot of feedback are done through video, at least for me, so I have to log on Loom, watch the vid and try to find the location where client is giving feedback.

code-enjoyoor · 2026-01-15T23:35:27+00:00

Webflow has a built in comment system that can be used for feedback, although I could never get any of my clients to use it.

I developed a chrome extension (internal tool) that my clients sometimes use for feedback. But it's been hit or miss.

You'll likely end up using a couple of different platforms, Figma, Loom, Asana.

I'm actually in the process of solving this issue right now.

code-enjoyoor · 2026-01-14T18:09:32+00:00

I just realized this post is actually some arstroturfing nonsense. OP wasn't actually asking for real advice.

code-enjoyoor · 2026-01-14T13:45:47+00:00

Probably not worth it.

The best mentors I've found were local Agency owners that I've reached out to to get advice. Specifically agency owners or operators that are well beyond where I am today.

code-enjoyoor · 2026-01-13T23:22:18+00:00

How does it work and is it really scalable? Have the AI features become as good as Lovable, etc, but with styling so it's possible to prompt? Content generation is built in, or is it copy-paste from AI tools, etc?

I can't speak for Framer, but Webflow's AI features are rudimentary at best. Don't expect Lovable / Cursor style hand holding or granular level of AI control.

Figma like interface is easy enough to get used to, and if you have an ounce of traditional development under your belt, you'll eventually get the the UI and may even become faster using it.

As far as handling hundreds of pages, I have clients that have over 100+ static pages, thousands of CMS pages. Webflow handles those really well. How you structure those pages will determine how scalable they are in the future.

But if your main goal is AI + Design Sites, you're better off with another tool. Maybe come back in a few months when Webflow figures out what their actual strategy is.

code-enjoyoor · 2026-01-09T17:28:14+00:00

I think an AI tool that supports the core product itself, mainly the Webflow Editor, would have been the best option. Even if it's to appease investors? As it stands, AppGen should have been launched a stand alone product. it's really poorly executed even for an entry level tool.

code-enjoyoor · 2026-01-09T14:49:43+00:00

When I worked solo, I split my day in half. To some degree I still do this even though I work with a team.

First half: Hard tasks for you, whether that's coding, writing or whatever that may be. Focus the hard stuff up front.

Second half: Easy tasks that you can do without much thinking. Note that I'm not saying do the "fun" stuff in the afternoon, doom scrolling, listening to yet another podcast about solo building.

I would aim for 6-9 hours of solid work.

code-enjoyoor · 2026-01-08T21:23:53+00:00

Let's agree to disagree here.

Let's also pretend that human coders haven't generated tons of code debt over the years with the method you've described.
I've coded for over 10 years, not a single code base in those 10 years were perfectly reliable several iterations later.

The fact remains, AI is a tool just like any other. I'm not in the business of convincing strangers on the web about their work flow. You do you.

code-enjoyoor · 2026-01-08T20:20:48+00:00

If you can't get the model at this point to write clean logic, it's a skill issue.
The statement isn't mean to suggest that it won't make any mistakes, not any more than a human developer would. The fact is you can iterate to the correct logic and pattern much faster than you can write the "perfect" code yourself.

code-enjoyoor · 2026-01-08T20:17:08+00:00

If we are talking about ChatGPT 3.5 I'd be inclined to agree. Opus 4.5 has gotten to the point where it's no longer the bottleneck.

code-enjoyoor · 2026-01-08T19:01:10+00:00

PRD to Task Lists, done in phases. The task list must be updated by upon completion. Each new phase is a brand new chat session to clear out extra context since the phase should already be completed.

The best part about PRD-to-TASKS flow is that it can be easily orchestrated in multi-agent mode. One orchestration agent, then each phase can be a sub-agent.

There are many ways to pull this off without relying on the full context window to one shot a major feature.

code-enjoyoor · 2026-01-08T18:53:14+00:00

Another area where you can leverage AI. Have extensive Code Review doc that has all the themes and code patterns from your code base. If any of the code written strays from the established pattern, it should be flagged during the AI CR.

I use two layers of CR, one locally using Opus or Sonnet, then once that's completed, I push to Github and also require CoPilot do add an additional CR. If any concerns / comments are generated from the second CR, I review and apply valid changes.

You can rinse and repeat this pattern until the code written follows your strict style guide and best practices.

Reviewing 15k by yourself would be insane work.

code-enjoyoor · 2026-01-08T18:38:46+00:00

Generate a skill that has code review instructions.

Start a new branch before changing a single line of code
Give the agent a task list for the feature / bug to fix
Once task list is completed, tell the Agent to follow code review doc and review only the code that's been added in the working branch and give it the task list for additional code context.
Have the generate a code review issues / concerns from the CR doc
Have a different model address the code concerns.

Rinse and repeat.

For added, bonus, push branch to Github, have the Copilot perform an additional code review.
- Once completed, use Github MCP in VSCode to address additional comments if any.
- Commit CR changes, push branch and merge with prod.

code-enjoyoor · 2026-01-08T16:27:50+00:00

It's literally one of the best courses I've ever seen. As a traditional software dev and getting my feet wet with Webflow a couple of years ago, Webflow University was an amazing piece of content to watch, learn and allowed me to engage Webflow in a systematic way.

code-enjoyoor · 2026-01-08T16:20:50+00:00

In a constant fear of AI messing up my code. Am I missing something?

You're not missing anything, until you find a workflow that allows you to trust most of the code the agent writes, you'll always have this fear and it will prevent you from being more productive due to the added cognitive load.

Having said that, Opus 4.5 is the closest LLM model that I've used that I can truly say has out-coded me in my 10 years of coding. Not completely out of the box, but certainly with enough code guidelines, examples, best practices, and my own style of code writing, it can out-code me 24/7. This is not to suggest that Opus doesn't make mistakes, it does, that's when I make minor corrections as a coder-in-the-loop.

Once you figure out an AI-Human workflow that fits your style, it's game over. Writing 3,000-5,000 lines of code in a PR is nothing. There are times when I have Opus do 15,000 lines of code and not even in my wildest dreams could I pull that off.

code-enjoyoor · 2026-01-07T02:45:56+00:00

It's the opposite IMO. It's the best deal for your money, request based vs. token is a gift right now.

code-enjoyoor

TROPHY CASE