Question on Nex’s AI-friendly scaffold and contributor onboarding

[flyoung588]

I noticed Nex generates both AGENTS.md and a project-local .agents/skills/nex-project/SKILL.md in new apps, alongside the “AI-friendly locality” idea in the README. That feels like a concrete design choice, not just a tagline: pages, components, and behavior stay close together, and the scaffold teaches both humans and agents the project shape from day one.

One outside observation: for a small framework like Nex, that could matter as much for contributor onboarding as for app development. The hard part may not be explaining file-based routing or use Nex once someone is inside the repo — it may be getting the right Elixir/HTMX people to notice the project and decide it is worth contributing to.

I’m Ray, a founder working near early devtool projects and contributor/recruiting problems. This is a genuine peer question, not a pitch:

For Nex specifically, do you expect the AGENTS.md / local skill / locality approach to reduce the need for manual contributor onboarding, or is the harder part still manually finding and pulling in the first few outside contributors from the Elixir/HTMX world?

A short reply is plenty.

[gofenix]

Hey Ray,

Good question. Honestly I think the AGENTS.md thing helps once someone is already here — it cuts down the "where do I start" questions. But finding those first few contributors from the Elixir/HTMX crowd? That's still the hard part. A good README and a few solid examples probably do more for that than any onboarding doc.