@OpenAI
Either it works extremely well, or it hallucinated on me.
Not sure how to feel about this.
@OpenAI
Either it works extremely well, or it hallucinated on me.
Not sure how to feel about this.
Once the functionality is solid, then design.
The interface always changes as the product takes shape.
Once the functionality is solid, then design.
The interface always changes as the product takes shape.
Does it ACTUALLY work for users?
We know AI builds fast but breaks things.
So I built prooven - AI tests your app like a real user.
Share link to your web app and I'll test it, or try it out yourself 👇
Does it ACTUALLY work for users?
We know AI builds fast but breaks things.
So I built prooven - AI tests your app like a real user.
Share link to your web app and I'll test it, or try it out yourself 👇
"Prooven keeps you in control when building with AI."
works for arbitrary tasks on the internet.
Prooven tests the user flows in your app, but the user flows can be anything!
Small launch tomorrow, free usage incoming!
"Prooven keeps you in control when building with AI."
works for arbitrary tasks on the internet.
Prooven tests the user flows in your app, but the user flows can be anything!
Small launch tomorrow, free usage incoming!
Let AI read the PRD, propose updates, but always review them by hand.
Sounds good?
The PRD-generator v2 is on the way!
Testing the MCP server by dogfooding 👇
Let AI read the PRD, propose updates, but always review them by hand.
Sounds good?
The PRD-generator v2 is on the way!
Testing the MCP server by dogfooding 👇
Day 0: research APIs and verify documentation.
I already have a Lovable design for the MVP, so now I simply write everything down for the AI.
Day 0: research APIs and verify documentation.
I already have a Lovable design for the MVP, so now I simply write everything down for the AI.
The PRD generator has been extremely helpful for building MVPs, but it's time to step it up with MCP and some agents.
Meanwhile, you can still use the old PRD generator for free below.
The PRD generator has been extremely helpful for building MVPs, but it's time to step it up with MCP and some agents.
Meanwhile, you can still use the old PRD generator for free below.
Describe results, not systems.
For UI projects --> document screens & user flows.
For AI agents --> document input shapes and expected outcomes.
Minimal effort, maximal control.
Don't write boilerplate documentation that AI will skip over.
Describe results, not systems.
For UI projects --> document screens & user flows.
For AI agents --> document input shapes and expected outcomes.
Minimal effort, maximal control.
Don't write boilerplate documentation that AI will skip over.
Let AI maintain internal docs (it's more verbose anyway).
Keep human-readable "source of truth" that you review yourself. Give up control for the AI internal docs, and ask AI to sync their changes to your docs.
Let AI maintain internal docs (it's more verbose anyway).
Keep human-readable "source of truth" that you review yourself. Give up control for the AI internal docs, and ask AI to sync their changes to your docs.
I love choosing from options. It helps me narrow the possibilities.
If I'm professional and see the options are wrong, then I can just write on my own.
What a pleasure to code.
I love choosing from options. It helps me narrow the possibilities.
If I'm professional and see the options are wrong, then I can just write on my own.
What a pleasure to code.
You don't need to read code, but you need to read docs and give the AI crystal clear instructions.
Otherwise, you'll drown in the AI's assumptions and sea of unaligned code.
You don't need to read code, but you need to read docs and give the AI crystal clear instructions.
Otherwise, you'll drown in the AI's assumptions and sea of unaligned code.
You're the context manager. Guide the AI:
"Read previous commits and upcoming issues, then propose a plan."
Aim for simplicity.
You're the context manager. Guide the AI:
"Read previous commits and upcoming issues, then propose a plan."
Aim for simplicity.
You will.
Planning is 70% of the work. Execution just follows the map.
You will.
Planning is 70% of the work. Execution just follows the map.
I aim for balance between chaos and control.
I'm building it live with Lovable, and it's shining again for small internal apps.
Can’t share PRD? I prompt "add live sharing"
Need to mock screens with AI? I prompt "add export"
I aim for balance between chaos and control.
I'm building it live with Lovable, and it's shining again for small internal apps.
Can’t share PRD? I prompt "add live sharing"
Need to mock screens with AI? I prompt "add export"
Experienced devs can spot fake confidence from miles away.
Experienced devs can spot fake confidence from miles away.
My gut says you end up spending more time setting up flows and verifying output, vs. just writing clear specs and letting a single agent code.
Someone deep into the space, help me!
My gut says you end up spending more time setting up flows and verifying output, vs. just writing clear specs and letting a single agent code.
Someone deep into the space, help me!
Code is easy to generate so impressive GitHub means nothing.
Asking about concepts and best practices works, but takes a lot of time and energy.
Code is easy to generate so impressive GitHub means nothing.
Asking about concepts and best practices works, but takes a lot of time and energy.
When context is over 80k:
1. Ask Claude to summarize the thread
2. Review it by hand
3. Start a fresh chat with the cleaned summary
From my experience, Claude gets unstable once you near 100k tokens.
When context is over 80k:
1. Ask Claude to summarize the thread
2. Review it by hand
3. Start a fresh chat with the cleaned summary
From my experience, Claude gets unstable once you near 100k tokens.
...
Well, why are you posting?
Remind yourself of your goal, and move towards it.
...
Well, why are you posting?
Remind yourself of your goal, and move towards it.
Read your CLAUDE. md. It could be outdated and have conflicting instructions to your codebase.
Read your CLAUDE. md. It could be outdated and have conflicting instructions to your codebase.
Planning is the most important phase of building.
Planning is the most important phase of building.
I'm creating a new page:
1. State the goal, reference style & data structure
2. Build the interface
3. Connect with mock API
👉 Then start fresh chat for backend.
Context is too polluted to continue with backend work.
I'm creating a new page:
1. State the goal, reference style & data structure
2. Build the interface
3. Connect with mock API
👉 Then start fresh chat for backend.
Context is too polluted to continue with backend work.
Define strict data shapes for the UI components.
AI can make a mess in between, but your interface will always render.
Want even less errors? 👇
Define strict data shapes for the UI components.
AI can make a mess in between, but your interface will always render.
Want even less errors? 👇
Even short action of 200ms you can break it up:
0–50ms → click feedback
50–200ms → subtle color change
200ms → start page animation
The app isn't faster, but it feels faster.
Even short action of 200ms you can break it up:
0–50ms → click feedback
50–200ms → subtle color change
200ms → start page animation
The app isn't faster, but it feels faster.