CLI for Defining AI Coding Project Scope and BoundariesCLI for Defining AI Coding Project Scope and Boundaries
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Mateo's avatar
Mateo Pérez Salazar
pro
• 4h
AI can write the code. But who decides what should actually be built? While building with AI coding agents, I kept running into the same problem: unclear requirements turned into assumptions about features, dependencies, and architecture.
Then came the extra iterations to undo decisions I never intended to make.
That’s why I’m building Archseed—a CLI that helps define the project before handing it to a coding agent.
The idea is simple: → Define what V1 needs to deliver. → Make “not building this yet” explicit. → Set technical boundaries. → Give your agent a clear project context.
It doesn’t write your application or replace your coding tool. It helps you give that tool a clearer starting point.
Less “build me everything.” More “here’s the outcome, here are the boundaries.”
What’s one assumption an AI coding agent made that you wish it had asked you about first?
aiagentsbuildinpublicwebdevepment
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started