Looking for builders working on something specific:
A painful workflow.
A tiny market.
An overlooked customer.
A tool you wanted for yourself.
What are you making, and who needs it?
An AI feature worth paying for:
You give it a messy input.
It produces something usable.
You don’t spend the next 20 minutes fixing it.
Simple pitch. Difficult product.
Open source is more than a cheaper alternative.
It gives builders the option to inspect, modify, self-host, and keep going when a vendor changes direction.
That option matters.
If agents become a major way people use the web, what should websites expose first?
Clear documentation?
Structured data?
An API?
A way to pay?
Feels like a web design conversation worth having.
A useful web dev exercise:
Open your app on an old phone.
Use a slow connection.
Start with a fresh account.
Now try to complete the main task without forgiving anything.
There’s room for more software that never becomes a startup.
A tool for your family.
A dashboard for a local business.
A script for a colleague.
Useful is a perfectly good outcome.
A practical way to learn agents:
Build one that uses a single tool.
Read every tool call.
Make it fail.
Add recovery.
Then give it another tool.
You’ll learn a lot before you need a framework.
“Someone could build this in a weekend” is rarely the whole story.
Could they find the customers?
Earn their trust?
Handle the edge cases?
Keep them coming back?
A good coding-agent instruction file should answer:
How does this repo work?
What should never change?
How do we check a change?
When should the agent stop and ask?
Write it for the next contributor, too.
A coding agent needs more than access to your repo.
Give it:
A clear task
Examples of good code
Commands to verify its work
Explicit limits
The prompt is only part of the setup.