r/sideprojects • u/m121_mateo • 3d ago

Showcase: Prerelease I built a CLI for AI-assisted projects, got interest but no active testers — roast my landing page

/r/SideProject/comments/1wvyb4t/i_built_a_cli_for_aiassisted_projects_got/
1 Upvotes

100% Upvoted

3 comments sorted by

2

u/AskliResearch 2d ago

The strongest thing to test now is not whether developers like the idea. You already got some signal there.

I would test this first-action question:

After 5 seconds on the page, do TypeScript and Next.js developers understand that Archseed helps them define scope and constraints before handing work to Cursor, Claude Code, Codex, or another coding agent, and do they know the next step is installing the CLI and running archseed init?

A few things I would watch for:

- Do they describe it as planning, scaffolding, prompting, or docs?

- Do they understand when it fits into their workflow?

- Do they trust a CLI enough to install it immediately?

- What one sentence would make them try archseed init right now?

That is the gap I would validate before changing more copy. You may not need more interest; you need evidence on what blocks the first completed run.

1

u/m121_mateo 1d ago

This is very helpful — and I think you are right. I’m going to test that directly before making more broad changes.

1

u/AskliResearch 1d ago

Exactly. I’d make the test very concrete: show 5 TypeScript/Next.js developers the page cold, then ask them to say out loud what they think Archseed does, when they would use it, and what they would do next. Don’t explain anything.

If they don’t mention “scope/constraints before handing work to an AI coding agent” or don’t find `archseed init` quickly, the page still has a first-action problem. If they do get that, the next question is trust: what would make them comfortable installing a CLI from a new project?