Turn emails into revenue with Brew. No credit card, free credits to try.
vueschool.io · newsletter
Explore this email design and adapt it to your own brand. Review the copy, links, and offer before sending.
Vue School website
Hi John,
Last week we opened early access for Unlearn and over 1000 developers joined as founding members. These are engineers who chose to invest in the parts of development AI can’t replace. Every one of them is already helping shape the platform and make it better before we reopen.
Enrollment is now temporarily closed so we can collect feedback, ship improvements, and make the experience even sharper for everyone.
I wanted to give you a peek at what you will actually be doing inside Unlearn if you decide to join the waitlist when enrollment opens again.
Most AI workflows feel inconsistent for one simple reason.
Nothing carries over.
You open your agent, build a feature, get decent output… and move on. When the next task starts, you’re right back at the beginning.
Same explanations. Same corrections. Same preferences.
It feels like you’re resetting every time.
Here are three things you can set up that immediately change how this feels.
1. Make your AGENTS.md actually control behaviour (10 minutes)
You probably already have an AGENTS.md file.
The problem is most of them are passive. They describe the project, but don’t actually change how the agent behaves.
Open it and add a Do/Don’t section somewhere.
Keep it tight and opinionated, and feel free to mix up general and technical constraints.
Here’s an example.
Turn on images to see do's and don't
Every time the agent does something you don’t like, don’t just correct it. Add a rule:
“Please update AGENTS.md do/don’t to avoid this in future: …”
That’s how this file becomes useful. It evolves based on real mistakes, instead of trying to be perfect upfront.
2. Turn one repeated task into a process (5 minutes)
Pick something you do often and create:
implement-feature.md
Define the steps you want followed every time:
Turn on images to see implement-feature
Use it like this:
“Use implement-feature.md. Here’s the spec: …”
You can use this with or without plan mode in your agent.
3. Move context out of chat
Create a few simple files (you can even generate these with your agent):
spec.md → what you’re building
features.md → broken into steps
decisions.md → important choices you’ve made for the feature or project
Keep them updated as you go.
Use it like this:
“Use spec.md and features.md. Implement the next item.”
Once you do this, things start to feel different quite quickly.
You stop repeating yourself. Similar tasks start producing similar outputs. Decisions carry forward instead of being rediscovered. You get faster.
And most importantly, you’re not fixing the same issues over and over again.
Try just the first step today and you’ll feel the difference straight away.
Unlearn will reopen enrollment soon so make sure to join the waitlist to secure your spot and be first in line when access opens again.
→ Join waitlist for Unlearn - 1 click
Best,
Alex GS
Tech Education Lead at BitterBrains
vueschool.io
X
GitHub
BlueSky
YouTube
TikTok
Vue School is proudly part of BitterBrains – Making Developers’ Lives Easier
Become a BitterBrains Community Supporter here.
Courses | Vue.js Master Class | Workshops | Tutorials | Plans
🔕 Not interested? Mute Unlearn Updates & Announcements here.
You received this email because you are subscribed to Marketing Information at thomas+vueschool@brew.marketing.
Manage email preferences
2093 Philadelphia Pike #9442, Claymont, Delaware 19703, United States